WRT1900ACS LAN Port only 100mbps?

Hi

I am trying to test local speed between my computer and WRT1900ACS running 19.0.7. I am not able to go past 93~95 mbps using iperf3. The "Switch" page is going the port as 100baseT Full Duplex. All of the WRT1900ACS ports are Gigabit. Windows 10 is detecting the connection as 100 mbps as well

The connections are as follow
Intel(R) 82579V Gigabit (PC Ethernet Port)
A long CAT6 Cable with an RJ45 jack on one end and a CAT6 keystone on the other.
A CAT6E cable between the keystone and the WRT1900ACS port.

I run iperf3 -s on OpenWRT and iperf3 -c XXX.XXX.XXX.XXX -t iperf3
What am I missing here? And why OpenWRT is displaying the LAN ports are 100baseT?

While there is always the possibility of interoperability issues between die different network cards involved, this would be rather unlikely (especially with common stuff like Intel vs Marvell). Cabling issues are way more likely, so I'd recommend to check that first, by doing a new test with another cable (just get a short patch cable and test it closer to each other, not that the distance (assuming <100m) would be a problem, but the connectors or cables - and I don't expect you have another long enough cable at hand).

1 Like

I have tested using another CAT5E cable (10m / RJ45 plugs at both ends) and it is the same problem. I tried to force 1Gbps full duplex mode from the Intel Chipset driver, but it shows the cable as unplugged. The WRT1900ACS just blinks the Ethernet port led on and off every 3 seconds.

I tested with another 1m CAT5E cable. Same
I tested with the cable than came with the router. Same.

Am I really unlucky with all these cables?

You could SSH into your router via terminal or command prompt on Windows using SSH root@192.168.1.1 and the install ethtool

opkg install ethtool and then run ifconfig to list all of your interfaces. You can then run ethtool on the desired interface and it may show you some extra information.

br-lan Link encap:Ethernet HWaddr XX:XX:XX:XX:XX:XX
inet addr:192.168.2.1 Bcast:192.168.2.255 Mask:255.255.255.0
inet6 addr: xxxx:xxxx:xxxx:xxxx/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1492 Metric:1
RX packets:23607 errors:0 dropped:4 overruns:0 frame:0
TX packets:24329 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:4448298 (4.2 MiB) TX bytes:31215817 (29.7 MiB)

eth0 Link encap:Ethernet HWaddr XX:XX:XX:XX:XX:XX
inet6 addr: xxxx:xxxx:xxxx:xxxx/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:19551 errors:0 dropped:0 overruns:0 frame:0
TX packets:18313 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:532
RX bytes:3932091 (3.7 MiB) TX bytes:24746732 (23.5 MiB)
Interrupt:37

eth0.1 Link encap:Ethernet HWaddr XX:XX:XX:XX:XX:XX
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:19307 errors:0 dropped:15 overruns:0 frame:0
TX packets:18293 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:3570413 (3.4 MiB) TX bytes:24670631 (23.5 MiB)

eth1 Link encap:Ethernet HWaddr XX:XX:XX:XX:XX:XX
inet6 addr: xxxx:xxxx:xxxx:xxxx/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:26998 errors:0 dropped:0 overruns:0 frame:0
TX packets:18874 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:532 <---- Why not 1000? SQM is already disabled
RX bytes:22912874 (21.8 MiB) TX bytes:4294658 (4.0 MiB)
Interrupt:36

eth1.2 Link encap:Ethernet HWaddr XX:XX:XX:XX:XX:XX
inet addr:192.168.1.2 Bcast:192.168.1.255 Mask:255.255.255.0
inet6 addr: xxxx:xxxx:xxxx:xxxx/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:24745 errors:0 dropped:0 overruns:0 frame:0
TX packets:18867 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:22329722 (21.2 MiB) TX bytes:4218364 (4.0 MiB)

lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:65536 Metric:1
RX packets:184 errors:0 dropped:0 overruns:0 frame:0
TX packets:184 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:16149 (15.7 KiB) TX bytes:16149 (15.7 KiB)

wlan0 Link encap:Ethernet HWaddr XX:XX:XX:XX:XX:XX
inet6 addr: xxxx:xxxx:xxxx:xxxx/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:3291 errors:0 dropped:0 overruns:0 frame:0
TX packets:8265 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:734776 (717.5 KiB) TX bytes:6738572 (6.4 MiB)

wlan1 Link encap:Ethernet HWaddr XX:XX:XX:XX:XX:XX
inet6 addr: xxxx::xxxx:xxxx:xxxx:xxxx/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:1834 errors:0 dropped:0 overruns:0 frame:0
TX packets:3386 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:322703 (315.1 KiB) TX bytes:951102 (928.8 KiB)

So what shall I be checking for here?

Just for the sake of testing, perhaps connect your WAN port with the port you see affected (yes, loops are bad - but we're just interested if it negotiates the correct link speed here, not to actually pass any packets through).

I have Archer VR600 running. Attaching the cable in the first post between both routers went undetected. The WRT port led didn't even go up, but when connected between the WRT and a switch or another PC, it negotiates on 100 mbps. Very weird behavior. Connecting the CAT5E 10m cable, both routers negotiated on a 1000 mbps. The same cable connected to the Gigabit Ethernet Card on the PC negotiates only on 100 mbps.

If you don't have any testing equipment, like cable tester, your only option is to try different combinations of ports and cables until you see what can be the culprit.
E.g port 1 on router and cable a towards PC. Then port 2 on router and cable a towards PC. If the problem remains, change cable. If not, then you might have a faulty port on router. If it isn't router port or cable, check the port on the PC.

1 Like

I have this cable tester
image
I used it on my cable and they are okay.
If you mean a cable tester of some other capabilities, then I don't have.

This one shows at least if there are cuts or shortcuts. Nonetheless proceed with testing the router and PC ports.

Look in the plugs confirm the wire colors are in the standard order-- a DC tester won't find split pairs.

Another common problem is for the RJ-45 contact points to be unevenly set, or the plastic comb in between them distorted, so they don't make contact all the time. Or they might make contact all the time in one device but never in another one.

1 Like
  • Why/how did you make the MTU of your br-lan 1492?
  • Can you also show the output of swconfig dev switch0 show | grep 'link: port:'
1 Like