lwIP - A Lightweight TCP/IP stack - Bugs: bug #47652, there is always a delay to send...
You are not allowed to post comments on this tracker with your current authentication level.
bug #47652: there is always a delay to send the first Neighbor Solicitation for the new add INCOMPLETE state neighbor entry
Submitter: | shu chen <chenshu> | ||
Submitted: | Sat 09 Apr 2016 12:15:27 AM UTC | ||
Category: | IPv6 | Severity: | 3 - Normal |
Item Group: | Change Request | Status: | Fixed |
Privacy: | Public | Assigned to: | goldsimon |
Open/Closed: | Closed | Planned Release: | None |
lwIP version: | git head |
Jump to the original submission
Tue 23 Aug 2016 01:50:59 PM UTC, comment #7: |
Simon Goldschmidt <goldsimon> |
Wed 27 Apr 2016 10:44:14 AM UTC, comment #6: Reading this correctly, I think sending the NS right away would be better. After all, this is what etharp.c does, too. |
Simon Goldschmidt <goldsimon> |
Wed 27 Apr 2016 10:28:29 AM UTC, comment #5: D'Oh! Forget the last comments, I confused this bug with DAD... |
Simon Goldschmidt <goldsimon> |
Tue 26 Apr 2016 08:28:31 PM UTC, comment #4: Also, the RFC says we SHOULD have an initial delay for first packets on a link. Although this delay should be random... |
Simon Goldschmidt <goldsimon> |
Tue 26 Apr 2016 08:06:51 PM UTC, comment #3: I'd be happy to send the NS instantly, but that wouldn't remove the delay to send packets: we do have DAD, so we need to wait, anyway, for nd6_tmr() to set the state to PREFERRED, or am I wrong? |
Simon Goldschmidt <goldsimon> |
Wed 13 Apr 2016 02:23:06 PM UTC, comment #2: The main reason why we may need to improve the IPv6 NS process is that the delay blocks all the first packet to the neighbors, all the first packet to a new neighbor always take a longer time(probably near one second) than usual.
|
shu chen <chenshu> |
Tue 12 Apr 2016 09:11:30 PM UTC, comment #1: This is an accurate description of what's going on. This could be improved, but I personally feel that for a lightweight TCP/IP stack, this should be sufficient.
|
Ivan Delamer <idelamer> |
Sat 09 Apr 2016 12:15:27 AM UTC, original submission:
The bug is found during the ping test in our project, all the first ping to the new neighbor exceeds one second.
|
shu chen <chenshu> |
No files currently attached
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 |
---|---|---|---|---|---|
2016-08-25 | goldsimon | Status | Works For Me | Fixed | |
Assigned to | None | goldsimon | |||
Open/Closed | Open | Closed | |||
2016-04-12 | idelamer | Item Group | Faulty Behaviour | Change Request | |
Status | None | Works For Me |
Powered by Savane 3.13-4448.
Corresponding source code
fixed, thanks for reportign