Bug #12604
closedIPv6 interface prefix change not reflected in RADVD configuration
100%
Description
https://forum.netgate.com/topic/168410/ipv6-prefix-change-not-reflected-in-ra-messages:
"This may pre-date 20211210, which I upgraded to just before this, but I changed my LAN interface IPv6 address from xxxx:xxxx:xxxx::1/64 to xxxx:xxxx:xxxx:1::1/64 so as not to have the same prefix on LAN as my /48. After that, none of my machines picked-up the new prefix (for hours). Running tcpdump on one of them, the router was still advertising the old prefix (xxxx:xxxx:xxxx:0::/64, in effect).
The fix was to disable RA on the interface and re-enable it (unmanaged, as before). Prior to that, DHCPv6 (disabled) did show the new prefix, leading me to think I didn't need to worry about RA. Everyone came to life after RA started working."
RADVD should be restarted when changing the IPv6 address of the interface
Updated by Viktor Gurov about 3 years ago
Updated by Jim Pingle about 3 years ago
- Status changed from New to Pull Request Review
- Assignee set to Viktor Gurov
- Target version set to 2.6.0
- Plus Target Version set to 22.01
Updated by Viktor Gurov about 3 years ago
- Status changed from Pull Request Review to Feedback
- % Done changed from 0 to 100
Applied in changeset fc31c0dd22d5212c22696ec24f8ab174f22279bb.
Updated by Danilo Zrenjanin almost 3 years ago
I couldn't replicate the issue on:
2.5.2-RELEASE (amd64) built on Fri Jul 02 15:33:00 EDT 2021 FreeBSD 12.2-STABLE
I captured the IPv6 router advertisement with a new prefix right after the prefix change under the interface setup. And I was able to ping a new LAN IP address right after the change.
Updated by Danilo Zrenjanin almost 3 years ago
Tested on:
2.6.0-BETA (amd64) built on Tue Jan 11 06:18:03 UTC 2022 FreeBSD 12.3-STABLE
It works as expected. I am marking this ticket resolved.
Updated by Danilo Zrenjanin almost 3 years ago
- Status changed from Feedback to Resolved