lwIP Socket API difference between WIFI & ETH Stack.
Posted: Thu Mar 22, 2018 2:44 pm
Hallo ESP-IDF,
pretty sure I should investigate long enough time before I post these questions in the forum. But your suggestion sometimes only take like 30sec. from your time (even the time for relax like me sometimes ) But it has the potential to save me many days to scratching my face and hair
I have a library (open62541) call Socket API of lwIP to make the tcp communications. It works just fine in a Project with WIFI, but the very same library (all toolchain and esp-idf are with the same version & git commit) won't work on the other project with ethernet. Here is where it get stucked:
Any idea for this?
Cheers
Gfast
pretty sure I should investigate long enough time before I post these questions in the forum. But your suggestion sometimes only take like 30sec. from your time (even the time for relax like me sometimes ) But it has the potential to save me many days to scratching my face and hair
I have a library (open62541) call Socket API of lwIP to make the tcp communications. It works just fine in a Project with WIFI, but the very same library (all toolchain and esp-idf are with the same version & git commit) won't work on the other project with ethernet. Here is where it get stucked:
Code: Select all
35836 if(setsockopt(newsock, SOL_SOCKET, SO_REUSEADDR,
35837 (const char *)&optval, sizeof(optval)) == -1) {
35838 UA_LOG_WARNING(UA_Log_Stdout, UA_LOGCATEGORY_NETWORK,
35839 "Could not make the socket reusable");
35840 CLOSESOCKET(newsock);
35841 return;
35842 }
Cheers
Gfast