Model Ubiquiti EdgeRouter 4
Architecture UBNT_E300 (CN7030p1.2-1000-AAP)
Firmware Version OpenWrt 21.02-SNAPSHOT r16232-febf6db0d0 / LuCI openwrt-21.02 branch git-21.188.55099-e52e1de
The forum post:
[[https://forum.openwrt.org/t/edgerouter-4-port-numbers-are-a-real-mess-in-the-log/101102/2|External Link]]
It seems that port numbers in system log is out of synck with hardware port numbers, for example this log text: switch0: port 1(lan0)
This bug makes log errors like Port 1 receive error code 7, packet dropped
very hard to find if the actual port is false flagged.
kern.notice kernel: [ 4979.972921] lan0: Link down
kern.info kernel: [ 4979.975979] switch0: port 1(lan0) entered disabled state
daemon.notice netifd: Network device 'lan0' link is down
kern.notice kernel: [ 5011.719291] lan0: 1000 Mbps Full duplex, port 1, queue 1
kern.info kernel: [ 5011.724648] switch0: port 1(lan0) entered blocking state
kern.info kernel: [ 5011.729976] switch0: port 1(lan0) entered forwarding state
daemon.notice netifd: Network device 'lan0' link is up
kern.notice kernel: [ 5035.272920] lan0: Link down
kern.info kernel: [ 5035.275978] switch0: port 1(lan0) entered disabled state
daemon.notice netifd: Network device 'lan0' link is down
kern.info kernel: [ 3594.470962] switch0: port 4(lan3) entered disabled state
daemon.notice netifd: Network device 'lan3' link is down
kern.notice kernel: [ 3615.941460] lan1: 1000 Mbps Full duplex, port 2, queue 2
kern.info kernel: [ 3615.946870] switch0: port 2(lan1) entered blocking state
kern.info kernel: [ 3615.952201] switch0: port 2(lan1) entered forwarding state
daemon.notice netifd: Network device 'lan1' link is up
The text was updated successfully, but these errors were encountered:
flygarn12:
Model Ubiquiti EdgeRouter 4
Architecture UBNT_E300 (CN7030p1.2-1000-AAP)
Firmware Version OpenWrt 21.02-SNAPSHOT r16232-febf6db0d0 / LuCI openwrt-21.02 branch git-21.188.55099-e52e1de
The forum post:
[[https://forum.openwrt.org/t/edgerouter-4-port-numbers-are-a-real-mess-in-the-log/101102/2|External Link]]
It seems that port numbers in system log is out of synck with hardware port numbers, for example this log text:
switch0: port 1(lan0)
This bug makes log errors like
Port 1 receive error code 7, packet dropped
very hard to find if the actual port is false flagged.
kern.notice kernel: [ 4979.972921] lan0: Link down
kern.info kernel: [ 4979.975979] switch0: port 1(lan0) entered disabled state
daemon.notice netifd: Network device 'lan0' link is down
kern.notice kernel: [ 5011.719291] lan0: 1000 Mbps Full duplex, port 1, queue 1
kern.info kernel: [ 5011.724648] switch0: port 1(lan0) entered blocking state
kern.info kernel: [ 5011.729976] switch0: port 1(lan0) entered forwarding state
daemon.notice netifd: Network device 'lan0' link is up
kern.notice kernel: [ 5035.272920] lan0: Link down
kern.info kernel: [ 5035.275978] switch0: port 1(lan0) entered disabled state
daemon.notice netifd: Network device 'lan0' link is down
kern.info kernel: [ 3594.470962] switch0: port 4(lan3) entered disabled state
daemon.notice netifd: Network device 'lan3' link is down
kern.notice kernel: [ 3615.941460] lan1: 1000 Mbps Full duplex, port 2, queue 2
kern.info kernel: [ 3615.946870] switch0: port 2(lan1) entered blocking state
kern.info kernel: [ 3615.952201] switch0: port 2(lan1) entered forwarding state
daemon.notice netifd: Network device 'lan1' link is up
The text was updated successfully, but these errors were encountered: