On Monday 21 July 2003 20:12, Wesley Skoczen wrote:
Dylan wrote:
On Monday 21 July 2003 19:51, Wesley Skoczen wrote:
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?
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
Dylan
Yes gateway is rebooted, it gets its IP from DHCP. I entered FW_SERVICE_DHCLIENT="yes and rebooted, didn't help.
Did you either A) do this in yast; or B) run SuSEconfig afterwards. Otherwise the firewall2 script doesn't get updated
I edited file /etc/sysconfig/SuSEfirewall2 and rebooted, do I need to run SuSEconfig or is this file read when the system boots up?
No, you need to run SuSEconfig to copy the changes from the config file to the actual firewal script
-- +++++++++++++++++++++++++++++++++++++++++++++++++++++++++ Wesley Skoczen http://portal.skoczen.com Linux Registered User #274645 at http://counter.li.org/ +++++++++++++++++++++++++++++++++++++++++++++++++++++++++
-- Sweet moderation Heart of this nation Desert us not We are between the wars - Billy Bragg