The 03.08.16 at 03:04, Matthew Goins wrote:

Sometimes my isp's DHCP server takes a little while to "wake up" or something, so by the time my startup scripts get to the firewall, eth0 is not yet configured. Then when eth0 finally gets going, I have to open YaST and restart the firewall, because nothing works right. Is there a

You do what? :-o

quick way of doing this without firing up YaST? Not that YaST is slow, but there must be a better way.

:-) Of course. Just enter on a console, as root: SuSEfirewall2 and you are done. All services have similar commands; all of them reside in /etc/init.d/. Most of them start with rc, so, on a console (as root), "type rc [tab][tab]" and you will see them all well, (almost).

Matt, always there with the newbie questions.

Ah, that explains it! X'-) The "SuSE User Gide" and the "Administration Guide" makes good bed reading material. Just read a chapter before going to sleep every night, and you will be there :-) -- Cheers, Carlos Robinson

On Saturday 16 August 2003 09:04, Matthew Goins wrote:

Sometimes my isp's DHCP server takes a little while to "wake up" or something, so by the time my startup scripts get to the firewall, eth0 is not yet configured. Then when eth0 finally gets going, I have to open YaST and restart the firewall, because nothing works right. Is there a quick way of doing this without firing up YaST? Not that YaST is slow, but there must be a better way.

You need to tell SuSEfirewall2 that you're getting an IP by DHCP. It's in YaST under system > Editor for /etc/sysconfig files. Drill down to Network>Firewall>SuSEFirewall2>FW_SERVICE_DHCLIENT and set it to yes. Next time you boot/connect the firewall shouldn't need restarting. God knows why this setting is in such an obscure place, or why it can't be worked out by SuSEConfig... HTH Dylan

Matt, always there with the newbie questions.

-- Sweet moderation Heart of this nation Desert us not We are between the wars - Billy Bragg