Might be HW issue with your board. Could you please try to debug using https://github.com/espressif/esp-eth-dr ... phy_tester ? Ideally, run the pytest script. However, just note it was tested on Linux so far so you need to be on Linux.

Once you done, let me know the results.

Go over https://ww1.microchip.com/downloads/en/ ... 03048A.pdf, identify the clock mode you use in your HW setup and properly configure the example in Kconfig.

Hi, it seems to be more like a HW problem of your setup. 8 inches (~20 cm) long wires are too long. RMII CLK is 50 MHz so signal integrity is an concern, see https://resources.pcb.cadence.com/blog/2019-mii-and-rmii-routing-guidelines-for-ethernet I have experience that ~5 cm log wires still work OK ...

That W5500 error messages indicate that there is something wrong with SPI communication. How is your W5500 connected to ESP32-S3? Is it custom board or via wires? What Arduino version do you use? Is other device connected to the same SPI bus?

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...