Install completion files in the right location. * debian/control: add bash-completion to Build-Depends to make sure we do YAML configurations in that directory, we just need to remove generated * networkd: don't wipe out /run/netplan on generate: we do want to keep any * netplan try: allow users to preview/test and approve network configurationĬhanges, and automatically revert if they are not accepted. io.install: install doc and examples in the * docs, examples: reformat comments in examples, add standalone example files With Windows Server-based DHCP servers which don't support RFC 4361. * DHCPv4: add a "dhcp-identifier: mac" field that can be set to fix interop * IPv6: accept-ra should default to being unset, so that the kernel default The value should be in milliseconds while keeping support for the previousīehavior of handling values are pure seconds when no suffix is present. * bonds/bridges: Support specifying time-based values with "ms" suffix when * debian/postinst: fix version check for when to write breadcrumbs. It is landed in 18.04 now looking at SRU to older releases: Additionally, failure to parse netplan configuration or invalid DHCP behavior should be investigated as possible regressions coming from this SRU. These DHCP behavior changes may lead to systems not receiving the same IP as they previously did on reservations from a DHCP server the default is not changing from using DUIDs so unchanged configurations should not be affected at all, but changes to add the new feature will likely change the IP address returned to the client from the DHCP server. It may be required to clear the DHCP server's cache of DHCP requests/responses.
requires a Windows Server DHCP setup, or another product without support for client identifier DUIDs.ġ) Configure a reservation for the device, using the device's MAC address.Ĥ) Verify that 'netplan apply' completes successfully, and that the expected IP address is received as part of the reservation. Users of Ubuntu dealing with a DHCP server based on Windows Server, Solarwinds IPAM, or possibly other DHCP server products that do no support RFC 4361.
0 kommentar(er)
