lwIP - A Lightweight TCP/IP stack - Bugs: bug #45353, IPv6 router / neighbor...
You are not allowed to post comments on this tracker with your current authentication level.
bug #45353: IPv6 router / neighbor relationship is not always consistent
Submitter: | Stian Sebastian Skjelstad <mywave> | ||
Submitted: | Fri 19 Jun 2015 08:27:05 AM UTC | ||
Category: | IPv6 | Severity: | 2 - Minor |
Item Group: | Faulty Behaviour | Status: | Fixed |
Privacy: | Public | Assigned to: | idelamer |
Open/Closed: | Closed | Planned Release: | None |
lwIP version: | git head |
Sun 06 Mar 2016 01:49:29 PM UTC, comment #4: |
Simon Goldschmidt <goldsimon> |
Fri 19 Jun 2015 05:00:19 PM UTC, comment #3: Yes, this is the potential case I am seeing, although it is hard to imagine a router that is both sending RAs and is also not online.
|
Ivan Delamer <idelamer> |
Fri 19 Jun 2015 04:54:39 PM UTC, comment #2: I only have my phone this weekend. But the issue i saw in codepath
|
Stian Sebastian Skjelstad <mywave> |
Fri 19 Jun 2015 04:16:02 PM UTC, comment #1: Thanks Stian.
|
Ivan Delamer <idelamer> |
Fri 19 Jun 2015 08:27:05 AM UTC, original submission:
When creating a IPv6 router, it will first create a neightbor and reference that with a pointer later:
|
Stian Sebastian Skjelstad <mywave> |
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 7 latest changes.
Date | Changed by | Updated Field | Previous Value | => | Replaced by |
---|---|---|---|---|---|
2016-03-06 | goldsimon | Status | Confirmed | Fixed | |
Open/Closed | Open | Closed | |||
2015-08-25 | goldsimon | Summary | IPv6 router / neightbor relationship is not always consistent | IPv6 router / neighbor relationship is not always consistent | |
2015-06-19 | idelamer | Severity | 3 - Normal | 2 - Minor | |
Status | None | Confirmed | |||
Assigned to | None | idelamer | |||
2015-06-19 | mywave | Attached File | - | Added 0001-Do-not-ever-free-neighbor_cache-entries-that-are-rou.patch, #34259 |
Powered by Savane 3.13-d3ae.
Corresponding source code
The race condition I'm seeing would be that router sends RA but then is offline a again and does not respond in state INCOMPLETE (without the router's invalidation_timer expiring). In normal communication, this does not happen, but it's not unlikely when plugging and pulling cables on the net...
The attached patch fixes this in a better way than checking for 'isrouter' in the free() function, as the latter fix would stop sending out NS.
Fixed by slightly changing the attached patch.