-
Notifications
You must be signed in to change notification settings - Fork 437
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
feat: Automatically join solicited-node multicast addresses #1012
Conversation
fd9a473
to
508b16c
Compare
One effect of this pr is that an ethernet-based interface wants to send out multicast reports as soon as an IPv6 address is configured. Not sure if there's strong opinions on that. |
508b16c
to
1027f4f
Compare
src/iface/interface/multicast.rs
Outdated
.filter_map(|group_addr| match group_addr { | ||
IpAddress::Ipv6(address) | ||
if address.is_solicited_node_multicast() | ||
&& self.inner.has_solicited_node(*address) => |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
should be && !has_solicited_node(...)
. fixed it for you.
IPv6 over Ethernet should join the solicited-node multicast addresses required by the configured IPv6 addresses, as neighbor solicitations for these addresses have the solicited-node multicast address as destination address. This commit automatically leaves old solicited-node multicast addresses and joins the new set when the IP addresses on the interface are updated.
c53d175
to
0385bad
Compare
IPv6 over Ethernet should join the solicited-node multicast
addresses required by the configured IPv6 addresses, as neighbor
solicitations for these addresses have the solicited-node multicast
address as destination address.
This commit automatically leaves old solicited-node multicast addresses
and joins the new set when the IP addresses on the interface are
updated.