diff options
| author | Zhiqiang Liu <liuzhiqiang26@huawei.com> | 2019-02-12 20:58:06 +0800 |
|---|---|---|
| committer | Lukáš Nykrýn <lnykryn@redhat.com> | 2019-02-12 14:14:24 +0100 |
| commit | 76226a349cd65ec9b511bc68e8f3cf8c291b7057 (patch) | |
| tree | 7e981a7f60a3c7949f0008473a479d30404fd550 /Makefile | |
| parent | bf6a9d7d1f708077bfaad8ea109ad8b4eeb69556 (diff) | |
| download | initscripts-76226a349cd65ec9b511bc68e8f3cf8c291b7057.tar initscripts-76226a349cd65ec9b511bc68e8f3cf8c291b7057.tar.gz initscripts-76226a349cd65ec9b511bc68e8f3cf8c291b7057.tar.bz2 initscripts-76226a349cd65ec9b511bc68e8f3cf8c291b7057.tar.xz initscripts-76226a349cd65ec9b511bc68e8f3cf8c291b7057.zip | |
ifup-eth: apply PERSISTENT_DHCLIENT to IPv6 dhclient daemon
IPv6 dhclient daemon only tries one time to obtain a IPv6 address
from a DHCPv6 server regardless of the setting of PERSISTENT_DHCLIENT.
PERSISTENT_DHCLIENT option is only used for IPv4 dhclient daemon.
With the popularization of IPv6 protocol, some users prefer setting
IPv6 like IPv4. I think there are two solutions as follows,
1. adopt PERSISTENT_DHCLIENT option to both IPv4 and IPv6.
2. create a new option, such as PERSISTENT_DHCLIENT_IPV6 option,
just for IPv6.
The first solution does not introduce addition options, and the IPv4
and IPv6 settings are consistent. So I perfer choosing the first
solution.
Fixes: bf00a0048 ("Replace /var/run with /run everywhere")
Signed-off-by: Zhiqiang Liu <liuzhiqiang26@huawei.com>
Diffstat (limited to 'Makefile')
0 files changed, 0 insertions, 0 deletions