lwIP - A Lightweight TCP/IP stack - Bugs: bug #62138, Minimum frame length
You are not allowed to post comments on this tracker with your current authentication level.
bug #62138: Minimum frame length
Submitter: | To Tamir <totamir> | ||
Submitted: | Thu 03 Mar 2022 01:40:55 PM UTC | ||
Category: | None | Severity: | 3 - Normal |
Item Group: | None | Status: | Wont Fix |
Privacy: | Public | Assigned to: | goldsimon |
Open/Closed: | Closed | Planned Release: | None |
lwIP version: | 2.1.1 |
Thu 03 Mar 2022 08:31:12 PM UTC, comment #1: |
Simon Goldschmidt <goldsimon> |
Thu 03 Mar 2022 01:40:55 PM UTC, original submission:
My ethernet controller require minimum frame length equal to 60 bytes (and then adds CRC on the fly). I modified SIZEOF_ETHARP_HDR to 46, so my controller send ARP frames correctly. But I have problem with other frames. Some frames generated by function ethernet_output has 58 bytes (propably ACK), so my ethernet controller ignore them. Is there some possibility to set minimum frame length?
|
To Tamir <totamir> |
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 |
---|---|---|---|---|---|
2022-03-03 | goldsimon | Status | None | Wont Fix | |
Assigned to | None | goldsimon | |||
Open/Closed | Open | Closed |
Powered by Savane 3.13-4b48.
Corresponding source code
Achieving the minimum frame length is up to the netif driver, as it is a "limitation" of the underlying transport medium.
You can just add the padding in your driver.