[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[lwip-devel] [bug #55972] The Neighbour Solicitation used to do IPv6 add
From: |
Gao Qingshui |
Subject: |
[lwip-devel] [bug #55972] The Neighbour Solicitation used to do IPv6 address resolution was wrong |
Date: |
Sun, 14 Apr 2019 08:48:26 -0400 (EDT) |
User-agent: |
Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:58.0) Gecko/20100101 Firefox/58.0 |
Follow-up Comment #2, bug #55972 (project lwip):
Hi, I am sorry for the previous patch as it was bad. In IPv6, the way to judge
whether one host was neighbour is very different from IPv4. pls refer the blog
on
"https://blog.ipspace.net/2012/11/ipv6-on-link-determination-what-is-it.html"
for more info, you can also refer RFC4861 and RFC5942 for more official
statements about IPv6 On-Link determination.
As a conclusion, In IPv6, it is possible that the neighbour is in one
different subnet with the Neighbour Solicitation Sender. so lwip should NOT
try to choose the source address based on the target address because it is
likely that there was no such one address. The correct way is to try to use
any valid address as the source of NS msg. pls review the attached patch
again.
(file #46768)
_______________________________________________________
Additional Item Attachment:
File name: try-to-use-any-valid-address-as-source-of-NS.patch Size:0 KB
<https://savannah.nongnu.org/file/try-to-use-any-valid-address-as-source-of-NS.patch?file_id=46768>
_______________________________________________________
Reply to this item at:
<https://savannah.nongnu.org/bugs/?55972>
_______________________________________________
Message sent via Savannah
https://savannah.nongnu.org/
- [lwip-devel] [bug #55972] The Neighbour Solicitation used to do IPv6 address resolution was wrong,
Gao Qingshui <=