lwIP - A Lightweight TCP/IP stack - Bugs: bug #63898, Wrong socket option level for...
You are not allowed to post comments on this tracker with your current authentication level.
bug #63898: Wrong socket option level for IPV6_CHECKSUM
Submitter: | Philipp Finke <philippfinke> | ||
Submitted: | Thu 09 Mar 2023 10:37:16 AM UTC | ||
Category: | sockets/netconn | Severity: | 3 - Normal |
Item Group: | Change Request | Status: | Fixed |
Privacy: | Public | Assigned to: | goldsimon |
Open/Closed: | Closed | Planned Release: | 2.2.1 |
lwIP version: | 2.1.3 |
Tue 10 Oct 2023 08:27:27 PM UTC, comment #2: |
Simon Goldschmidt <goldsimon> |
Tue 10 Oct 2023 06:56:01 PM UTC, comment #1: Hm, Linux seems to allow this for both SOL_RAW and SOL_IPV6 (see https://elixir.bootlin.com/linux/v6.5/source/net/ipv6/raw.c). Both for backwards compatibility and compatibility to Linux, I'd do it that way, too. |
Simon Goldschmidt <goldsimon> |
Thu 09 Mar 2023 10:37:16 AM UTC, original submission:
In lwip_setsockopt_impl() and lwip_getsockopt_impl() the option IPV6_CHECKSUM is handled for socket option level IPPROTO_RAW. This is wrong in my opinion, as RFC 3542 section 3.1 (https://www.rfc-editor.org/rfc/rfc3542) clearly states in the example that this option belongs to level IPPROTO_IPV6. |
Philipp Finke <philippfinke> |
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 |
---|---|---|---|---|---|
2023-10-10 | goldsimon | Status | In Progress | Fixed | |
Open/Closed | Open | Closed | |||
Planned Release | None | 2.2.1 | |||
2023-10-10 | goldsimon | Status | None | In Progress | |
Assigned to | None | goldsimon |
Powered by Savane 3.13-4448.
Corresponding source code
Fixed, thanks for reporting!