Age | Commit message (Collapse) | Author |
|
This reverts commit 6b48900358ce9b01eaa78e3a086e95a26064f0df.
|
|
|
|
StartLimitIntervalSec is part of the [Unit] definition and not the [Service]
definition [1]. This caused the following warning message:
systemd[1]: /lib/systemd/system/dhcp6c@.service:12: Unknown lvalue
'StartLimitIntervalSec' in section 'Service', ignoring
This error has been introduced via commit 992d356 ("dhcpv6-pd: T421: workaround
for non existing interfaces").
[1]: https://www.freedesktop.org/software/systemd/man/systemd.unit.html
|
|
When DHCPv6-PD is configured to delegate a prefix to a non existing interface,
it is restarted (systemd default) but will then hit the restart rate-limit which
disables the service entirely.
As VyOS currently has no "hook" to be called once an interface goes online we
need this "try and error" approach until there is a way to deal with it. This
behavior can be reproduced when delegating an IPv6 prefix to a bridge interface
as a bridge interface will always be started after all interfaces have been
configured.
We will now restart dhcp6c as long as the requested interface is online.
|
|
Wide dhcp client forks by itself
|
|
ISC does not support running the client on PPP(oE) interfaces which makes it
unusable for DHCPv6 Prefix Delegation tasks.
Internet Systems Consortium DHCP Client 4.4.1
Copyright 2004-2018 Internet Systems Consortium.
All rights reserved.
For info, please visit https://www.isc.org/software/dhcp/
Unsupported device type 512 for "pppoe0"
|