Re: 5.3 + dhclient: bpf needed in kernel config?

From: Brooks Davis <brooks_at_one-eyed-alien.net>
Date: Mon, 1 Nov 2004 10:27:49 -0800
On Mon, Nov 01, 2004 at 02:11:01PM +0100, Tobias Roth wrote:
> On Mon, Nov 01, 2004 at 03:57:31AM -0800, Brooks Davis wrote:
> > > 
> > > Is something else, unusual, needed in 5.3, that is critical
> > > to dhclient?
> > 
> > dhclient works with GENERIC and I believe all you need is bpf.
> > 
> > There is no default address for dhclient so that's not your problem.
> > Even if there were a default it would almost certaintly be in the
> > Microsoft autoconfig address space which is not part of the 192.168/16
> > network.  It is possiable you are using an unexpired prior lease in
> > /var/db/dhclient.leases.  I'd tend to suspect your dhcp server or a NIC
> > driver bug.
> 
> my cablemodem assigns me adresses within 192.168/16 when it cannot get
> a connection.

That's presumably your cablemodem not dhclient.  You're cable model is
free to do what ever it wasn't with private address space it manages.
If dhclient with no leases file laying around is handing out 192.168
addresses that's a bug that should be fixed.

-- Brooks

-- 
Any statement of the form "X is the one, true Y" is FALSE.
PGP fingerprint 655D 519C 26A7 82E7 2529  9BF0 5D8E 8BE9 F238 1AD4

Received on Mon Nov 01 2004 - 17:27:52 UTC

This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:38:20 UTC