LAN ports go off sometimes- O2box 6431

Installing and Using OpenWrt Network and Wireless Configuration
1

This is observed on the o2box 6431 and OpenWrt 24.10.2 (r28739-d9340319c6)

Since some years (also before using this release) I observed that from time to time, the 4 lan ports of the device ‘go off’ and then only Wi-Fi is working for network. This means that the switch seems to be inactive. LEDs are off, plug-in or -out of a network cable does nothing.

After looking at the log I didn’t find any hint, but I am not an expert either. I did not yet find any coincidence that happens also when this is happening.

But I also did not yet find a good solution to remedy: restarting the LAN network does not help, and restarting this or that service also did not.

So the question is two-fold:

  • how to stop the internal switch, or the LAN ports, or whatever is the culprit to switch lan ports to deactivated state?
  • how to restart the internal switch, or device, or … well, whatever in details was shut off…?

greetings

2

now the picture is a bit more complete:

today the device rebooted itself, and, suprise: the two lan ports which are connected seemed to be off. No LED activity, no anything. But plugging the cables into the two other ports (3+4 from 1+2) showed that those ports are working. Indeed the ports 1+2 never came back to live.

Until another reboot: then it was vice versa: ports 3+4 where the cables where plugged where off, and putting them into 1+2 alighted those ports.

here is a log extract:

[    2.549589] gswip 1e108000.switch: configuring for fixed/internal link mode
[    2.555834] gswip 1e108000.switch: Link is Up - 1Gbps/Full - flow control off
[    2.642085] gswip 1e108000.switch wan (uninitialized): PHY [1e108000.switch-mii:01] driver [ICPlus IP101A] (irq=POLL)
[    2.658329] gswip 1e108000.switch lan2 (uninitialized): PHY [1e108000.switch-mii:11] driver [Intel XWAY PHY22F (xRX v1.2 integrated)] (irq=POLL)
[    2.676666] gswip 1e108000.switch lan1 (uninitialized): PHY [1e108000.switch-mii:12] driver [Intel XWAY PHY22F (xRX v1.2 integrated)] (irq=POLL)
[    2.690232] gswip 1e108000.switch lan4 (uninitialized): no phy at 4
[    2.695172] gswip 1e108000.switch lan4 (uninitialized): failed to connect to PHY: -ENODEV
[    2.703317] gswip 1e108000.switch lan4 (uninitialized): error -19 setting up PHY for tree 0, switch 0, port 4
[    2.713505] gswip 1e108000.switch lan3 (uninitialized): no phy at 5
[    2.719448] gswip 1e108000.switch lan3 (uninitialized): failed to connect to PHY: -ENODEV
[    2.727713] gswip 1e108000.switch lan3 (uninitialized): error -19 setting up PHY for tree 0, switch 0, port 5

and later, plugging on off from port 2 and into port 3 and back into port 2:

[ 9488.942346] gswip 1e108000.switch lan2: Link is Down
[ 9488.946329] br-lan: port 2(lan2) entered disabled state
[ 9498.382286] gswip 1e108000.switch lan2: Link is Up - 100Mbps/Full - flow control rx/tx
[ 9498.388937] br-lan: port 2(lan2) entered blocking state
[ 9498.394141] br-lan: port 2(lan2) entered forwarding state

Yes, the other port, number 3, is not even mentioned in the kernel log.
Does that make even sense?

3

Lan3 didn't come up, and there is probably no such interface in the system. This is why you don't see it in the log. The real cause of the problem is why PHY doesn't come up after a reboot.

4

Consider creating an issue on GitHub.

5

I don’t think you’re the only one to report this problem with the lantiq target but i’m too lazy to search for the existing threads about it.

6

well, the problem I described in the second post seems to be different from the first one which was just that the switch seems to go deactivated after some uptime (can be days to weeks).

Maybe it also has to do something with the image I built using imagebuilder… I will try and check with other images before reporting more :person_shrugging: