Kernel log shows (wrongly) LAN is blocking

Pi4b running OpenWrt 21.02.0-rc3 r16172-2aba3e9784 in the kernel log I see a number of events

[1129519.715964] br-lan: port 1(eth0) entered blocking state
[1129519.715971] br-lan: port 1(eth0) entered forwarding state
[1129550.435323] bcmgenet fd580000.ethernet eth0: Link is Down
[1129550.435738] br-lan: port 1(eth0) entered disabled state
[1129554.531410] bcmgenet fd580000.ethernet eth0: Link is Up - 1Gbps/Full - flow control off
[1129554.532626] br-lan: port 1(eth0) entered blocking state
[1129554.532633] br-lan: port 1(eth0) entered forwarding state
[1129795.174012] bcmgenet fd580000.ethernet eth0: Link is Down
[1129795.174524] br-lan: port 1(eth0) entered disabled state
[1129799.271591] bcmgenet fd580000.ethernet eth0: Link is Up - 1Gbps/Full - flow control off
[1129799.271635] br-lan: port 1(eth0) entered blocking state
[1129799.271642] br-lan: port 1(eth0) entered forwarding state

I've have a script running on my PiHole that constantly checks both my internet connection and the connection to the router and no drops detected, the router ping check looks good too so I think that this is a false alarm. I thought I had tracked it down to when the cron job runs which takes a snapshot and saves to my NAS, however, whilst that will trigger the events perhaps linked to dd running and saving to a networked drive they also happen at other times.

This I suppose is really for information and if there is help needed tracking this down a suggestion of logs to get.

I have this on all my units with 21.02. 19.07 and before never showed this.
But this phenomena has always been in my TP-Switch original firmware log, and my new Ubiqinti switch log.
As you say it is a lot of log text and it doesn’t really say the much.
If I have a computer and boot it there is also a lot of log text for the connected port.

Another thing that seems to also trigger these entries is making use of the wireguard VPN. As far as I can see this does not cause any break in service.

1 Like