-
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
sys: make auto init default with DHCPv6 client #21178
base: master
Are you sure you want to change the base?
Conversation
|
|
Huh? Why wouldn't you want the DHCPv6 client auto-initialized with Ethernet? |
Because
Maybe add |
Because you can use netdev without gnrc. Isn't it the default for modules any more that the corresponding auto_init is enabled? |
I wonder why this error is raised in the C file instead of modelling this check directly in the |
Wouln't it make sense to consolidate the auto_init code from dhcp6_client with the simple_pd code? There seems to be quite some duplicated code here. |
They do mainly different configuration, IIRC. |
I'll come up with a consolidation proposal. |
I moved the former simple_pd init code into the regular auto_init code. |
94fef5b
to
e89d3d9
Compare
The DHCPv6 client uses an event queue that needs to get initialized. The auto_init code does that and, hence, should be used by default.
Allows to set and execute a hook during auto_init of the DHCPv6 client.
Sets a hook to configure the DHCPv6 client for simple PD.
e89d3d9
to
9201073
Compare
I reverted my previous idea because it was leaking gnrc code into the generic DHCPv6 client code. This new proposal now solves this via a generic hook that can be set during auto_init and is used by the gnrc simple_pd module. |
Contribution description
The DHCPv6 client uses an event queue that needs to get initialized. The auto_init code does that and, hence, should be used by default.
Testing procedure
Build the
gnrc_networking
example with DHCPv6 client support:Result
Expected result
DHCP client works, RIOT doesn't crash.