lwIP - A Lightweight TCP/IP stack - Bugs: bug #55972, The Neighbour Solicitation used to...
You are not allowed to post comments on this tracker with your current authentication level.
bug #55972: The Neighbour Solicitation used to do IPv6 address resolution was wrong
Submitter: | Gao Qingshui <kevingao> | ||
Submitted: | Thu 21 Mar 2019 01:16:36 PM UTC | ||
Category: | IPv6 | Severity: | 3 - Normal |
Item Group: | Faulty Behaviour | Status: | Fixed |
Privacy: | Public | Assigned to: | None |
Open/Closed: | Closed | Planned Release: | None |
lwIP version: | git head |
Wed 17 Jul 2019 07:32:15 PM UTC, comment #4: |
Simon Goldschmidt <goldsimon> |
Sun 14 Apr 2019 01:05:55 PM UTC, comment #3: for the ping failed issue I reported, the best fix method is to update the peer side's neighbour cache by sending one Neighbour Advertisement actively, with override flag. There was two way to do this, 1) make nd6_send_na not one static function and call it after L2 address changed; 2) call nd6_send_na at the last of netif_issue_reports, this modification is take IPv4 gratituous ARP as reference because GARP is sent out after L2 address changed, but I suggest to add the 3rd input argument for netif_issue_reports to make the caller decide which address used to send NA. the second way I prefer. |
Gao Qingshui <kevingao> |
Sun 14 Apr 2019 12:48:25 PM UTC, comment #2: 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.
|
Gao Qingshui <kevingao> |
Sun 24 Mar 2019 08:35:07 PM UTC, comment #1: Applied, thanks for the patch! |
Dirk Ziegelmeier <dziegel> |
Thu 21 Mar 2019 01:16:36 PM UTC, original submission:
The Neighbour Solicitation was used to do IPv6 address resolution or Duplicate Address Detection. For IPv6 address resolution, lwip always use the link local address as the source address, this could cause network unreachable in below scenario.
|
Gao Qingshui <kevingao> |
Depends on the following items: None found
Items that depend on this one: None found
There are 0 votes so far. Votes easily highlight which items people would like to see resolved in priority, independently of the priority of the item set by tracker managers.
Follow 5 latest changes.
Date | Changed by | Updated Field | Previous Value | => | Replaced by |
---|---|---|---|---|---|
2019-04-14 | kevingao | Attached File | - | Added try-to-use-any-valid-address-as-source-of-NS.patch, #46768 | |
2019-03-24 | dziegel | Status | None | Fixed | |
Open/Closed | Open | Closed | |||
2019-03-21 | kevingao | Attached File | - | Added 11.pcap, #46601 | |
Attached File | - | Added choose-source-address-based-on-target-address.patch, #46602 |
Powered by Savane 3.13-4448.
Corresponding source code
Gao, this bug is closed. If comment #2 or #3 contain things to be addressed, please speak up!