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

Support for extracting DNS server information from SLAAC (RFC 8106) #293

Open
mariuszste opened this issue Dec 9, 2024 · 3 comments
Open
Labels
feature New feature or enhancement request

Comments

@mariuszste
Copy link

Is your feature request related to a problem? Please describe.
Some networks only offer IPv6 over SLAAC (since many client devices don't support DHCPv6 anyway).
Currently, there is no way to extract the DNS server information from router advertisements.

Describe the solution you'd like
implement RFC 8106 and/or add a callback so the user can parse unsupported ICMPv6 options themselves.

Describe alternatives you've considered
DHCPv6, but not all routers support it (looking at you MikroTik)

Additional context
RFC 8106

@mariuszste mariuszste added the feature New feature or enhancement request label Dec 9, 2024
@Hnz2
Copy link

Hnz2 commented Dec 10, 2024

Hi mariuszste,

One year ago I have same question. Answer was this #176

But it would be good to know if there is any progress.

Jan

@fdesbiens
Copy link

Hi @mariuszste.

Thank you for this feature request. I will discuss it with the project team.

To my knowledge, no work has been done to implement this feature since last year, @Hnz2. Microsoft halted the implementation of new features when it decided to contribute Azure RTOS to the Eclipse Foundation.

@fdesbiens
Copy link

@eclipse-threadx/iot-threadx-committers Please review the proposal and provide your feedback.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature New feature or enhancement request
Projects
None yet
Development

No branches or pull requests

3 participants