Confusing DHCP-related Linux and Windows issues / differences
Posted: Wed Aug 14, 2024 11:24 pm
I have two (possibly related) questions:
1) In the ESP-IDF /examples/sta2eth code, I must ensure that I `#define MODIFY_DHCP_MSGS 1` at the beginning of /main/ethernet_iface.c. If I don't do this, my target ESP32's (or ESP32s3's) eth0 interface will not be assigned an IPv4 address, and I will not be able to connect my Linux host machine to it.
2) Additionally, if I am connecting the ESP32 to a Windows machine (10, 11, whatever) - rather than a Linux distro like Ubuntu, or indeed any Linux distro - I must ALSO `#define CONFIG_TINYUSB_NET_MODE_ECM_RNDIS 1` or yet again, the eth0 interface will not be assigned an IPv4 address, and again I'm unable to connect to it over the network.
Please could someone give me a reasonably straightforward explanation of what is going on here?
1) In the ESP-IDF /examples/sta2eth code, I must ensure that I `#define MODIFY_DHCP_MSGS 1` at the beginning of /main/ethernet_iface.c. If I don't do this, my target ESP32's (or ESP32s3's) eth0 interface will not be assigned an IPv4 address, and I will not be able to connect my Linux host machine to it.
2) Additionally, if I am connecting the ESP32 to a Windows machine (10, 11, whatever) - rather than a Linux distro like Ubuntu, or indeed any Linux distro - I must ALSO `#define CONFIG_TINYUSB_NET_MODE_ECM_RNDIS 1` or yet again, the eth0 interface will not be assigned an IPv4 address, and again I'm unable to connect to it over the network.
Please could someone give me a reasonably straightforward explanation of what is going on here?