Bug#688470: netcfg infinitely tries to get a DHCPv6 reply in mixed stateless/stateful autoconfig if the DHCPv6 server does not reply
Package: netcfg
Version: 1.92
Severity: wishlist
Scenario: Netcfg 1.92 runs in an IPv6 environment with
stateless autoconfiguration including RDNSS.
When the router advertisements have "AdvOtherConfigFlag" set to
"On", i.e. they tell the client to do a DHCPv6 request for
additional (non-address) information, and the DHCPv6 server
does not respond, the client seems to infinitely try to get
a DHCPv6 reply. After about 10 minutes I have killed the
dhcp6c process, but that results in the whole network
configuration process starting from the beginning.
Having router advertisements with AdvOtherConfigFlag On and
a non-responding DHCPv6 server should of course not happen
in a correctly functioning network, but if possible it would
be nice if the client could timeout within a relatively
short time when there is no reply, as it does for DHCPv4.
In this scenario (DNS is supplied via RA) all information which
is strictly required for the installation (prefix, gateway and
DNS) has already been gathered from the RA, so the installation
could proceed without the additional DHCPv6 info (domain name,
NTP servers, timezone info, etc.). A malfunctioning DHCPv6 server
should not block the installation in this case.
Even if DNS info is not supplied via router advertisements but
via DHCPv6, it would be better from a user perspective if the
DHCPv6 request would timeout after a reasonable amount of time
and the user gets asked for the missing DNS information.
Regards,
Karsten
--
Gem. Par. 28 Abs. 4 Bundesdatenschutzgesetz widerspreche ich der Nutzung
sowie der Weitergabe meiner personenbezogenen Daten für Zwecke der
Werbung sowie der Markt- oder Meinungsforschung.
Reply to: