From: Togan Muftuoglu (toganmusers.sourceforge.net)
Date: Sun Apr 04 2004 - 11:00:33 CDT

• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

* Robbert Eggermont; <R.EggermontEWI.TUDelft.nl> on 04 Apr, 2004 wrote:
>Indeed, but... the return traffic is blocked!?!
>The services I talk about above are *client* services,
>so they need to be able to interact with the server(s)...
>(At least, that's what I'm thinking. :-)
>
>So, shouldn't the firewall be (more) completely setup before any
>network activity occurs (network related services are started)?
>I don't see any options to partly open up the firewall in the init
>stage (at least for the {dns, nfs, nis} server responses).
>Is there a way to do this (or should I do it differently)?
>

you can change $local_fs to $remote_fs in SuSEFirewall2_setup required
for setup action as by default $remote_fs should be $local_fs+nfs and
cjamhe $network to $named so dns and networking devices are setup before
SuSEfirewall2is called. Make sure you call

insserv /etc/init.d/SuSEfirewall2_init
insserv /etc/init.d/SuSEfirewall2_setup
insserv /etc/init.d/SuSEfirewall2_final

so the respective links are established. Nevertheless it is the job of
SuSEfirewall2_final to have the firewall setup for the final as all
these services have already started. I still believe the intenden format
is correct

For mor information you can refer to "man insserv" and "man init.d"

--

Togan Muftuoglu |
Unofficial SuSE FAQ Maintainer | Please reply to the list;
http://susefaq.sf.net | Please don't put me in TO/CC.

                Nisi defectum, haud refiecendum

--
Check the headers for your unsubscription address
For additional commands, e-mail: suse-security-helpsuse.com
Security-related bug reports go to securitysuse.de, not here

• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]