[Firehol-support] Error after Panic mode

Costa Tsaousis costa at tsaousis.gr
Sun Mar 16 19:53:26 GMT 2003


The way the default NFS service is implemented, if portmap is not allowed
by the running firewall, you will have to stop and start the firewall.
This is because FireHOL has to query the portmap in order to find the NFS

If you are using NFS in production systems, I suggest to make nfsd and
mountd run on static ports (the documentation has a link to the NFS-HOWTO
that says how to do this). Then you can define the services nfsd and
mountd using the static ports you used and get rid of the portmap query.

Costa Tsaousis

Bernhard Gruen said:
> Hi,
> I have found a new? error in the panic mode. I have a NFS daemon running
>  on my server. So i have two entries in the firehol.conf.
> server portmap accept
> server nfs accept
> It is possible to go to the panic mode but
> the way back (with /etc/init.d/firehol start) is not possible there are
> warnings that it is not possible to connect to portmap RPC daemon. I am
> not sure if this is an error in my configuration because you write in
> your services-documentation someting special for nfs.
> Bernhard
> -------------------------------------------------------
> This SF.net email is sponsored by:Crypto Challenge is now open!
> Get cracking and register here for some mind boggling fun and
> the chance of winning an Apple iPod:
> http://ads.sourceforge.net/cgi-bin/redirect.pl?thaw0031en
> _______________________________________________
> Firehol-support mailing list
> Firehol-support at lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/firehol-support

More information about the Firehol-support mailing list