What IDF version do you use? And what do you mean by "the device is not connected to the network"? Do you mean the cable is unplugged from WT-32-S1? Could you please be more specific about your setup?

IDFv3 is super old and has completely different structure of the Ethernet driver. It would be probably easier to start writing the whole new driver for KS8863 rather than trying to modify the current one, I'm afraid... The only recommendation is to upgrade to higher IDF version. If you are developin...

Sorry for late and short answer. However, I'm super busy with other tasks... Try to go over ESP-NETIF documentation or go over examples. If you don't find anything, I think stopping and starting the netif with different configuration should work. Here is example https://github.com/espressif/esp-idf/...

Here https://github.com/espressif/esp-eth-dr ... rver.c#L48 is example how to configure DHCP Server. Please don't use `ESP_NETIF_AUTOUP`. That's reserved for WiFi AP mode.

I don't know details about your code so I cannot give you much more detailed answer. However, you need to free memory allocated for Ethernet frames (https://github.com/espressif/esp-idf/bl ... esp.c#L337)

Once you open tap interface for specific ethertype, these frames are then only accepted by the tap interface. They are not passed to the IP stack. It's described at: https://docs.espressif.com/projects/esp-idf/en/stable/esp32/api-reference/network/esp_netif.html#e-esp-netif-l2-tap-interface Please l...

Do I understand it correctly that your board is able to boot now? You just don't get IP address? If so, try to download this application https://github.com/espressif/esp-eth-dr ... phy_tester and follow the instructions. Just note it currently works (was tested) only on Linux.

Check if MDIO and MDC GPIOs are properly configured.
Check the PHY address is correctly set in code and in PHY device via it's bootstraps or set PHY address to -1 (auto) in menuconfig.
Probe the MDIO and MDC with oscilloscope if you see any signal.

The observed issue with generated CLK stability is unfortunately a real issue... ESP32 cannot be used as RMII CLK source when Wi-Fi is used. The only workaround is to not use Wi-Fi or use external source of the CLK :( We are deeply sorry for trouble caused. We at least updated errata https://www.esp...

The observed issue with generated CLK stability is unfortunately a real issue... ESP32 cannot be used as RMII CLK source when Wi-Fi is used. The only workaround is to not use Wi-Fi or use external source of the CLK :( We are deeply sorry for trouble caused. We at least updated errata https://www.esp...