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

DHCPv6 Declinet not sent after duplicate address is detected. #62

Open
Spantik opened this issue Dec 16, 2020 · 1 comment
Open

DHCPv6 Declinet not sent after duplicate address is detected. #62

Spantik opened this issue Dec 16, 2020 · 1 comment

Comments

@Spantik
Copy link

Spantik commented Dec 16, 2020

RFC 8415 https://tools.ietf.org/html/rfc8415#section-18.2.8 we MUST send DHCv6 decline if we see duplicate adddress on the network. While I was testing this when linux kernel found that address is not usable as there was a duplicate address in the network odhcp6c did not send decline.

Wanted to know if this case is not handled?

Snippet from RFC.

" The client MUST perform duplicate address detection as per
Section 5.4 of [RFC4862], which does list some exceptions, on each
of the received addresses in any IAs on which it has not performed
duplicate address detection during processing of any of the
previous Reply messages from the server. The client performs the
duplicate address detection before using the received addresses
for any traffic. If any of the addresses are found to be in use
on the link, the client sends a Decline message to the server for
those addresses as described in Section 18.2.8."

@hd-oppo
Copy link

hd-oppo commented Sep 16, 2022

Found it too.
For dhcpv6, there is no dad detect before use it.
Otherwise, I see that like wide-dhcpv6 had already support generating DECLINE msg.
Hope that there is someone to fix it.

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

No branches or pull requests

2 participants