Skip to content
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_dhcpv6_client / uhcp: delay router advertisements until prefix was received #16755

Merged
merged 2 commits into from
Jan 4, 2022

Conversation

benpicco
Copy link
Contributor

@benpicco benpicco commented Aug 18, 2021

Contribution description

The border router does not send out router solicitations as it sends out router advertisements instead.
This delays the reception of router advertisements from upstream routers.

Instead, start with router advertisements disabled and only enable them when we received a global prefix via DHCPv6 or UHCP.

Testing procedure

Run examples/gnrc_border_router both with USE_DHCPV6=1 and without.
You should notice that now a configuration on the upstream interface is obtained much faster.

Issues/PRs references

alternative to #16590

@github-actions github-actions bot added Area: network Area: Networking Area: sys Area: System labels Aug 18, 2021
@benpicco benpicco added the Type: enhancement The issue suggests enhanceable parts / The PR enhances parts of the codebase / documentation label Aug 18, 2021
@benpicco benpicco added the CI: ready for build If set, CI server will compile all applications for all available boards for the labeled PR label Sep 17, 2021
@benpicco
Copy link
Contributor Author

benpicco commented Jan 4, 2022

Thank you for the review!

@benpicco benpicco merged commit 55900e0 into RIOT-OS:master Jan 4, 2022
@benpicco benpicco deleted the gnrc_ipv6_nib-no_adv_router branch January 4, 2022 12:34
@miri64
Copy link
Member

miri64 commented Jan 4, 2022

The border router does not send out router solicitations as it sends out router advertisements instead.
This delays the reception of router advertisements from upstream routers.

Huh? Didn't we fix this a while ago, that router solicitations go out the upstream interface?

@fjmolinas fjmolinas added this to the Release 2022.01 milestone Jan 21, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Area: network Area: Networking Area: sys Area: System CI: ready for build If set, CI server will compile all applications for all available boards for the labeled PR Type: enhancement The issue suggests enhanceable parts / The PR enhances parts of the codebase / documentation
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants