You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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
The text was updated successfully, but these errors were encountered:
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.
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
The text was updated successfully, but these errors were encountered: