Wan port seems to be dependent on lan

AndrewZ · May 26, 2026, 6:34pm

Can someone help me understand the following behaviour - once one of the LAN ports is disconnected, WAN goes down as well.
The device in question is ZBT WE1326 running 24.10.3 (this is a remote device that cannot be upgraded at this time). There is nothing special with this device configuration.

Tue May 26 02:23:31 2026 kern.info kernel: [129743.925971] mt7530-mdio mdio-bus:1f lan2: Link is Down
Tue May 26 02:23:31 2026 kern.info kernel: [129743.931371] br-lan: port 2(lan2) entered disabled state
Tue May 26 02:23:31 2026 daemon.notice netifd: Network device 'lan2' link is down
Tue May 26 02:23:31 2026 kern.info kernel: [129744.521914] mtk_soc_eth 1e100000.ethernet wan: Link is Down
Tue May 26 02:23:32 2026 daemon.notice netifd: Network device 'wan' link is down
Tue May 26 02:23:32 2026 daemon.notice netifd: Network alias 'wan' link is down
Tue May 26 02:23:32 2026 daemon.notice netifd: Interface 'wan6' has link connectivity loss
Tue May 26 02:23:32 2026 daemon.notice netifd: Interface 'wan' has link connectivity loss

psherman · May 26, 2026, 6:35pm

Let's start by looking at the complete config...

Please connect to your OpenWrt device using ssh and copy the output of the following commands and post it here using the "Preformatted text </> " button (red circle; this works best in the 'Markdown' composer view in the blue oval):

Remember to redact passwords, VPN keys, MAC addresses and any public IP addresses you may have:

ubus call system board
cat /etc/config/network
cat /etc/config/wireless
cat /etc/config/dhcp
cat /etc/config/firewall

egc · May 26, 2026, 6:38pm

Wild guess
Switch architecture combined 5 port switch with wan and lan split by vlans e.g. eth0.1 eth0.2

AndrewZ · May 26, 2026, 7:02pm

Wan is not a member of the switch as I can see:

github.com/openwrt/openwrt

target/linux/ramips/dts/mt7621_zbtlink_zbt-wexx26.dtsi

v24.10.3


      
          
          &ethphy4 {
          	/delete-property/ interrupts;
          };
          
          &gmac0 {
          	nvmem-cells = <&macaddr_factory_e000>;
          	nvmem-cell-names = "mac-address";
          };
          
          &gmac1 {
          	status = "okay";
          	label = "wan";
          	phy-handle = <&ethphy4>;
          
          	nvmem-cells = <&macaddr_factory_e006>;
          	nvmem-cell-names = "mac-address";
          };
          
          &pcie {
          	status = "okay";

Verylongusername · May 27, 2026, 5:44am

Hi,
I have 3 we1326, two of them hw. rev5 and one hw. rev1, and never experienced such issue. I am running 25.12 in two of them and 24.10 in the other.
Could it be a bug in the 24.10 service release you are running? Mine is 24.10 snapshot, commit cc1b909, its prior to your 24.10.3. Anyway my 25.12 ones have no issue either