Hallo,
I have a fritzbox 4020 with OpenWRT. So far almost no clients, just me testing around.
I noticed that the following lines appeared about 6 times within 30 min. Before that, nothing at all for the whole day. And after that, it's been about 40min, it hasn't come back again. It looks like a switch port which changes state to avoid short circuit or something. I don't understand why this device is doing this. I have several devices, eth0.11 and eth0.15 are identically configured, but eth0.15 doesn't do this.
I would appreciate if someone could please tell me why it was doing this. I was connecting over wireguard from another net and looking at luci, didn't do anything with eth0.11. It says "port 1", but the physical port 1 on the router doesn't have eth0.11. It's just untagged eth0.16.
Sun May 29 21:43:12 2022 kern.info kernel: [729978.900591] device eth0.11 left promiscuous mode
Sun May 29 21:43:12 2022 kern.info kernel: [729978.905672] br-11: port 1(eth0.11) entered disabled state
Sun May 29 21:43:12 2022 kern.info kernel: [729978.927040] br-11: port 1(eth0.11) entered blocking state
Sun May 29 21:43:12 2022 kern.info kernel: [729978.932803] br-11: port 1(eth0.11) entered disabled state
Sun May 29 21:43:12 2022 kern.info kernel: [729978.938837] device eth0.11 entered promiscuous mode
Sun May 29 21:43:12 2022 kern.info kernel: [729978.944328] br-11: port 1(eth0.11) entered blocking state
Sun May 29 21:43:12 2022 kern.info kernel: [729978.950056] br-11: port 1(eth0.11) entered forwarding state
It looks like normal operating procedure from the introduction of 21.02 with kernel 5.4.
This text comes everytime a ethernet connection is established. So did you reboot the computer or reset the ethernet connector on the computer or put the computer to sleep or upgraded the computer or anything else?
2 Likes
Port1 in the log and port1 in luci and port1 on the hardware doesn’t necessarily have anything to do with each other. At least not if you have a Edgerouter!
Easiest way to find out the port numbers in the log for
is to connect a computer to each port one at a time and watch the log what port number every connector has in the log.
@flygarn12
Thank you for your reply! It seems that at least it's harmless, then? The traffic wont get blocked or anything if this message is showing? Is that right?
However, I haven't done anything with ethernet connection. The connected devices are access points (trunk eth0.11, 0.15, and 0.16) and Raspberry pi (0.16 untagged). I was in another building on a different net, accessed to that OpenWRT over wireguard, and was trying to figure out how to make site-to-site. But didn't restart any of these devices.
I have only one port that has eth0.11 on it, (port "2" on the router), so I guess that one must be called port 1 then. But like I said, I don't see any reason why these messages came, particularly if there wasn't any for eth0.15 and eth0.16...
O I forgot to mention, the APs are over a 16-port switch, so the switch is the one that is directly connected to the router over a port, that got eth0.11. I haven't restarted the switch at all....
@flygarn12
I restarted the switch connected to a port to see what number it got on the log, but in the system log, nothing appeared.....
Now I looked at the kernel log for the first time, there are a lot more of them, with various devices. I see that port1 seems to mean just eth, and port 2 is wlan.
While the other devices have this lines just once, perhaps in connection with something I have done, what makes br-11 odd is, that it repeated 6 times, and that they also showed up in the system log. On to other hand, on the kernel log, there is no date, so it may be also the case, that they did appear on sys log, I just wasn't looking.