The shell read command ignores lines that are not terminated with a carriage return. If you have added a line to one of your configuration files and Seattle Firewall seems to be ignoring the line, this is probably the reason.
DNS doesn't work on your Eiger LRP installation? -- be sure to check the setting of dnslocalports. Also, if you are running dnscache on your LRP box, DO NOT specify your ISP's name servers in the dnsservers variable.
If you receive an error message when starting or restarting the firewall and you can't determine the cause, then do the following:
seawall debug start 2> /tmp/trace
Look at the /tmp/trace file and see if that helps you determine what the problem is.
If you still can't determine what's wrong then post the /tmp/trace file to seawall-user@lists.sourceforge.net along with any additional information you believe is relevant.
The following error may appear if you have a DMZ defined:
[: seagrep: unknown operand
You may correct this problem by installing this
version of the firewall script or by editing the firewall script
and changing line 1645 to read:
elif [ -f /etc/seawall/nat -a -n "`seagrep '^dmz'
/etc/seawall/nat`" ]; then
If the PORTS column in /etc/seawall/proxyarp is non-empty, the firewall fails to start.
UDP replies from weak proxyarp hosts were being blocked by the firewall.
Install this updated firewall script to correct these problems.
The updown script included with Seattle Firewall has outdated PLUTO version check. This updated version corrects that problem.
Last updated 6/18/2001 - Tom Eastep