LWIP version and ESP32

[ibrahimdanish]

Hi,

I want to know which version of LWIP ESP32 is currenlty using? From the source files, it seems like ESP32 took version 1.5 which is quite old and from there ESP32 is doing modifications and upgrades of its own. Whereas the LWIP latest stable version is 2.3.

My other question is that why ESP32 does not just pull the latest stable version of LWIP and keep the porting code seperate from the LWIP source code? This in order to use the latest LWIP while maintaining the portability.

Is there any guideline how to use the latest LWIP version?

Regards,

Ibrahim

[kolban]

I'm going to guess ... if we look here:

https://savannah.nongnu.org/news/?group=lwip

We see that lwIP 2.0.0 was released in November 2016. The ESP32 (and ESP-IDF stack) were already available and being actively used. At that time, we were still waiting on core drivers such as Bluetooth, I2C and SPI so I would imagine all attention was being given to them.

From a personal perspective, if I am bringing a new product to market (eg. the ESP32) I'd try and make it as stable as possible so using an older release of lwIP that had already proven itself sounds like a plan. Looking at the release date of 1.5, it seems to be towards the end of 2015 which probably means that it is about 24 months old. In my mind, that's still pretty recent.

Are there identified bug fixes or features or performance enhancements that we can point to in lwIP latest that are impacting us in ESP32 land?

[Gfast2]

Hi Ibrahim,

Older colleague told me, there are still some 8-bit Stuff in Satellite, the reason is very simple: Know-How & Test. The more complexer the system is, the more overhead developers are facing and more time to spend on debugging and testing.

Till a system / Platform is "bug-free" in real, the ecnomic system has markt them as "deprecated" for years.

So it sounds to me, we have to take care our decisions. Things are not always as simple as "The newser the better", it is very often true though.

Cheer2

Gfast2

[mjahamel]

> Are there identified bug fixes or features or performance enhancements that we can point to in lwIP latest that are impacting us in
> ESP32 land?

I believe there is: LwIP 2.0 has support for https in the httpd application (via an altcp layer). I have been building a captive-portal WiFi configuration app for the ESP32. This is basically working, but is subject to the rather serious objection that it passes the WiFi SSID and password that the user specifies across in plaintext over an unencrypted link. There are several ways of dealing with this, but https would be the nicest and has a lot of other applications.

[kolban]

I'd always assumed that LwIP dealt exclusively with the TCP/IP layers and higher levels dealt with application protocols delivered over the sockets. In the ESP-IDF, we have SSL processing via the mbedtls functions. There are also a number of HTTP libraries for either making/sending HTTP requests or for processing incoming HTTP requests (web server/http server). These also seem to support SSL.

[WiFive]

> Are there identified bug fixes or features or performance enhancements that we can point to in lwIP latest that are impacting us in
> ESP32 land?

I believe there is: LwIP 2.0 has support for https in the httpd application (via an altcp layer). I have been building a captive-portal WiFi configuration app for the ESP32. This is basically working, but is subject to the rather serious objection that it passes the WiFi SSID and password that the user specifies across in plaintext over an unencrypted link. There are several ways of dealing with this, but https would be the nicest and has a lot of other applications.

Not really if it is using wpa2 psk. There are other http servers that support tls like https://github.com/chmorgan/libesphttpd and https://github.com/warmcat/lws-esp32-factory

[Gfast2]

> Are there identified bug fixes or features or performance enhancements that we can point to in lwIP latest that are impacting us in
> ESP32 land?

I believe there is: LwIP 2.0 has support for https in the httpd application (via an altcp layer). I have been building a captive-portal WiFi configuration app for the ESP32. This is basically working, but is subject to the rather serious objection that it passes the WiFi SSID and password that the user specifies across in plaintext over an unencrypted link. There are several ways of dealing with this, but https would be the nicest and has a lot of other applications.

Not really if it is using wpa2 psk. There are other http servers that support tls like https://github.com/chmorgan/libesphttpd and https://github.com/warmcat/lws-esp32-factory

Hi WiFive,

any disscusion about a list of webservers that works great on ESP32?

AFAIK, mongoose, libhttpd, kolban's WebServer.

Cheers

Gfast2