Skip site navigation (1)Skip section navigation (2)
Date:      Thu, 19 Aug 2004 19:37:13 +0300
From:      Ruslan Ermilov <ru@freebsd.org>
To:        Barney Wolff <barney@databus.com>
Cc:        current@freebsd.org
Subject:   Re: RELENG_5 kernel b0rken with IPFIREWALL and without PFIL_HOOKS
Message-ID:  <20040819163713.GE82175@ip.net.ua>
In-Reply-To: <20040819160445.GA29937@pit.databus.com>
References:  <41249DEA.80404@portaone.com> <200408191300.i7JD0wvm006811@the-macgregors.org> <20040819154334.GA23926@pit.databus.com> <20040819155413.GB82175@ip.net.ua> <20040819160445.GA29937@pit.databus.com>

next in thread | previous in thread | raw e-mail | index | archive | help

--ZRyEpB+iJ+qUx0kp
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Thu, Aug 19, 2004 at 12:04:45PM -0400, Barney Wolff wrote:
> On Thu, Aug 19, 2004 at 06:54:13PM +0300, Ruslan Ermilov wrote:
> > On Thu, Aug 19, 2004 at 11:43:34AM -0400, Barney Wolff wrote:
> > > I was inspired by the PFIL_HOOKS discussion to check my firewall rule=
s :)
> > > There were none, other than 65535.  Apparently, /etc/rc.d/ipfw attemp=
ts
> > > to kldload ipfw, which will fail if ipfw is compiled into the kernel,
> > > and since the precmd failed, the _cmd will not be run.  When did it
> > > become mandatory to have ipfw as a module, not compiled in?  Is there
> > > some rationale for this?  It strikes me as rather dangerous, especial=
ly
> > > for firewalls, especially when default-to-accept is chosen.  Am I just
> > > confused, and missing some obvious bit of config?
> > >=20
> > > Is it relevant that my /usr is on vinum, and the rules are in /usr/lo=
cal/etc?
> > >=20
> > net.inet.ip.fw.enable is gone, and it upsets /etc/rc.d/ipfw.
> > I asked Andre to follow up on this.
>=20
> Yes, but aside from that, ipfw_precmd returns 1 if the kldload fails,
> which if I'm not confused causes ipfw_start not to be run.  At least
> that's what my system as of 8/17/04 says.
> Barney
>=20
Yes sure.  Non-existing sysctl causes kldload to be attempted,
that fails (because the module already exists), and the whole
/etc/rc.d/ipfw is aborted.


Cheers,
--=20
Ruslan Ermilov
ru@FreeBSD.org
FreeBSD committer

--ZRyEpB+iJ+qUx0kp
Content-Type: application/pgp-signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.5 (FreeBSD)

iD8DBQFBJNc5qRfpzJluFF4RAg1tAKCcyVvjIUUh8+plqW4QHp+wbm5QUgCgj1Mh
ad4yczYCdG7FkFych9zwSFg=
=YR16
-----END PGP SIGNATURE-----

--ZRyEpB+iJ+qUx0kp--



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20040819163713.GE82175>