lwIP - A Lightweight TCP/IP stack - Bugs: bug #39565, Server "ddosed" by PCBs...
You are not allowed to post comments on this tracker with your current authentication level.
bug #39565: Server "ddosed" by PCBs in LAST_ACK state
Submitter: | Roman Trunov <thestream> | ||
Submitted: | Thu 25 Jul 2013 09:43:18 AM UTC | ||
Category: | TCP | Severity: | 3 - Normal |
Item Group: | Change Request | Status: | Fixed |
Privacy: | Public | Assigned to: | goldsimon |
Open/Closed: | Closed | Planned Release: | None |
lwIP version: | 1.4.1 |
Wed 18 Feb 2015 08:32:48 PM UTC, comment #1: |
Simon Goldschmidt <goldsimon> |
Thu 25 Jul 2013 09:43:18 AM UTC, original submission:
Our device is a server which suddenly stopped responding. LWIP on the device was configured for 10 PCBs for incoming connections. We found that all 10 PCBs were active in "LAST_ACK" state, so no more incoming connections could be accepted.
|
Roman Trunov <thestream> |
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 3 latest changes.
Date | Changed by | Updated Field | Previous Value | => | Replaced by |
---|---|---|---|---|---|
2015-02-18 | goldsimon | Status | None | Fixed | |
Assigned to | None | goldsimon | |||
Open/Closed | Open | Closed |
Powered by Savane 3.13-d3ae.
Corresponding source code
Fixed, thanks for the hint.
Independently of this bug, I've changed the deallocation scheme prefer killing LAST_ACK, but explicitly killing LAST_ACK (and CLOSING) independent of the prio (no data is lost) seems like a better idea.