Wesley Skoczen wrote, On 07/22/2003 02:51 AM:
Dylan wrote:
On Monday 21 July 2003 19:07, Wesley Skoczen wrote:
After rebooting my internal network isn't able to connect to internet. Issuing SuSEfirewall2 stop and SuSEfirewall2 start fixes the problem. Is there a way to fix this behaviour?
Yes
What machine was rebooted? I assume it was the gateway? Do you get your public IP from DHCP? if so then this needs to be set to yes:
FW_SERVICE_DHCLIENT="yes"
Otherwise the firewall doesn't know the external IP so thinks it's an illegal target
Yes gateway is rebooted, it gets its IP from DHCP. I entered FW_SERVICE_DHCLIENT="yes and rebooted, didn't help.
Did you also open the port for dhclient to actually work? Try adding port 68 to FW_SERVICES_EXT_UDP (and maybe INT as well). It sounds like your firewall is blocking dhclient from getting its address, stopping and restarting allows it to get its address and sets up the firewall with the correct external address. Do you see anything in /var/log/firewall? -- Joe Morris New Tribes Mission Email Address: Joe_Morris@ntm.org Web Address: http://www.mydestiny.net/~joe_morris Registered Linux user 231871 God said, I AM that I AM. I say, by the grace of God, I am what I am.