[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: IPF device issue; SIOCFRENB
- To: misc_(_at_)_openbsd_(_dot_)_org
- Subject: Re: IPF device issue; SIOCFRENB
- From: Craig Anderson <craig_(_at_)_xtime_(_dot_)_com>
- Date: Thu, 19 Oct 2000 10:43:03 +0000 (GMT)
On Thu, 19 Oct 2000, Craig Anderson wrote:
> I woke up this morning to my OpenBSD 2.7 stable box that acts as a
> firewall ( ipf ) having problems allowing new connections. The
> established connections were working fine, so I tried to reload the
> ruleset to see if that would clear up the issue, and this is what ipf
> SIOCFRENB: Device busy
> This macro is identified in ipf(4), but nothing is said in detail (
> perhaps it's detailed in some IPF documentation somewhere or on the IPF
> list.. checking there next ).
> What would be the main cause of this device being busy ( has anyone run
> into this )?
> BTW: The kernel/binaries were built using the stable branch from
> October 12th, 2000 without problems.
> After exhausting all 'ipf' userland options.. I rebooted the machine,
> which cleared up the problem ( I hate doing that, damn it ;) )
<--( SNIP )-->
Looking at the IPF mailing list.. the 'SIOCFRENB' device busy issue,
probably isn't the issue ( leaving off the -E from the ipf command will
quiet this guy out ( basically means that the ruleset is already
enabled.. why the hell it doesn't just say that is beyond me.. I guess
obscurity is better than nice error messages ;) ) ).
Still looking through the archives, but has anyone else run into an
issue where IPF has stopped responding to new connections ( but allowing
all established connections to go through )? Nothing changed ruleset-wise
or anything, it just started 'happening' ( it's fine now, but this would
not be a good repeat issue ).
Visit your host, monkey.org