TPLink WR1043NDv2 Switch Labels are Wrong

For Developers
1

The Switch labels are wrong on the model": "TP-Link TL-WR1043ND v2",
Currently listed as:
CPU (eth1) CPU (eth0) LAN 1 LAN 2 LAN 3 LAN 4 WAN

They are in fact

CPU (eth1) WAN (eth0) LAN4 LAN3 LAN2 LAN1 CPU
0 6 1 2 3 4 5

Is it possible to fix the labels in the build?

1 Like
2

yeah here: https://github.com/openwrt/openwrt/blob/4b907e69ea58fc0ba35fd1755dc4ba22262af3a4/target/linux/ath79/generic/base-files/etc/board.d/02_network#L566

1 Like
3

Please show ubus call system board and swconfig dev switch0 show | grep -A1 ^[a-zA-Z]

eth0 is 0 and eth1 is 6

then eth1.2 is linked to one mid-port in separate vlan others to eth0.1

…

4

ubus call system board
{
"kernel": "6.6.104",
"hostname": "OpenWrt",
"system": "Qualcomm Atheros QCA9558 ver 1 rev 0",
"model": "TP-Link TL-WR1043ND v2",
"board_name": "tplink,tl-wr1043nd-v2",
"rootfs_type": "squashfs",
"release": {
"distribution": "OpenWrt",
"version": "24.10.3",
"revision": "r28872-daca7c049b",
"target": "ath79/generic",
"description": "OpenWrt 24.10.3 r28872-daca7c049b",
"builddate": "1758316778"
}
}

swconfig dev switch0 show | grep -A1 ^[a-zA-Z]
Global attributes:
enable_vlan: 1
--
Port 0: MAC c0:4a:xx:xx:xx:xx
Port 4: MAC 00:22:xx:xx:xx:xx
Port 5: MAC 00:e0:xx:xx:xx:xx
Port 5: MAC 58:9c:xx:xx:xx:xx
Port 5: MAC 58:9c:xx:xx:xx:xx
Port 6: MAC c0:4a:xx:xx:xx:xx

--
Port 0:
mib: ???
--
Port 1:
mib: ???
--
Port 2:
mib: ???
--
Port 3:
mib: ???
--
Port 4:
mib: ???
--
Port 5:
mib: ???
--
Port 6:
mib: ???
--
VLAN 1:
vid: 1
--
VLAN 2:
vid: 2
--
VLAN 3:
vid: 10
--
VLAN 4:
vid: 26

	tplink,tl-wr1043nd-v2|\
	ucidef_add_switch "switch0" \
	FROM: "0@eth1" "1:lan:4" "2:lan:3" "3:lan:2" "4:lan:1" "5:wan" "6@eth0"

port 6 represented in the UI as CPU(eth0) is in fact the physical WAN connector
port 5 represented in the UI as WAN is in fact the CPU trunk 
			
	TO: "0@eth1" "1:lan:4" "2:lan:3" "3:lan:2" "4:lan:1" "5:eth0" "6@wan"

I verified per the below configuration.

If WAN cable is removed;

  • connectivity between the LAN client and box remains in below config
  • If eth(0) is tagged for vlan10/26 and WAN is off, connectivity between the LAN client and box is lost

Conclusion is the WAN is therefore the CPU truck, and the CPU(eth0) is the WAN port.
Which also explains why the default config has eth0.2 as the wan interface.

image
image972×384 28.7 KB

5

I'm not quite following what is connected to each of the ports and what is connecting upstream vs downstream.

One thing I will note is that it is unusual to use the CPU untagged... I don't think it will cause issues, but the recommended configuration is to have the CPUs tagged.

But let's run the following test:

  1. Create a backup
  2. Reset the WR1043NDv2 to defaults
  3. Connect a computer to one of the lan ports (no other connections on the device aside from power), login
  4. Post the default /etc/config/network config file here
  5. Observe and record the behavior of the pseudo-physical vs physical port mapping in the switch page by connecting your computer to each of the lan ports in turn (i.e. does port lan1 on the hardware match port lan1 on the switch page and so on).
  6. connect your computer to the wan port... at this point, you shouldn't have access anymore. Please verify this
  7. assuming 6 is as expected, connect your computer back to the lan port and then attach the wan port to an upstream network that provides dhcp. You should see the pesudo-physical wan port indicator show that it is connected and your 1043NDv2 should get an IP on the wan. Please confirm.