Re: Loss of Network Adress is DHCP Server failed for some hours
- From: Francesco Giudici <fgiudici redhat com>
- To: Olaf Hering <olaf aepfle de>
- Cc: networkmanager-list gnome org
- Subject: Re: Loss of Network Adress is DHCP Server failed for some hours
- Date: Mon, 2 Oct 2017 18:25:48 +0200
On 02/10/2017 17:22, Olaf Hering wrote:
On Mon, Oct 02, Francesco Giudici wrote:
With that anyway you miss the option of having different
connections that could fallback if the "primary" one with dhcp
fails.
How is it a failure if the DHCP server disappears, perhaps right
after it provided a lease? Well, there is likely some blurb in the
RFCs about what must be done when the lease expired. Defaulting to
fail the interface from NM point of view is certainly undesired
behaviour.
Yeah, you can only manage it with the dhcp-timeout value.
A change in the default NetworkManager.conf can switch it off
for default connections leaving the feature there if needed:
(https://bugzilla.redhat.com/show_bug.cgi?id=1350830#c7).
-EPERM
Sorry, my fault.
Here what I meant:
"It is possible to set a global default for ipv4.dhcp-timeout, see 'man
NetworkManager.conf' for the details. For example you could add the
following to /etc/NetworkManager/conf.d/10-persistent-dhcp.conf:
[connection-eth-dhcp-timeout]
match-device=type:ethernet
ipv4.dhcp-timeout=2147483647
so that all ethernet connections with unset timeout
(ipv4.dhcp-timeout=0) inherit the new value."
Olaf
[
Date Prev][
Date Next] [
Thread Prev][
Thread Next]
[
Thread Index]
[
Date Index]
[
Author Index]