Esp-idf: [TW#17970] LWIP update

[zafrirron]

Hi
Looking at LWIP version, you are using old version, lots of changes since you import LWIP,
would you consider updatating LWIP?
(not sure how many customizations done...)

[hchaudhary1]

@zafrirron are you looking for a particular feature?

[zafrirron]

Looking to port HomeKit protocol support github project that requires newer LWIP according to the project writer.

[FayeY]

Hi @zafrirron , the ESP32 has already supported Homekit, but it is not open on the github, you can send a request for ESP32 Homekit SDK on the ESP website.
Thanks.

[renssies]

@FayeY don't close this too quickly. The SDK you are referring too is for MFI licensees only and Espressif has said to have no plans for a non-commercial SDK. So hobbyists are creating their own SDK for the ESP32.

Since WWDC 2017 there is a Non-commercial HomeKit spec for Hobbyist, Enthusiasts, and prototyping without needing a license. People have already created an SDK for the ESP8266 (https://github.com/maximkulkin/esp-homekit). They want to port this to the ESP32, however, this can not be done due too LWIP being out of date and therefor missing features.

So until Espressif decides to also open an SDK for non-commercial use, you should still consider updating LWIP

[zafrirron]

Thanks @renssies,
I did not expect such answer from @FayeY, thought he understands most users here and ESP32 IDF current state, we all in development and prototyping stages, so sending me to MFI option.... was disappointing 👎:-( did not bother to answer).

[FayeY]

Hi both,
Sorry for the misunderstanding before.
This issue has been reopened and assigned to our engineers internally, we will evaluate this request.
Thanks for your interest in ESP32!

[affonsoloyola]

Same thing here. Trying to prototype something that needs newer features os LWIP.
I tried to get the HomeKit SDK with Espressif support but they said it’s only available for MFi licenced companies. Please update LWIP. That version is too old!

[goldsimon]

While you're at it, you could try to minimize the changes to upstream sources so that updating lwIP would be a simple matter of updating the sources and recompiling. lwIP tries to be compatible and/or simple to upgrade, so this should not be too hard as long as the sources are kept clean.

Also: a) some of the local changes seem bogus and should not be required and b) for things that are real bugs, it would be nice to get them reported back to the lwIP project.

[zhangyanjiaoesp]

@zafrirron@hchaudhary1@renssies@affonsoloyola@goldsimon
Recently we are updating our LWIP to the offical v2.0.3, but it will take some time for the system to work stablely

[goldsimon]

That's great news! May I suggest again to work with the lwIP project (I'm the maintainer of that stack) to get you a clean copy of the stack? That will also make it easier to integrate new releases, as there should be no stability issues otherwise (when upgrading a clean lwIP stack).

Just post your questions or issues to the [email protected] mailing list.

[zhangyanjiaoesp]

@goldsimon yes, you are right ! we are doing what you said exactlly.

[jukorp]

i'm looking forward to the new lwip 2.0.3 version.
Estimate when ready?

[zaninime]

I'm also waiting on this. Anything I can do to help? Thanks!

[jpan127]

Another bump (to show this would be appreciated).

[ourairquality]

I would also like to see a sync to the upstream lwip. The esp-open-rtos has been following the upstream lwip and attempting to contribute changes upstream. It would make it easier to port code across these development environments. Is someone planning to work on this, or is it waiting for a contribution?

[jeffsenn]

Big +1 on this. I just spent the day finding and fixing a leak (LWIP Bug #51937) that has already been fixed "upstream".

[NZSmartie]

I've started a fork where i've removed Espressif's copy of LWIP in favour of using @goldsimon's version hosted on nongnu,org. The build does compile with "Copy L2 to L3" enabled under both LWIP and Ethernet component configuration options.

Modifications have/are being done to components of ESP-IDF to support the new LWIP and I've found quite a few redundancies with developers reimplementing code that already exists in LWIP. Hopefully once it's all done, keeping LWIP up to date will be as easy as git pull within components/lwip/lwip

Please note that not all configuration options have been tested yet, but i hope to have that done in the next week.

[twelve12pm]

Big +1 on using clean upstream lwIP!

[comcomservices]

@NZSmartie, using your fork! Thanks a ton!

[zhangyanjiaoesp]

Hi all， sorry for replying later.
The lwIP in ESP-IDF has been updated based on the offical stable version 2.0.3 in the latest master.
And the lwIP is as a submodule in ESP-IDF now, you can find the esp-lwip here