In scenarios where we need to start dhcp6 on several interfaces at once, the mandatory 1 second sleep can add an unacceptable amount of wait time.
(mandatory 1s added here)
https://github.com/anders-nexthop/ifupdown2/blob/164248fa353fe5396679e767a7e709b56496c51b/ifupdown2/addons/dhcp.py#L165
On a network switch with port breakouts, we may need to run this code on a few hundred interfaces at the same time, which can add up to several minutes of wait time. If an operator guarantees that a link local address for a given interface will exist before we try to start dhcp6, then the wait is not necessary. Therefor, we should add handling for passing "no" as a value to dhcp6-ll-wait (similar to what is done for the "dhcp-wait" knob), and skip the link-local addr check when this knob is configured.
PR:
#349
In scenarios where we need to start dhcp6 on several interfaces at once, the mandatory 1 second sleep can add an unacceptable amount of wait time.
(mandatory 1s added here)
https://github.com/anders-nexthop/ifupdown2/blob/164248fa353fe5396679e767a7e709b56496c51b/ifupdown2/addons/dhcp.py#L165
On a network switch with port breakouts, we may need to run this code on a few hundred interfaces at the same time, which can add up to several minutes of wait time. If an operator guarantees that a link local address for a given interface will exist before we try to start dhcp6, then the wait is not necessary. Therefor, we should add handling for passing "no" as a value to dhcp6-ll-wait (similar to what is done for the "dhcp-wait" knob), and skip the link-local addr check when this knob is configured.
PR:
#349