conf/74610: Hostname resolution failure causes firewall rules to stop loading

Matteo Riondato rionda at gufi.org
Tue Mar 29 07:20:05 PST 2005


The following reply was made to PR conf/74610; it has been noted by GNATS.

From: Matteo Riondato <rionda at gufi.org>
To: freebsd-gnats-submit at freebsd.org
Cc: Ceri Davies <ceri at submonkey.net>
Subject: Re: conf/74610: Hostname resolution failure causes firewall rules to stop loading
Date: Tue, 29 Mar 2005 17:15:12 +0200

 --nljfjKcp9HDtPSOP
 Content-Type: text/plain; charset=us-ascii
 Content-Disposition: inline
 Content-Transfer-Encoding: quoted-printable
 
 According to rcorder -s nostart /etc/rc.d/* , named is started after
 ipfw rules have been loaded and IMHO, this is right and good.
 I think you should rely on /etc/hosts to have a hostname translated to
 an IP address at this point of the boot process. Perhaps this should be
 documented (where? ipfw(8) ? ) but then this would become a
 documentation related problem.
 Best Regards
 
 --=20
 Rionda aka Matteo Riondato
 G.U.F.I. Staff Member (http://www.gufi.org)
 FreeSBIE Developer (http://www.freesbie.org)
 
 --nljfjKcp9HDtPSOP
 Content-Type: application/pgp-signature
 Content-Disposition: inline
 
 -----BEGIN PGP SIGNATURE-----
 Version: GnuPG v1.4.0 (FreeBSD)
 
 iD8DBQFCSXEA2Mp4pR7Fa+wRAvCsAJ41Ttq1WAc7UtAxDlKPeDXeiIC2gACgqxA/
 TahZ2/ODGg1W+zMZP6pkAbA=
 =eil5
 -----END PGP SIGNATURE-----
 
 --nljfjKcp9HDtPSOP--


More information about the freebsd-bugs mailing list