Troubleshooting Asymmetric Routing
4 articles
Browse articlesAZTCOFW / DOCUMENTATION
Configuration guides, troubleshooting and practical advice for AZTCOFW.
4 articles
Browse articles9 articles
Browse articles2 articles
Browse articles5 articles
Browse articles3 articles
Browse articles16 articles
Browse articles4 articles
Browse articles3 articles
Browse articles3 articles
Browse articles7 articles
Browse articles4 articles
Browse articles4 articles
Browse articles9 articles
Browse articles4 articles
Browse articles8 articles
Browse articles7 articles
Browse articles1 articles
Browse articles3 articles
Browse articles7 articles
Browse articles14 articles
Browse articles3 articles
Browse articles3 articles
Browse articles2 articles
Browse articles1 articles
Browse articles4 articles
Browse articles5 articles
Browse articles11 articles
Browse articles6 articles
Browse articlesPacket captures can be invaluable for troubleshooting and debugging traffic issues. With a packet capture, it is easy to tell if the traffic is reaching the outside interface or leaving an inside interface, among many ot
Occasionally, the following messages may appear in the system log: login: login on console as root or: login: login on ttyv0 as root This is normal. It means that the console menu stopped and restarted, or someone presse
The following log messages are recorded when a utility has placed the network card into “promiscuous mode”: Feb 10 01:41:58 kernel: vr0: promiscuous mode disabled Feb 10 01:41:57 kernel: vr0: promiscuous mode e
Disable the FTP Proxy and attempt the connection again Use SCP/SFTP which only needs 1 port to traverse the firewall since it is wrapped in SSH (yes a safe AND simple way of traversing a firewall!) Don’t use FTP (highly
To eliminate a possible incompatibility between wireless functions on AZTCO-FW and a wireless client, be sure to try it with multiple devices or cards first. If the same problem is repeatable with several different makes
First check the service status at Status > Services . If the IPsec service is stopped, double check that it is enabled at VPN > IPsec . Also, if using mobile clients, ensure that on the Mobile clients tab, the enable box
The top suspect if a tunnel comes up but won’t pass traffic is the IPsec firewall rules. If Site A cannot reach Site B, check the Site B firewall log and rules. Conversely, if Site B cannot contact Site A, check the Site
If a tunnel will establish sometimes, but not always, generally there is a mismatch on one side. The tunnel may still establish because if the settings presented by one side are more secure, the other may accept them, bu
In some cases a tunnel will function properly but once the phase 1 or phase 2 lifetime expires the tunnel will fail to renegotiate properly. This can manifest itself in a few different ways, each with a different resolut
Certain traffic cannot be filtered. Not because the AZTCO-FW software isn’t capable, but because they actually do not touch the firewall at all. A prime example of this is trying to keep one device on the LAN from access
AZTCO-FW -upgrade keeps a log of the last update attempt, which may contain additional useful information. This log is located at /conf/upgrade_log.latest.txt. Please include the contents of this log with any post or sup
If the update system does not offer an upgrade to the most recent version, the upgrade will not proceed, or the upgrade process encounters errors with shared libraries, take the following steps: Navigate to System > Upda
If UPnP/NAT-PMP is enabled and a LAN device opens a port to the world, the traffic may still get in even if it appears it should otherwise be blocked.
Out of the box, traffic allowed in by the UPnP daemon will end up in the default queue. This happens because the rules generated dynamically by the UPnP daemon do not have any knowledge of queues unless UPnP is configure
Rule problems can almost always be solved by waiting 20-30 minutes and then trying the download again. Failing that, uninstall the package completely and then reinstall the package to ensure the snort binaries are the la
Traceroute is a useful tool for testing and verifying routes and multi-WAN functionality, among other uses. It shows each “hop” along the path a packet travels from one end to the other, along with the latency encountere
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
To view the top processes, including interrupt processing CPU usage and system CPU top -aSH
To view I/O operations: systat -iostat 1 Or: top -aSH Then press m to switch to I/O mode to view disk activity.
To view the interrupt counters and other system usage: systat -vmstat 1
To view the mbuf usage: netstat -m Note: Alternately, check the dashboard mbuf counter, and the graph under Status > Monitoring on the System tab.
There are two ways to view the routes: Via the WebGUI, and via the command line. To view the routes in the WebGUI, navigate to Diagnostics > Routes and output is shown similar to this Figure. The output from the command
Setting Promiscuous mode: Allow All on the relevant interfaces of the VM allows CARP to function on any interface type (Bridged, Host-Only, Internal)
There could also be issues between the WAN and the Modem/CPE. It could be a cable, or a quirk in how the two interfaces talk to each other. Place a small switch between the firewall and the Modem/CPE as a test.