lwIP - A Lightweight TCP/IP stack - Tasks: task #12722, Improve IPv4/v6 address handling
You are not allowed to post comments on this tracker with your current authentication level.
task #12722: Improve IPv4/v6 address handling
Submitter: | Simon Goldschmidt <goldsimon> | ||
Submitted: | Sat 29 Jun 2013 08:11:41 PM UTC | ||
Category: | IPv6 | Should Start On: | Sat 29 Jun 2013 12:00:00 AM UTC |
Should be Finished on: | Sat 29 Jun 2013 12:00:00 AM UTC | Priority: | 5 - Normal |
Status: | Done | Privacy: | Public |
Assigned to: | goldsimon | Percent Complete: | 100% |
Open/Closed: | Closed | Planned Release: | 1.5.0 beta1 |
Effort: | 0.00 |
Jump to the original submission
Thu 09 Apr 2015 08:29:23 PM UTC, comment #10: |
Simon Goldschmidt <goldsimon> |
Mon 30 Mar 2015 04:10:33 PM UTC, comment #9: this would be amazing... I'm really busy with work now but I'll try to test it if it helps. |
Ivan Delamer <idelamer> |
Sun 29 Mar 2015 08:14:03 PM UTC, comment #8: I'm currently working on this but it's much more work than I thought: to finally get the code clean, I'm removing the whole 'ipX' idea. Instead, ip_addr_t shall be the universal address type, visible to the APIs. Plus I'm planning to rename all IPv4 functions from 'ip_*' to 'ip4_*' and renaming the version-wrapper-defines to 'ip_*'.
|
Simon Goldschmidt <goldsimon> |
Thu 05 Mar 2015 06:42:50 PM UTC, comment #7: I agree about adding a version field to ipX_addr_t, this is what sockaddr, sockaddr_in, sockaddr_in6 do with the sa_family_t field, which is always the first one:
|
Sylvain Rochet <gradator> |
Wed 04 Mar 2015 08:51:23 PM UTC, comment #6:
|
Simon Goldschmidt <goldsimon> |
Wed 04 Mar 2015 08:39:39 PM UTC, comment #5: bump (so we can discuss in this context vs. email list)
|
Ivan Delamer <idelamer> |
Wed 03 Jul 2013 03:20:54 PM UTC, comment #4: PCBs have the isipv6 member, we can use the same macros we use in tcp/udp code to handle addresses.
|
Ivan Delamer <idelamer> |
Wed 03 Jul 2013 03:01:20 PM UTC, comment #3: What drove me to start this task was that the smtp example application does not compile with IPv6 enabled because of this code:
|
Simon Goldschmidt <goldsimon> |
Tue 02 Jul 2013 03:59:06 PM UTC, comment #2: This is a good discussion and I think there is no straightforward answer.
|
Ivan Delamer <idelamer> |
Sat 29 Jun 2013 08:12:18 PM UTC, comment #1: Forgot: this change would greatly help adapting contrib applications to use IPv6 |
Simon Goldschmidt <goldsimon> |
Sat 29 Jun 2013 08:11:41 PM UTC, original submission:
One thing I'm still not happy with in integrating IPv6 is the ipX_addr_t implementation. As a union, it covers both IPv4 and IPv6 addresses but once you have it detached from its pcb, you can't tell wether it is v4 or v6.
|
Simon Goldschmidt <goldsimon> |
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 |
---|---|---|---|---|---|
2015-04-09 | goldsimon | Status | None | Done | |
Percent Complete | 0% | 100% | |||
Assigned to | None | goldsimon | |||
Open/Closed | Open | Closed | |||
2013-06-29 | goldsimon | Planned Release | None | 1.5.0 beta1 |
Powered by Savane 3.13-4448.
Corresponding source code
Should be done now. Maybe I missed some things...
At least SNMP might really be improved as it currently cannot handle IPv6 addresses in the MIB.