Running 4.11-RELEASE. Getting some weirdness from dhclient(1).
It keeps reporting "not found" for any interface. This is a
notebook PC and at first I thought it was just the wi(4) card,
but I tried a "regular" ep(4) NIC and got the same result. The
interface is found by pccardd(8) just fine (after
"David G. Andersen" wrote:
>
> On Wed, Feb 09, 2005 at 01:58:28PM -0500, David G. Andersen scribed:
> > On Wed, Feb 09, 2005 at 06:33:11PM +0100, Andre Oppermann scribed:
> > > >
> > > > (Barring that, has anyone patched it in their own system, and if so,
> > > > would you mind sending me the patc
On Wed, Feb 09, 2005 at 01:58:28PM -0500, David G. Andersen scribed:
> On Wed, Feb 09, 2005 at 06:33:11PM +0100, Andre Oppermann scribed:
> > >
> > > (Barring that, has anyone patched it in their own system, and if so,
> > > would you mind sending me the patch? I dislike running custom kernel
> >
On Wed, Feb 09, 2005 at 06:33:11PM +0100, Andre Oppermann scribed:
> >
> > (Barring that, has anyone patched it in their own system, and if so,
> > would you mind sending me the patch? I dislike running custom kernel
> > code on these machines, but I'm happy to do so to get things working. :)
>
"David G. Andersen" wrote:
>
> The last messages I saw in the archives about kern/73129 indicated
> that it was going to be fixed "shortly"
>
> (73129 is the "IPFW misbehavior in RELENG_5 thread" -- it's no longer
> possible to use ipfw fwd to perform policy routing).
>
> This bug is on my criti
The last messages I saw in the archives about kern/73129 indicated
that it was going to be fixed "shortly"
(73129 is the "IPFW misbehavior in RELENG_5 thread" -- it's no longer
possible to use ipfw fwd to perform policy routing).
This bug is on my critical path for getting my network entirely swa
