On 06/12/11 22:34, Dan Williams wrote:
On Mon, 2011-12-05 at 17:21 +, Chris Paulson-Ellis wrote:
On 05/12/11 14:54, Chris Paulson-Ellis wrote:
On 05/12/11 12:34, Chris Paulson-Ellis wrote:
Is there some way to configure NetworkManager to keep running dhclient
and never give up?
NetworkMan
On Mon, 2011-12-05 at 17:21 +, Chris Paulson-Ellis wrote:
> On 05/12/11 14:54, Chris Paulson-Ellis wrote:
> > On 05/12/11 12:34, Chris Paulson-Ellis wrote:
> >> Is there some way to configure NetworkManager to keep running dhclient
> >> and never give up?
> >>
> >> NetworkManager-0.9.1.90-3.git
On 05/12/11 14:54, Chris Paulson-Ellis wrote:
On 05/12/11 12:34, Chris Paulson-Ellis wrote:
Is there some way to configure NetworkManager to keep running dhclient
and never give up?
NetworkManager-0.9.1.90-3.git20110927.fc15.x86_64
It seems commit fdfbe00aac3f17b19bb8d84cba1c8f210d90e8a0 is t
On 05/12/11 12:34, Chris Paulson-Ellis wrote:
Is there some way to configure NetworkManager to keep running dhclient
and never give up?
NetworkManager-0.9.1.90-3.git20110927.fc15.x86_64
It seems commit fdfbe00aac3f17b19bb8d84cba1c8f210d90e8a0 is trying to
address my issue, but I'm not seeing
On 05/12/11 13:10, Jiri Popelka wrote:
timeout ;
statement in /etc/dhcp/dhclient-.conf
could help.
The problem is with the behaviour of NetworkManager, not dhclient.
From dhclient.conf man page:
"The timeout statement determines the amount of time that must pass
between the time that the c
timeout ;
statement in /etc/dhcp/dhclient-.conf
could help.
From dhclient.conf man page:
"The timeout statement determines the amount of time that must pass
between the time that the client begins
to try to determine its address and the time that it decides that it's
not going to be able to
Hi,
I have a deployment scenario which requires NetworkManager to keep
trying forever to obtain a IPv4 address on a wired network using DHCP.
Currently, NetworkManager runs dhclient every 45s, which is fine, but it
stops after a few minutes and never seems to try again. In my scenario,
the (