lwIP - A Lightweight TCP/IP stack - Bugs: bug #56135, The IPv6 autoconfig should be...
You are not allowed to post comments on this tracker with your current authentication level.
bug #56135: The IPv6 autoconfig should be enabled by default.
Submitter: | Gao Qingshui <kevingao> | ||
Submitted: | Sun 14 Apr 2019 01:26:08 PM UTC | ||
Category: | IPv6 | Severity: | 3 - Normal |
Item Group: | Faulty Behaviour | Status: | Fixed |
Privacy: | Public | Assigned to: | goldsimon |
Open/Closed: | Closed | Planned Release: | None |
lwIP version: | git head |
Fri 01 Oct 2021 06:04:16 PM UTC, comment #3: |
Simon Goldschmidt <goldsimon> |
Tue 28 Sep 2021 05:44:24 AM UTC, comment #2: Is this fix also need for v2.1.3? |
Axel Lin <axellin> |
Tue 04 Feb 2020 09:27:59 PM UTC, comment #1: Applied, thanks for the patch. |
Simon Goldschmidt <goldsimon> |
Sun 14 Apr 2019 01:26:08 PM UTC, original submission:
1)as RFC4862 section 5.5 statement: Creation of global addresses as described in this section SHOULD be locally configurable. However, the processing described below MUST be enabled by default. 2) In other TCP/IP protocol stack, such as Linux and FreeBSD, the IPv6 autoconfig is enabled by default. so I suggest that IPv6 autoconfig should be enabled by default in lwip by setting netif->ip6_autoconfig_enabled to 1 in netif_add, pls refer the attached patch. |
Gao Qingshui <kevingao> |
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 4 latest changes.
Date | Changed by | Updated Field | Previous Value | => | Replaced by |
---|---|---|---|---|---|
2020-02-04 | goldsimon | Status | None | Fixed | |
Assigned to | None | goldsimon | |||
Open/Closed | Open | Closed | |||
2019-04-14 | kevingao | Attached File | - | Added enable-IPV6-autoconfig-by-default.patch, #46769 |
Powered by Savane 3.13-758e.
Corresponding source code
No, this is not really a fix: I don't want to change the behaviour here from 2.1.2 to 2.1.3.