[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Old Index]
Re: Retiring dhclient
On Wed, Nov 23, 2011 at 10:30:48PM +0000, Roy Marples wrote:
> On Tue, 2011-11-15 at 17:10 +0100, Joerg Sonnenberger wrote:
> > The second important item is that dhcpcd by default depends on working
> > link state management in the driver. Sadly, quite a few of our older
> > drivers don't do it properly. Typical issue is calling if_reset from
> > if_ioctl e.g. to update multicast filters. This is a two fold issue:
> > (1) Fixing kernel drivers to not do this.
> > (2) Documenting the work arounds (aka crippling dhcpcd with -K)
> > Building a list of drivers affected would be a good start.
> > What other items are missing?
> I don't know if you covered it, but currently dhcpcd by default requests
> an MTU from the DHCP server and if given and valid, sets it.
> A lot of drivers reset their link on MTU change. Infact, about 90% of
> the dhcpcd bug reports I get is about this very behaviour.
Perhaps it would be better to set the MTU only if it actually differs from the
MTU already configured on the adapter?
Main Index |
Thread Index |