lwIP - A Lightweight TCP/IP stack - Bugs: bug #34534, Error in sending fragmented IP if...
You are not allowed to post comments on this tracker with your current authentication level.
bug #34534: Error in sending fragmented IP if MEM_ALIGNMENT > 2
Submitter: | Andriy Korud <akorud> | ||
Submitted: | Wed 12 Oct 2011 05:49:20 AM UTC | ||
Category: | IPv4 | Severity: | 3 - Normal |
Item Group: | Faulty Behaviour | Status: | Fixed |
Privacy: | Public | Assigned to: | goldsimon |
Open/Closed: | Closed | Planned Release: | None |
lwIP version: | 1.4.0 |
Fri 24 Feb 2012 09:45:52 AM UTC, comment #2: |
Simon Goldschmidt <goldsimon> |
Wed 12 Oct 2011 04:24:58 PM UTC, comment #1: Well spot! Although I doubt that many people use a MEM_ALIGNMENT setting > 4 (and I think I did not ever try that myself), I'm still happy if it works.
|
Simon Goldschmidt <goldsimon> |
Wed 12 Oct 2011 05:49:20 AM UTC, original submission:
Hi, I've discovered that this change "Fixed bug #29361 (ip_frag has problems with zero-copy DMA MACs) by adding custom pbufs and implementing custom pbufs that reference other (original) pbufs." has introduced new problem.
|
Andriy Korud <akorud> |
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 6 latest changes.
Date | Changed by | Updated Field | Previous Value | => | Replaced by |
---|---|---|---|---|---|
2012-02-24 | goldsimon | Summary | Error in sending fragmented IP if MEM_ALIGNMENT > 4 | Error in sending fragmented IP if MEM_ALIGNMENT > 2 | |
2011-10-12 | goldsimon | Open/Closed | Open | Closed | |
2011-10-12 | goldsimon | Status | None | Fixed | |
Assigned to | None | goldsimon | |||
Planned Release | 1.4.1 | ||||
Summary | Error in sending fragmented IP if MEM_ALIGNMENT > 1 | Error in sending fragmented IP if MEM_ALIGNMENT > 4 |
Powered by Savane 3.13-caa5.
Corresponding source code
Adapted summary:
When ETH_PAD_SIZE is set to 0, this also happens for MEM_ALIGNMENT > 2.