How to Remove LWIP and all HTTP Server and Client
Posted: Fri Mar 28, 2025 3:53 pm
I've been using the FreeRTOS TCPIP stack for over 10 years on STM32F4 devices and understand/like it.
I've had nothing but issues with the ESP LWIP stack.
I ONLY use raw socket call from the stack - I have my own Server code.
When I go into the IDF Config menu and uncheck the usage of LWIP and then attempt to build - I get an error during the compiling of
v5.4/esp-idf/components/esp_http_server/src/httpd_ws.c
that <sys/socket.h> was not found.
I would NOT get the error if the IDF was NOT attempting to compile the esp_http_server which is NOT checked in the config menu.
So -- please inform me how to build the IDF will ALL LWIP source and related HTTP Server, HTTP Client, NETIF NOT in the build process.
I did this 12 years ago for the 8266 idf so it was possible then ... why not now.
I know your intention is to make the ESP32 coding idiot proof but there must be away to bypass all of your default builds.
Thanks in advance for any reply.
NOTE: Right now my biggest issue with LWIP is that is does NOT respond to ARP requests. Example - Desk Top Chrome connects with ESP32 and wants to make a TCP connection. It keeps asking via ARP to respond to the requested IP Address (using wireshark to view network activity. LWIP does NOT respond. Finally, LWIP sends a gratuitous ARP and the connection is made. LWIP sends a gratuitous ARP about every minute so you have to hang and wait. WHY no reply when ARP is requested.
Thanks
I've had nothing but issues with the ESP LWIP stack.
I ONLY use raw socket call from the stack - I have my own Server code.
When I go into the IDF Config menu and uncheck the usage of LWIP and then attempt to build - I get an error during the compiling of
v5.4/esp-idf/components/esp_http_server/src/httpd_ws.c
that <sys/socket.h> was not found.
I would NOT get the error if the IDF was NOT attempting to compile the esp_http_server which is NOT checked in the config menu.
So -- please inform me how to build the IDF will ALL LWIP source and related HTTP Server, HTTP Client, NETIF NOT in the build process.
I did this 12 years ago for the 8266 idf so it was possible then ... why not now.
I know your intention is to make the ESP32 coding idiot proof but there must be away to bypass all of your default builds.
Thanks in advance for any reply.
NOTE: Right now my biggest issue with LWIP is that is does NOT respond to ARP requests. Example - Desk Top Chrome connects with ESP32 and wants to make a TCP connection. It keeps asking via ARP to respond to the requested IP Address (using wireshark to view network activity. LWIP does NOT respond. Finally, LWIP sends a gratuitous ARP and the connection is made. LWIP sends a gratuitous ARP about every minute so you have to hang and wait. WHY no reply when ARP is requested.
Thanks