espeasy keep reboot loop after Ethernet cable remove

[easpeasy-s]

It' a opnsense router and IPV4 and IPV6 are enabled on this interface.



Do you have dhcpv6 client on esp32 or use you another way to set the IPV6 address?

I can see ping from the router, but without response (from fw):

Code: Select all

IOT Out 2025-11-16T17:23:17 IPV6-ICMP fe80::2e0:b4ff:fe5b:a436  ff02::1 pass IPv6 RFC4890 requirements (ICMP)

eps32 log:

Code: Select all

05.723 : (306964) Info       | eth0: Got IPv6: IP Index: 0, Type: LINK_LOCAL, Zone: 2, Address: fe80:0000:0000:0000:32ed:a0ff:fee3:30dd
05.744 : (306900) Info       | firstLoopConnectionsEstablished
05.747 : (306880) Info       | Internal command: All checked OK
05.748 : (306924) Info       | EVENT: p2pNode#Connected=2,'sk_esp02','20251108'
27.769 : (306640) Info       | EVENT: p2pNode#Connected=1,'sk_esp01','20250430'
28.768 : (306768) Info       | eth0: Got IP: 172.23.20.2/24 GW: 172.23.20.254
28.769 : (306776) Info       | EVENT: eth0#Connected

[TD-er]

And IPv6 not working on RMII is exactly what I reported to be still an issue

[easpeasy-s]

Yes, so it confirm the problem with RMI.
I hope this will be resolved quickly.

By the way, do you have any idea when a new stable version of Espeasy will be released?

[TD-er]

Well I did discuss with Ton about what to do, make a new release first which is based on the current code in the 'mega' branch, or when the rewrite PR is ready to be merged.

Ton mentioned it makes more sense to make another release first as he also changed/fixed a lot of other things and then we should make a build with the network code fixes.
This way it is slightly easier to pinpoint any issues (if they may arise).

I will discuss with Ton what has to be merged to make a new build based on the 'mega' branch.

For the network rewrite, there is still something really odd about the WiFi state not being recognized causing the ESP32-S3 and P4 (mainly, not tested much on others) keep scanning while being connected to the access point.
Also sometimes the access point may not get found on the 1st scan and then it takes about 1 minute before a new attempt is being made.

[easpeasy-s]

Nice to see this project going ahead.

A separate publication would indeed make it easier to identify any potential problems.

I just tested an ESP32-S3-ETH board (with W5500 ETH).
It did not work with ESPEasy_mega_20251108_ESP32_beta version (didn’t initialise the network card) but with the ESP_Easy_mega_20251117_max_ESP32s3_16M8M_OPI_PSRAM beta it work (IPv4 and IPv6)

It would be nice to display the ipv6 global address on the node list on the main page
Cheers.

[TD-er]

[...]
It would be nice to display the ipv6 global address on the node list on the main page
Cheers.

Well I didn't include it in the node list for various reasons.
The main reason is that those pages are often posted by users as a screenshot and being a global IPv6 address, it depends on the user's router settings whether it is shielded properly from the internet.

I have not yet seen routers which do have global IPv6 addresses exposed to the internet by default, but better safe than sorry.

Also I have to re-think how to represent IP-addresses on the nodes list page.
- An interface may have upto 6 IPv6 addresses
- ESPEasy p2p should take into account via which interface the other node is reachable. The Link-local address with the zone would suffice.
- ESPEasy p2p itself must have an extra flag on which interface(s) it should be active as for example PPP (LTE modem) is completely unsuited to use for p2p
- IPv6 addresses can become quite long. Especially the global and unique link local ones as those typically do not have lots of zeroes which could be abbreviated.


Glad to see the SPI Eth device is now working on your S3 node.

FYI: I am now working on the remaining WiFi issues.
The RMII global IPv6 issue is still under investigation by Espressif.
There are some funky issues with ESP-HOSTED-MCU running on the ESP32-C6 on ESP32-P4 boards (e.g. erase all settings on P4 board and the C6 may still connect to WiFi as it is locally stored and not erased)
I did add (initial) support for ESP32-C61 and even the web flasher has been fixed to be able to flash ESP32-C61 and ESP32-C5 (status for C61: It boots, connects to WiFi and doesn't crash Nothing else was tested so far. )

[easpeasy-s]

OK. I understand the problem with GUA. It's more complicated than I thought.

My ESP32-P4-ETH board does not have a Wi-Fi/Bluetooth chip, so this may be a new case for espeasy to consider.

[TD-er]

That will work just fine.
The reason I know it will is that I do have a board here with P4 & ESP32-C5 as remote wifi chip.
Since that combination isn't supported jet by Arduino, I have to run that board with WiFi disabled.

Also there are boards out there which don't even have any ESP-Hosted-MCU firmware flashed on the 'wifi' board, so you need to flash those using an USB to serial adapter.
And the initial release version of the ESP-hosted-mcu firmware was running build 0.6.0.
This build was way too basic, so even querying not yet implemented functions (like "what is your build version?") caused the P4 to crash immediately.

There is a way to perform an OTA update from that firmware, but it got broken in the latest ESP-IDF 5.5 I'm now running.
So I need to fix that part too, or provide some intermediate build simply for OTA flashing from the 0.6.0 firmware...
And today I just got a test build from the Espressif guys which fixes some other issues with this hosted firmware, like that the wifi credentials were a bit too persistent. So even if you would wipe the P4 flash and start fresh with whatever firmware, the C6 would already be connected using previously used WiFi credentials.

[easpeasy-s]

Are you talking about these cards?
https://fr.aliexpress.com/item/1005009760226684.html
https://fr.aliexpress.com/item/1005009588981799.html

[TD-er]

Well those also seem to have the C6 for WiFi.
The boards I have here are the
- Waveshare ESP32-P4 nano (also one with camera, not yet used the cam)
- This one with display (not yet used)
- ESP32-P4 with ESP32-C5

Do not try the C5 variant as it isn't yet supported with the P4

I also have the official P4 dev kit with display and camera. Really nice kit, but way too bulky and too expensive.
And I have the WHY2025 badge (really happy I got one) which you can't ever buy as it was the badge of the hackers conference this summer.