diff options
author | Stefano Brivio <sbrivio@redhat.com> | 2023-12-08 17:43:17 +0100 |
---|---|---|
committer | Stefano Brivio <sbrivio@redhat.com> | 2023-12-27 19:22:29 +0100 |
commit | 00358b782852f5b66bf413251ead0d1ee5d724c5 (patch) | |
tree | 1aa2edab4cd026b80fbc714ca6b3e27fe918d4e0 /test/pasta | |
parent | d491a4099b8db6199225812562b4dfc315accc6d (diff) | |
download | passt-00358b782852f5b66bf413251ead0d1ee5d724c5.tar passt-00358b782852f5b66bf413251ead0d1ee5d724c5.tar.gz passt-00358b782852f5b66bf413251ead0d1ee5d724c5.tar.bz2 passt-00358b782852f5b66bf413251ead0d1ee5d724c5.tar.lz passt-00358b782852f5b66bf413251ead0d1ee5d724c5.tar.xz passt-00358b782852f5b66bf413251ead0d1ee5d724c5.tar.zst passt-00358b782852f5b66bf413251ead0d1ee5d724c5.zip |
ndp: Extend lifetime of prefix, router, RDNSS and search list
Currently, we have no mechanism to dynamically update IPv6
addressing, routing or DNS information (which should eventually be
implemented via netlink monitor), so it makes no sense to limit
lifetimes of NDP information to any particular value.
If we do, with common configurations of systemd-networkd in a guest,
we can end up in a situation where we have a /128 address assigned
via DHCPv6, the NDP-assigned prefix expires, and the default route
also expires. However, as there's a valid address, the prefix is
not renewed. As a result, the default route becomes invalid and we
lose it altogether, which implies that the guest loses IPv6
connectivity except for link-local communication.
Set the router lifetime to the maximum allowed by RFC 8319, that is,
65535 seconds (about 18 hours). RFC 4861 limited this value to 9000
seconds, but RFC 8319 later updated this limit.
Set prefix and DNS information lifetime to infinity. This is allowed
by RFC 4861 and RFC 8319.
Signed-off-by: Stefano Brivio <sbrivio@redhat.com>
Reviewed-by: David Gibson <david@gibson.dropbear.id.au>
Diffstat (limited to 'test/pasta')
0 files changed, 0 insertions, 0 deletions