The Industrial Raspberry Pi Forum

Hi,

When the router restarts, the Revpi Connect 4 looses connection. The lights on the ethernet port turn off on Port B (eth1). This does not happen on eth0.

I tried the same thing on an older Revpi Connect and I do not notice this problem.

I noticed there was a difference between eth0 and eth1 here:
/lib/udev/rules.d/50-revpi.rules I am using a static IP address. I used the same settings on Eth1 and Eth0.

I used a different IP address with no difference.
I tried having the router set the IP address and the Pi set to automatic and again no difference.

I tried updating everything and again no difference.
The issue persists with old and new kernels as well as old and new bootloaders.

Journalctl -r log: The pi will connect to the router after a restart and the lights will flash. Then a minute later, it will disconnect and lights will turn off. Unplugging and replugging the ethernet cable makes no difference. Once the pi has failed, there are two ways to recover the Pi.
1. restart the pi
2. connect another network device, lights will flash and then connect the original router.

Hey in06khattab, thanks for your detailed report. Please send me an SOS report:
https://kunbus-gmbh.atlassian.net/servi ... 2036400208

Hi in06khattab, I have an idea for a workaround. If you don't mind testing it - if you don't need link local fallback, the easiest workaround consists of removing that connection. As a result, DHCP is given the lowest priority and is thus triggered during link-up.

Hi Derk,

Thank you for replying. Do you mean removing the eth0 connection?

The connection is called "Link-local eth0 (fallback)", so please try to remove that connection: This is what it looks like for me after removal:

Thank you Dirk

I removed the link local and the issue still appears when I am connected to eth1. The network disconnects when the router reboots and the lights on the ethernet port do not light up any more. This does not happen on eth0. I tried this test with a fresh bullseye image and the same thing occurred.

Hi in06khattab I am dismayed to hear this, can you send me an SOS report?
https://kunbus-gmbh.atlassian.net/servi ... 2036400208

Additionally, a Wireshark trace or a tcpdump of the appropriate interface would sure be helpful see here:
https://kunbus-gmbh.atlassian.net/servi ... 1400012823

In the meantime I am trying to reproduce the problem with a test setup. Thank you very much.

Hi Dirk,

Attached is the SOS report before and after the router restart and the wireshark capture.
Kind regards,
Ahmad

Hi Ahmad, thank you very much for the extensive data I have gratefully received. You are using an outdated system and kernel.
Please update your system.

The best case we see here is you test with a fresh installation of the latest Bullseye release because a lot has changed in the network configuration over time.

You can do this by following the steps of the Revolution Pi Checklist.
Thank you