-
Notifications
You must be signed in to change notification settings - Fork 2k
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
gnrc_ipv6_nib: include RIO with all subnets in downstream RA #19644
Conversation
Why should it be optional in final RAs but is always included in normal RAs? |
62e1fe1
to
5e182b5
Compare
5e182b5
to
4a5d68a
Compare
It's now also optional in normal RAs (and even more so as it's only needed when we are a) not the default router but have b) a route to a specific subnet we want to propagate). |
4a5d68a
to
fa5fd21
Compare
I'd say resolve the conflict and let's go. |
fa5fd21
to
41f9c25
Compare
bors merge |
Build succeeded! The publicly hosted instance of bors-ng is deprecated and will go away soon. If you want to self-host your own instance, instructions are here. If you want to switch to GitHub's built-in merge queue, visit their help page. |
Contribution description
When RIOT is an upstream router to a subnet, but not the default route, we need to convey the information that this subnet is available through it to the downstream hosts.
Testing procedure
A riot board is connected to a Raspberry Pi over USB. The Raspberry Pi also has a WiFi uplink that constitutes it's default route.
The RIOT node is part of the
fd00::/32
network, but by use ofgnrc_ipv6_auto_subnets
it's actually in thefd00:0:c000::/64
subnet.To reach the
fd00::1
host at the root of the upstream subnet, we have to inform the Raspberry Pi that the entire fd00::/32network is reachable through the RIOT node, not just
fd00:0:c000::/64` - we can use the Route Information Option for that.We don't want to include redundant RIOs in the RA, e.g. the networks
fd00:0:8000::/33
andfd00:0:c000::/64
are both included infd00::/32
(which is also reachable through our node) so we only have to include that one.and on the Linux side
Issues/PRs references