Troubleshooting Multi-WAN

Configuration guides, troubleshooting and practical advice for AZTCOFW.

Articles

7 results

A gateway is incorrectly marked offline

If a gateway is listed as offline, but the WAN is actually up, several things could be at fault: First, test to see if the monitor IP address responds to a ping from a client device on the LAN, and again from Diagnostics

Failover not working

If problems occur when an Internet connection fails, typically it is because the monitor IP address is still answering, so the firewall thinks the connection is still available. Check Status > Gateways to verify. An IP a

Load balancing not working

Check that the Gateway Group is properly configured for load balancing, with at least two gateways on the same tier. Check that the firewall rules being matched direct traffic to the correct load balancing gateway group.

Ping works by IP address, but web browsing fails

In this case, the most likely cause is DNS. If the firewall DNS settings do not match those in Interface and DNS Configuration, clients may not be able to resolve DNS when a WAN is down. Review the settings and fix any p

Policy routing does not work for web traffic or all traffic

When a proxy package that can transparently capture HTTP traffic is used, such as squid, it overrides any policy routes that are defined for client traffic on that port. So no matter which gateway is set in firewall rule

Squid doesn’t seem to be using both connections

Squid and most other packages on the firewall itself do not understand load balancing; They will use only the WAN connection with the default gateway.

Verify Firewall Rule Configuration

The most common error when configuring multi-WAN is improper firewall rules. Remember, the first matching rule wins and any further rules are ignored. If a policy routing rule is below the default LAN rule in the list, n