Something’s been bugging me about the way eth0 isn’t shown as under DSA and has a different icon, yet it seems to perform well as a switch port. I’ve tested it with iperf3. I don’t recall clearly the results on OpenWRT. I think it suggested the performance as switchport as I didn’t remember it differently than EdgeMax, yet I definitely remember going back to EdgeMax (stock OS) to mess about and see if it worked any differently, and it performed just fine as a switch between eth0 and another port as well as two other ports to each other (ex. eth0 + eth2 vs eth1 + eth3). I mean, I didn’t take notes, but I think I’d remember if it were different–I did test both OS.
I’m using it partly as a router on a stick as some vlans/devices are on another switch that eth0 leads to including another VLAN between the ERX and the WAN that’s physically connected to that other switch. PC and some servers have a dedicated switchport on the ERX. I noticed the different icon, and it set me off to do testing in case I had to redo the topology.
Even though all 5 ports are connected to the internal hardware switch chip, this display is likely because eth0 is not part of the bridge in the default configuration. Instead, it's configured as if it is an individually routed port and used for the wan.
With that said, are you using eth0 as a wan, or is it part of br-lan in your configuration?
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:
Remember to redact passwords, MAC addresses and any public IP addresses you may have:
On this model the physical ports are named ethN to correspond with the labels on the case instead of the usual wan and lanN. This means that the internal connection which is usually named eth0 has to be called something else I think it is called dsa0. This connection is listed because it exists in th kernel, but it should not be referred to in any configs.
