On Tue, Nov 30, 1999 at 10:34:56AM -0700, Davec wrote:
>
> Yup tried it, didn't work. Got the same error messages (refer to the [LONG]
> email I sent a few days past. Thanks for the suggestion though.
>
I missed that one apparently. Send it to me in private and I'll see what I
can do.
> Dave
On Tue, 30 Nov 1999, Davec wrote:
> On Tue, 30 Nov 1999, Dan Langille wrote:
>
> > FWIW, I just fetched the tarball from the website and started a compile.
> > It gets further than the previous attempt. My suggestion to Davec is
> > that he try the instructions at:
> >
> > http://www.freebs
I just went to the Oct. 7th snap of -CURRENT (right before IP Filter was
removed from FreeBSD 4.0-CURRENT's source tree). Would this warning have
anything to do with ipl not working in the latest snap?
WARNING: driver ipl should register devices with make_dev() (dev_t = "#ipl/1")
As I recall, th
On Tue, 30 Nov 1999, Dan Langille wrote:
> FWIW, I just fetched the tarball from the website and started a compile.
> It gets further than the previous attempt. My suggestion to Davec is
> that he try the instructions at:
>
> http://www.freebsddiary.org/freebsd/ipfilter333.htm
>
> I know th
On Mon, 29 Nov 1999, O'Shaughnessy Evans wrote:
> So could it be that some of your rules are breaking things? I think I've
> seen the same error message when trying to write a rule for a non-existant
> interface name or a group that wasn't created with "... head N".
>
> --
> O'Shaughnessy Evans
On Mon, 29 Nov 1999, O'Shaughnessy Evans wrote:
> "Mikhail A. Sokolov" <[EMAIL PROTECTED]> wrote:
> > No, it can't. He was refering to ipf -V; I managed to reproduce the
> > behaviour several days ago, but since I remade the devices it's ok in
> > my case, but in his. Again, no other rules/whatev
"Mikhail A. Sokolov" <[EMAIL PROTECTED]> wrote:
> On Mon, Nov 29, 1999 at 02:15:16PM -0800, O'Shaughnessy Evans wrote:
> # Davec <[EMAIL PROTECTED]> wrote:
> # [...]
> # > But when I try to load any rules, I get the error messages above.
> # > Same result with ipnat. I checked to make sure I was
On Mon, Nov 29, 1999 at 02:15:16PM -0800, O'Shaughnessy Evans wrote:
# Davec <[EMAIL PROTECTED]> wrote:
# [...]
#> But when I try to load any rules, I get the error messages above. Same result
# > with ipnat. I checked to make sure I was using the right version of ipf:
# [...]
#
# So could it be
Davec <[EMAIL PROTECTED]> wrote:
[...]
> But when I try to load any rules, I get the error messages above. Same result
> with ipnat. I checked to make sure I was using the right version of ipf:
[...]
So could it be that some of your rules are breaking things? I think I've
seen the same error mes
Ok, I just tried downloading the IP Filter sources for 3.3.3 and followed the
instructions at http://www.freebsddiary.org/freebsd/ipfilter333.htm.
Unfortunately I have ended up with the same errors:
open device: Device not configured
ioctl(SIOCIPFFL): Bad file descriptor
To reiterate for -CURREN
No solutions for you, but I have had the same exact problems with
Current and Ip Filter 3.3.3. Giving up.
Current Ip Filter works fine on 3.3-STABLE. Can't hardly wait for 4.0
to be stable and released, I'm not happy with my current mangling of
different compilers in STABLE.
_
Nathan Kinsman
11 matches
Mail list logo
