Re: DHCP timeout on ethernet device.

[Dan Williams <dcbw redhat com>]

On Tue, 2011-10-04 at 11:44 +0200, Jiri Popelka wrote:
> You can add
> 
> timeout <value>;
> 
> to /etc/dhcp/dhclient-<interface>.conf
> 
> 
> See also
> http://mail.gnome.org/archives/networkmanager-list/2011-September/msg00127.html

That doesn't work because NM bounds the DHCP transaction and kills it if
it runs over 45 seconds.

The better question is:  why is DHCP on that network taking so long?
I've talked about bumping the timeout to 60 seconds before, but the
point here is that if your network is taking more than 60 seconds to
respond to DHCP requests, something is *really*, *really* wrong, and
should be corrected on the network side instead of working around this
in the client.  How long is the DHCP transaction taking?

Dan

> -
> Jiri
> 
> On 10/04/2011 10:24 AM, Anders Gnistrup wrote:
> > Hi
> >
> > I have searched the net and the only method to set the DHCP request timeout value is to change the code.
> >
> >   /NetworkManager/src/dhcp-manager/nm-dhcp-manager.c:#define NM_DHCP_TIMEOUT   45 /* DHCP timeout, in seconds */
> >
> > But that it not a good solution.
> > It there configuration option in the DBUS interface or keyfile that can be set?
> > My own answer is No, it has to done in code.
> >
> > /AG
> 
> _______________________________________________
> networkmanager-list mailing list
> networkmanager-list gnome org
> http://mail.gnome.org/mailman/listinfo/networkmanager-list