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. <SNIP>
Are you using an interface which not available when the firewall starts? The PC here has a USB wireless adapter which is not up when the firewall starts. After booting, once the adapter is activated the firewall has to be restarted to allow connections to the USB adapter. LW999