diff options
| author | Zhiqiang Liu <liuzhiqiang26@huawei.com> | 2019-03-06 04:25:00 +0800 |
|---|---|---|
| committer | Jan Macku <jamacku@redhat.com> | 2021-06-24 12:07:01 +0200 |
| commit | a8212c1b232a902938d0e5ea6a82bd6ae52e861c (patch) | |
| tree | d20ab96dc25e964e9b5672e098acec4d0d2580d6 /network-scripts/ifup-aliases | |
| parent | 81b7893dd1627c43464064e670583803aca2d5ff (diff) | |
| download | initscripts-a8212c1b232a902938d0e5ea6a82bd6ae52e861c.tar initscripts-a8212c1b232a902938d0e5ea6a82bd6ae52e861c.tar.gz initscripts-a8212c1b232a902938d0e5ea6a82bd6ae52e861c.tar.bz2 initscripts-a8212c1b232a902938d0e5ea6a82bd6ae52e861c.tar.xz initscripts-a8212c1b232a902938d0e5ea6a82bd6ae52e861c.zip | |
ifup-eth: add a new PERSISTENT_DHCLIENT_IPV6 option for IPv6 dhclient daemon
In 76226a34 ("ifup-eth: apply PERSISTENT_DHCLIENT to IPv6 dhclient daemon"),
one PERSISTENT_DHCLIENT option works for both IPv4 and IPv6, so the IPv4
and IPv6 settings are consistent. However, the user settings for IPv4 and IPv6
are limited.
For example, users try to adopt both IPv4 and IPv6 protocol. DHCPv6 servers
may be not stable as DHCP servers, thus the expectation for obtaining IPv6
address is lower than IPv4 address. For users, IPv4 address must be
obtained for the basic communication. So the PERSISTENT_DHCLIENT option is
set to be "yes | 1" for IPv4 address. However, the network service may be
stuck until it fails due to missing DHCPv6 servers, and the remaining devices also
cannot obtain both IPv4 and IPv6 addresses. The problem is very serious for users.
Here, I add a new PERSISTENT_DHCLIENT_IPV6 option only for IPv6 dhclient daemon,
so users can set IPv4 and IPv6 separately.
Fixes: 76226a3 ("ifup-eth: apply PERSISTENT_DHCLIENT to IPv6 dhclient daemon")
Signed-off-by: Zhiqiang Liu <liuzhiqiang26@huawei.com>
Diffstat (limited to 'network-scripts/ifup-aliases')
0 files changed, 0 insertions, 0 deletions