lwip: bump to v2.2.0 #19780
Merged
lwip: bump to v2.2.0 #19780
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
Had some time to test 6LoWPAN. LWIP_IPV4=1 does not make any sense with 6LoWPAN (= IPv6 over Low-Power Wireless Personal Area Networks), as I remembered during testing ;-P, so this leaves only
|
|
Is this still a draft, or ready for review? |
|
This is still a draft, since 2.2.0 is still a release candidate, as explained in OP. |
|
(I just wanted to test as early as possible to report possible bugs back to lwIP before the next RC) |
867110c to
f800437
Compare
|
2.2.0 came out last night, so this is ready for review. I did not test 6LoWPAN or IPv4 with |
f800437 to
2cbdd66
Compare
|
And rebased to current master. |
|
Tested IPv4 and IPv6 dual stack support (and IPv4 alone, but not shown) on ServerRIOT native interrupts/signals initialized.
RIOT native board initialized.
RIOT native hardware initialization complete.
main(): This is RIOT! (Version: 2023.10-devel-310-g2cbdd6-pkg/enh/lwip-2.2.0)
RIOT lwip test application
> ip server start 254
ip server start 254
Success: started IP server on protocol 254
> Received IP data from [10.0.0.166]:
00000000 AB CD EF
ifconfig
ifconfig
Iface ET0 HWaddr: da:27:1d:a8:64:24 Link: up State: up
Link type: wired
inet addr: 10.0.0.167 mask: 255.255.255.0 gw: 10.0.0.1
inet6 addr: fe80:0:0:0:d827:1dff:fea8:6424 scope: link state: valid preferred
> Received IP data from [fe80::e0bc:7dff:fecb:f550]:
00000000 12 34 56
udp server start 1337
udp server start 1337
Success: started UDP server on port 1337
> Received UDP data from [fe80::e0bc:7dff:fecb:f550]:49153
00000000 AB CD EF
Received UDP data from [a00:a6::]:49154
00000000 12 34 56 78 90
tcp server start 4321
tcp server start 4321
Success: started TCP server on port 4321
> TCP client [a00:a6::]:49153 connected
Received TCP data from client [a00:a6::]:49153
00000000 76 54 32 10
TCP connection to [a00:a6::]:49153 reset
TCP client [fe80::e0bc:7dff:fecb:f550]:49154 connected
Received TCP data from client [fe80::e0bc:7dff:fecb:f550]:49154
00000000 AB CD EFClientRIOT native interrupts/signals initialized.
RIOT native board initialized.
RIOT native hardware initialization complete.
main(): This is RIOT! (Version: 2023.10-devel-310-g2cbdd6-pkg/enh/lwip-2.2.0)
RIOT lwip test application
> ip send 10.0.0.167 254 abcdef
ip send 10.0.0.167 254 abcdef
Success: send 3 byte over IPv4 to 10.0.0.167 (next header: 254)
> ip send fe80:0:0:0:d827:1dff:fea8:6424 254 123456
ip send fe80:0:0:0:d827:1dff:fea8:6424 254 123456
Success: send 3 byte over IPv6 to fe80:0:0:0:d827:1dff:fea8:6424 (next header: 254)
> udp send [fe80:0:0:0:d827:1dff:fea8:6424]:1337 abcdef
udp send [fe80:0:0:0:d827:1dff:fea8:6424]:1337 abcdef
Success: send 3 byte over UDP to [fe80:0:0:0:d827:1dff:fea8:6424]:1337
> udp send 10.0.0.167:1337 123456789
udp send 10.0.0.167:1337 123456789
Success: send 5 byte over UDP to 10.0.0.167:1337
> tcp connect 10.0.0.167:4321
tcp connect 10.0.0.167:4321
> tcp send 7654321
tcp send 7654321
Success: send 4 byte over TCP to server
> tcp disconnect
tcp disconnect
> tcp connect [fe80:0:0:0:d827:1dff:fea8:6424]:4321
tcp connect [fe80:0:0:0:d827:1dff:fea8:6424]:4321
> tcp send abcdef
tcp send abcdef
Success: send 3 byte over TCP to server |
|
I can confirm that DHCP and TCP on IPv4 are still working (at least on native). |
|
SLAAC and TCP over IPv6 seems to work as well. |
|
Tested 6LoWPAN on IoT-LAB |
benpicco
approved these changes
Sep 26, 2023
OlegHahm
approved these changes
Sep 26, 2023
|
bors merge |
|
Build failed: |
|
Seems unrelated. Let's retry: bors merge |
|
bors merge |
|
Build succeeded! The publicly hosted instance of bors-ng is deprecated and will go away soon. If you want to self-host your own instance, instructions are here. If you want to switch to GitHub's built-in merge queue, visit their help page. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Contribution description
RC1 of lwIP 2.2.0 is out, so let's see if it works with RIOT.
DO NOT MERGE YET! WE SHOULD ONLY MERGE THE ACTUAL RELEASE. This PR is currently WIP and only for testing if the 2.2.0 API works with RIOT.Testing procedure
The
tests/pkg/lwip*tests should work.tests/lwipshould also manually tested for all combinations ofLWIP_IPV4=0andLWIP_IPV6=1on a 6LoWPAN-based board (did not do that yet).Issues/PRs references
None