RuggedCom RuggedRouter RX1000 - Manual (Page 243)

Chapter 26 – Maintaining The Router
Gauntlet net fw TCP any 10000
The order of rules is significant. Rules inserted before this set will not be
protected by Gauntlet. Any rule appearing after the gauntlet chain rules will
automatically be ignored. Consult with RuggedCom support for assistance. If
you want to grant SSH access to the router, replace "10000" in the last rule with
"22,10000".
When adding these rules via Webmin, for those rules where you select "Gauntlet"
from the "Action" pulldown list, be sure to leave the "log to syslog level" set to
"<Don't log>". If you manually edit the "/etc/shorewall/rules" file then do not
specify any loglevel in your Gauntlet rules.
5. Ensure that the firewall is enabled in the Bootup and Shutdown Menu and
apply the firewall configuration to effect the changes.
Note: You must ensure that the firewall is configured and enabled when using the
Gauntlet Security Appliance.
Gauntlet Status Menu
Gauntlet integrates tightly with the firewall, opening it for communications between
vetted clients and critical assets on a demand basis.
Figure 206: Gauntlet Security Appliance Menu
The status menu provides a list of validated open connections.
Upgrading Gauntlet
During an upgrade, the Gauntlet daemon may be required to restart. During the
upgrade all existing Gauntlet protected connections will be closed.
RuggedCom 241