What's new

RT-AX58U - WAN Disocnnecting and Reconnecting at Lower Speed

  • SNBForums Code of Conduct

    SNBForums is a community for everyone, no matter what their level of experience.

    Please be tolerant and patient of others, especially newcomers. We are all here to share and learn!

    The rules are simple: Be patient, be nice, be helpful or be gone!

Izno

New Around Here
Hello!

I'm a bit new to all this, and trying to find the issue here. I recently upgraded to 1000 up/down from 100 up/down. I'm running into an issue where my WAN and network will get the normal 1000 mbps connection, but after a seemingly random amount of time (has been 30 minutes, has been 12 hours) the WAN will go down and come back up at 100 mbps. If I reset my ONT or router, it will usually fix and come back up at 1000 mbps but then will go down and repeat the cycle.

My setup is my ISP ONT to my RT-AX58U router, to a switch, to my computers. ISP is saying it's on my end and not theirs. I've tested the cables from router to switch and switch to computers, they seem fine. I've also changed the ports I'm using, and still run into the issue. Below is what I'm seeing happen in the sys log:

Code:
Jun 13 07:23:06 WAN Connection: WAN(0) link down.
Jun 13 07:23:07 kernel: ^[[0;33;41m[ERROR archer] archer_mcast_activate,577: ADD_PORT: WLAN SSID has already been added: egress_port 7, current 0x0001, new 0x0001^[[0m
Jun 13 07:23:07 kernel: ^[[0;33;41m[ERROR archer] archer_mcast_activate,577: ADD_PORT: WLAN SSID has already been added: egress_port 7, current 0x0001, new 0x0001^[[0m
Jun 13 07:23:07 kernel: eth4 (Int switch port: 4) (Logical Port: 4) (phyId: c) Link Up at 1000 mbps full duplex
Jun 13 07:23:12 WAN Connection: WAN(0) link up.
Jun 13 07:23:12 rc_service: wanduck 1444:notify_rc restart_wan_if 0
Jun 13 07:23:15 wan: finish adding multi routes
Jun 13 07:23:15 miniupnpd[19676]: shutting down MiniUPnPd
Jun 13 07:23:16 miniupnpd: it is advised to use network interface name instead of 192.168.50.1/255.255.255.0
Jun 13 07:23:16 miniupnpd[22111]: HTTP listening on port 47868
Jun 13 07:23:16 kernel: Archer TCP Pure ACK Enabled
Jun 13 07:23:16 dhcp client: bound X/255.255.255.0 via X for 1800 seconds.
Jun 13 07:23:16 miniupnpd[22111]: Listening for NAT-PMP/PCP traffic on port 5351
Jun 13 07:23:16 kernel: ^[[0;33;41m[ERROR archer] archer_mcast_activate,577: ADD_PORT: WLAN SSID has already been added: egress_port 6, current 0x0001, new 0x0001^[[0m
Jun 13 07:23:16 kernel: ^[[0;33;41m[ERROR archer] archer_mcast_activate,577: ADD_PORT: WLAN SSID has already been added: egress_port 6, current 0x0001, new 0x0001^[[0m
Jun 13 07:23:20 WAN Connection: WAN was restored.
Jun 13 07:23:27 kernel: eth4 (Int switch port: 4) (Logical Port: 4) (phyId: c) Link DOWN.
Jun 13 07:23:29 kernel: eth4 (Int switch port: 4) (Logical Port: 4) (phyId: c) Link Up at 1000 mbps full duplex
Jun 13 07:23:30 kernel: eth4 (Int switch port: 4) (Logical Port: 4) (phyId: c) Link DOWN.
Jun 13 07:23:30 kernel: ^[[0;33;41m[ERROR archer] archer_mcast_activate,577: ADD_PORT: WLAN SSID has already been added: egress_port 6, current 0x0001, new 0x0001^[[0m
Jun 13 07:23:30 kernel: ^[[0;33;41m[ERROR archer] archer_mcast_activate,577: ADD_PORT: WLAN SSID has already been added: egress_port 6, current 0x0001, new 0x0001^[[0m
Jun 13 07:23:33 kernel: eth4 (Int switch port: 4) (Logical Port: 4) (phyId: c) Link Up at 1000 mbps full duplex
Jun 13 07:23:34 kernel: eth4 (Int switch port: 4) (Logical Port: 4) (phyId: c) Link DOWN.
Jun 13 07:23:35 WAN Connection: WAN(0) link down.
Jun 13 07:23:37 kernel: eth4 (Int switch port: 4) (Logical Port: 4) (phyId: c) Link Up at 1000 mbps full duplex
Jun 13 07:23:38 kernel: eth4 (Int switch port: 4) (Logical Port: 4) (phyId: c) Link DOWN.
Jun 13 07:23:40 kernel: eth4 (Int switch port: 4) (Logical Port: 4) (phyId: c) Link Up at 1000 mbps full duplex
Jun 13 07:23:42 kernel: eth4 (Int switch port: 4) (Logical Port: 4) (phyId: c) Link DOWN.
Jun 13 07:23:44 kernel: eth4 (Int switch port: 4) (Logical Port: 4) (phyId: c) Link Up at 1000 mbps full duplex
Jun 13 07:23:45 WAN Connection: WAN(0) link up.
Jun 13 07:23:45 rc_service: wanduck 1444:notify_rc restart_wan_if 0
Jun 13 07:23:46 kernel: ^[[0;33;41m[ERROR archer] archer_mcast_activate,577: ADD_PORT: WLAN SSID has already been added: egress_port 7, current 0x0001, new 0x0001^[[0m
Jun 13 07:23:46 kernel: ^[[0;33;41m[ERROR archer] archer_mcast_activate,577: ADD_PORT: WLAN SSID has already been added: egress_port 7, current 0x0001, new 0x0001^[[0m
Jun 13 07:23:46 kernel: eth4 (Int switch port: 4) (Logical Port: 4) (phyId: c) Link DOWN.
Jun 13 07:23:47 kernel: eth4 (Int switch port: 4) (Logical Port: 4) (phyId: c) Link Up at 100 mbps full duplex
Jun 13 07:23:47 wan: finish adding multi routes
Jun 13 07:23:48 miniupnpd[22111]: shutting down MiniUPnPd
Jun 13 07:23:48 miniupnpd: it is advised to use network interface name instead of 192.168.50.1/255.255.255.0
Jun 13 07:23:48 miniupnpd[22477]: HTTP listening on port 42005
Jun 13 07:23:48 kernel: Archer TCP Pure ACK Enabled
Jun 13 07:23:48 dhcp client: bound X/255.255.255.0 via X for 1800 seconds.
Jun 13 07:23:48 miniupnpd[22477]: Listening for NAT-PMP/PCP traffic on port 5351
Jun 13 07:23:48 kernel: ^[[0;33;41m[ERROR archer] archer_mcast_activate,577: ADD_PORT: WLAN SSID has already been added: egress_port 6, current 0x0001, new 0x0001^[[0m
Jun 13 07:23:49 kernel: ^[[0;33;41m[ERROR archer] archer_mcast_activate,577: ADD_PORT: WLAN SSID has already been added: egress_port 6, current 0x0001, new 0x0001^[[0m
Jun 13 07:23:50 WAN Connection: WAN was restored.

Notice towards the end the link goes down and comes back up at 100 instead of 1000, then it just stays at 100. Again I'm a bit new to this, so I'm not sure entirely what I'm looking at here. Any help or suggestions would be greatly appreciated!
 
Hello!

I'm a bit new to all this, and trying to find the issue here. I recently upgraded to 1000 up/down from 100 up/down. I'm running into an issue where my WAN and network will get the normal 1000 mbps connection, but after a seemingly random amount of time (has been 30 minutes, has been 12 hours) the WAN will go down and come back up at 100 mbps. If I reset my ONT or router, it will usually fix and come back up at 1000 mbps but then will go down and repeat the cycle.

My setup is my ISP ONT to my RT-AX58U router, to a switch, to my computers. ISP is saying it's on my end and not theirs. I've tested the cables from router to switch and switch to computers, they seem fine. I've also changed the ports I'm using, and still run into the issue. Below is what I'm seeing happen in the sys log:

Code:
Jun 13 07:23:06 WAN Connection: WAN(0) link down.
Jun 13 07:23:07 kernel: ^[[0;33;41m[ERROR archer] archer_mcast_activate,577: ADD_PORT: WLAN SSID has already been added: egress_port 7, current 0x0001, new 0x0001^[[0m
Jun 13 07:23:07 kernel: ^[[0;33;41m[ERROR archer] archer_mcast_activate,577: ADD_PORT: WLAN SSID has already been added: egress_port 7, current 0x0001, new 0x0001^[[0m
Jun 13 07:23:07 kernel: eth4 (Int switch port: 4) (Logical Port: 4) (phyId: c) Link Up at 1000 mbps full duplex
Jun 13 07:23:12 WAN Connection: WAN(0) link up.
Jun 13 07:23:12 rc_service: wanduck 1444:notify_rc restart_wan_if 0
Jun 13 07:23:15 wan: finish adding multi routes
Jun 13 07:23:15 miniupnpd[19676]: shutting down MiniUPnPd
Jun 13 07:23:16 miniupnpd: it is advised to use network interface name instead of 192.168.50.1/255.255.255.0
Jun 13 07:23:16 miniupnpd[22111]: HTTP listening on port 47868
Jun 13 07:23:16 kernel: Archer TCP Pure ACK Enabled
Jun 13 07:23:16 dhcp client: bound X/255.255.255.0 via X for 1800 seconds.
Jun 13 07:23:16 miniupnpd[22111]: Listening for NAT-PMP/PCP traffic on port 5351
Jun 13 07:23:16 kernel: ^[[0;33;41m[ERROR archer] archer_mcast_activate,577: ADD_PORT: WLAN SSID has already been added: egress_port 6, current 0x0001, new 0x0001^[[0m
Jun 13 07:23:16 kernel: ^[[0;33;41m[ERROR archer] archer_mcast_activate,577: ADD_PORT: WLAN SSID has already been added: egress_port 6, current 0x0001, new 0x0001^[[0m
Jun 13 07:23:20 WAN Connection: WAN was restored.
Jun 13 07:23:27 kernel: eth4 (Int switch port: 4) (Logical Port: 4) (phyId: c) Link DOWN.
Jun 13 07:23:29 kernel: eth4 (Int switch port: 4) (Logical Port: 4) (phyId: c) Link Up at 1000 mbps full duplex
Jun 13 07:23:30 kernel: eth4 (Int switch port: 4) (Logical Port: 4) (phyId: c) Link DOWN.
Jun 13 07:23:30 kernel: ^[[0;33;41m[ERROR archer] archer_mcast_activate,577: ADD_PORT: WLAN SSID has already been added: egress_port 6, current 0x0001, new 0x0001^[[0m
Jun 13 07:23:30 kernel: ^[[0;33;41m[ERROR archer] archer_mcast_activate,577: ADD_PORT: WLAN SSID has already been added: egress_port 6, current 0x0001, new 0x0001^[[0m
Jun 13 07:23:33 kernel: eth4 (Int switch port: 4) (Logical Port: 4) (phyId: c) Link Up at 1000 mbps full duplex
Jun 13 07:23:34 kernel: eth4 (Int switch port: 4) (Logical Port: 4) (phyId: c) Link DOWN.
Jun 13 07:23:35 WAN Connection: WAN(0) link down.
Jun 13 07:23:37 kernel: eth4 (Int switch port: 4) (Logical Port: 4) (phyId: c) Link Up at 1000 mbps full duplex
Jun 13 07:23:38 kernel: eth4 (Int switch port: 4) (Logical Port: 4) (phyId: c) Link DOWN.
Jun 13 07:23:40 kernel: eth4 (Int switch port: 4) (Logical Port: 4) (phyId: c) Link Up at 1000 mbps full duplex
Jun 13 07:23:42 kernel: eth4 (Int switch port: 4) (Logical Port: 4) (phyId: c) Link DOWN.
Jun 13 07:23:44 kernel: eth4 (Int switch port: 4) (Logical Port: 4) (phyId: c) Link Up at 1000 mbps full duplex
Jun 13 07:23:45 WAN Connection: WAN(0) link up.
Jun 13 07:23:45 rc_service: wanduck 1444:notify_rc restart_wan_if 0
Jun 13 07:23:46 kernel: ^[[0;33;41m[ERROR archer] archer_mcast_activate,577: ADD_PORT: WLAN SSID has already been added: egress_port 7, current 0x0001, new 0x0001^[[0m
Jun 13 07:23:46 kernel: ^[[0;33;41m[ERROR archer] archer_mcast_activate,577: ADD_PORT: WLAN SSID has already been added: egress_port 7, current 0x0001, new 0x0001^[[0m
Jun 13 07:23:46 kernel: eth4 (Int switch port: 4) (Logical Port: 4) (phyId: c) Link DOWN.
Jun 13 07:23:47 kernel: eth4 (Int switch port: 4) (Logical Port: 4) (phyId: c) Link Up at 100 mbps full duplex
Jun 13 07:23:47 wan: finish adding multi routes
Jun 13 07:23:48 miniupnpd[22111]: shutting down MiniUPnPd
Jun 13 07:23:48 miniupnpd: it is advised to use network interface name instead of 192.168.50.1/255.255.255.0
Jun 13 07:23:48 miniupnpd[22477]: HTTP listening on port 42005
Jun 13 07:23:48 kernel: Archer TCP Pure ACK Enabled
Jun 13 07:23:48 dhcp client: bound X/255.255.255.0 via X for 1800 seconds.
Jun 13 07:23:48 miniupnpd[22477]: Listening for NAT-PMP/PCP traffic on port 5351
Jun 13 07:23:48 kernel: ^[[0;33;41m[ERROR archer] archer_mcast_activate,577: ADD_PORT: WLAN SSID has already been added: egress_port 6, current 0x0001, new 0x0001^[[0m
Jun 13 07:23:49 kernel: ^[[0;33;41m[ERROR archer] archer_mcast_activate,577: ADD_PORT: WLAN SSID has already been added: egress_port 6, current 0x0001, new 0x0001^[[0m
Jun 13 07:23:50 WAN Connection: WAN was restored.

Notice towards the end the link goes down and comes back up at 100 instead of 1000, then it just stays at 100. Again I'm a bit new to this, so I'm not sure entirely what I'm looking at here. Any help or suggestions would be greatly appreciated!

Have you tried a different WAN cable?

OE
 
Have you tried a different WAN cable?

OE
I assume that's the Ethernet cable going from my ONT outlet to my router? If so, yes - I tried using a brand new cat 6 there. If it's the connection from the ONT to the outlet (inside the wall), I'm not sure exactly how that's wired. I didn't think about that, I can try to see how that's wired when I have a minute later today.
 
Likely a CAT 5e cable would be more than adequate.
Is the ONT outside or inside ?
either way, if the WAN to Wall Plate cable change does not fix it, run a cat5e cable direct from the ONT to the WAN port to sort out if it is the in wall cable or termination as the cause.
It could be the wall plate termination or RJ connector, the cable, the ONT RJ connector, etc up to and including the WAN port RJ connector.
 
I assume that's the Ethernet cable going from my ONT outlet to my router? If so, yes - I tried using a brand new cat 6 there. If it's the connection from the ONT to the outlet (inside the wall), I'm not sure exactly how that's wired. I didn't think about that, I can try to see how that's wired when I have a minute later today.

Yes, all the way to the ONT 'LAN' port... intervening links and jacks increases the suspect factor. A spare 100' Ethernet cable is handy for such a test... or move the router to the ONT.

OE
 
Likely a CAT 5e cable would be more than adequate.
Is the ONT outside or inside ?
either way, if the WAN to Wall Plate cable change does not fix it, run a cat5e cable direct from the ONT to the WAN port to sort out if it is the in wall cable or termination as the cause.
It could be the wall plate termination or RJ connector, the cable, the ONT RJ connector, etc up to and including the WAN port RJ connector.
The ONT is outside. It looks like it might be a pain to replace any cable there as it all goes through the brick. I don't think I'm experienced enough to mess with that, might be best for me to call the ISP and see if they'll come out and look at it. Thank you so much for the info. Seems pretty certain the issue is not the router itself then?
 
The ONT is outside. It looks like it might be a pain to replace any cable there as it all goes through the brick. I don't think I'm experienced enough to mess with that, might be best for me to call the ISP and see if they'll come out and look at it. Thank you so much for the info. Seems pretty certain the issue is not the router itself then?
depends on the route through the wall. If it is just straight out, then easy. But if it makes bends or is not in conduit, then difficult.
You can call them, but they may not be willing to do anything. Alarm system installers or other low voltage cable installers may be cheaper/easier.

First you need to establish if the problem is in the wall or not. Get a long enough cat5e cable to run from your ASUS WAN port to the ONT port. See if you have the same issue. Or move the ASUS for a few days to allow a temporary connection direct to the ONT. Even just a loose RJ connector in the socket on either end can be an issue.
It could be the ONT connector itself. The ISP would only have the option to replace it. But you may need to establish that it is not on your side of the ONT.
If you were using the ISP router, they might have been more willing during the upgrade to fiber to address it or make a new penetration in the wall.
Mounting the ONT inside might be a better solution, but up to the ISP.

Since it initially links at 1000, that suggests too much noise on the line or intermittent connection. Could be from a damaged wire in the cable or a poor termination, loose socket connection ( no retainer spring clip for example) or even corrosion on the connectors.

It is possible that you have a bad port on the ASUS. If you can try another router, or of another port on this router can be used as WAN, that would help you nail this down. i would use another router if possible.
 
Last edited:
Unfortunately I don't have another router at the moment. I had plugged a laptop directly into the ONT plate and was getting the slower 100 mbps, but it's an old laptop. I had initially used this to assume it wasn't the router... but I guess it's possible the laptop ethernet card doesn't have that speed capability? Is there any way to monitor speed changes on a pc (similar to the sys log above) without a router? I can grab a longer cable and plug directly into a better PC. Maybe a dumb question, but if it's the router (so lets say it's not a problem between the ONT and router), would there be any reason I'd still get a lower speed plugged directly into the ONT plate assuming the PC and everything can handle the higher speed? I think that would help me rule out if it's the router port or not? I can also try removing and bypassing the plate itself to help rule that out as a connection issue. Assuming the cable isn't hardwired into the plate which I can't check or confirm just yet.

The route through the outside wall is not a good one. It bends, has no conduit, and the hole it comes through is very small - the size of the cable itself. I'd need to run cable through the wall and attach the ends/heads after it's on the outside - which I have no idea how to do. I'll keep this as a last resort since I think the only way I can do this without drilling new holes would be to run the cable from the outside around my house into the garage and run the tests there. Assuming I have the tools to open the box the ONT is in :)
 
Unfortunately I don't have another router at the moment. I had plugged a laptop directly into the ONT plate and was getting the slower 100 mbps, but it's an old laptop. I had initially used this to assume it wasn't the router... but I guess it's possible the laptop ethernet card doesn't have that speed capability? Is there any way to monitor speed changes on a pc (similar to the sys log above) without a router? I can grab a longer cable and plug directly into a better PC. Maybe a dumb question, but if it's the router (so lets say it's not a problem between the ONT and router), would there be any reason I'd still get a lower speed plugged directly into the ONT plate assuming the PC and everything can handle the higher speed? I think that would help me rule out if it's the router port or not? I can also try removing and bypassing the plate itself to help rule that out as a connection issue. Assuming the cable isn't hardwired into the plate which I can't check or confirm just yet.

The route through the outside wall is not a good one. It bends, has no conduit, and the hole it comes through is very small - the size of the cable itself. I'd need to run cable through the wall and attach the ends/heads after it's on the outside - which I have no idea how to do. I'll keep this as a last resort since I think the only way I can do this without drilling new holes would be to run the cable from the outside around my house into the garage and run the tests there. Assuming I have the tools to open the box the ONT is in :)

Have you noticed that System Status in the router webUI reports port link rates:
1655144824150.png


I would use the router and a good cable to test Ethernet link rates. If you can't get a long Ethernet cable, get a long extension cord.

Assume the ONT port is ok and test it.

Assume the wall cable/jack is not ok and test it.

Finally, assume your router WAN port is ok and test it... assuming your switch has Gigabit ports, connect the router WAN port to a bare switch port to test it.

Maybe you can isolate the issue. Also check the wiring on the back of the wall plate... maybe you just need to fix one termination there.

Terminating Ethernet is not difficult, but you need the RJ-45 connectors, cutter, crimper, and the right conductor order, easily copied from a working cable. And keep the twisted pairs twisted together as much as possible. Practice makes perfect. Good tools and connectors might cost $100, more or less. Or get an ISP tech out to check the ONT and then beg 'em to fix the inside wiring, if possible.

OE
 
Last edited:
On this router, what is logical/physical port 4 on the switch ?
Is that the WAN port ?
or were you plugged into LAN port 4 with your computer or switch when that log was captured ?

IF that was LAN port 4, then you have an issue with the cable/device that was plugged into that port and not the connection from the WAN port to the ONT.

@OzarkEdge do you know how ASUS numbers their ports internally ?
 
@OzarkEdge do you know how ASUS numbers their ports internally ?

No, I just tried to monitor the log while disconnecting cables... the info is likely there but its complicated with a lot of references to logical ports, etc., and responses were not the same for 2.5GbE WAN vs LAN ports... so I gave up! :)

OE
 
Have you noticed that System Status in the router webUI reports port link rates:
View attachment 41831

I would use the router and a good cable to test Ethernet link rates. If you can't get a long Ethernet cable, get a long extension cord.

Assume the ONT port is ok and test it.

Assume the wall cable/jack is not ok and test it.

Finally, assume your router WAN port is ok and test it... assuming your switch has Gigabit ports, connect the router WAN port to a bare switch port to test it.

Maybe you can isolate the issue. Also check the wiring on the back of the wall plate... maybe you just need to fix one termination there.

Terminating Ethernet is not difficult, but you need the RJ-45 connectors, cutter, crimper, and the right conductor order, easily copied from a working cable. And keep the twisted pairs twisted together as much as possible. Practice makes perfect. Good tools and connectors might cost $100, more or less. Or get an ISP tech out to check the ONT and then beg 'em to fix the inside wiring, if possible.

OE
Thank you!

I saw it had the speeds, but didn't think about using it to test. I don't know if it means anything, but my WAN port (on the system status such as below and your image) switches from 1 Gbps to 100 Mbps when the issue happens. It doesn't go back up to 1 Gbps unless I reset the router.

1655149527349.png


Dumb question, when testing the ONT port and cables/jack, I can plug those into LAN ports and it's fine right? Or should I still be using WAN to test even though it could be the issue.
 
there seem to be a few reports with people having wan issues, so if this does not track down to a cabling issue, you might RMA to ASUS and replace with an AX86s or AX86U

 
On this router, what is logical/physical port 4 on the switch ?
Is that the WAN port ?
or were you plugged into LAN port 4 with your computer or switch when that log was captured ?

IF that was LAN port 4, then you have an issue with the cable/device that was plugged into that port and not the connection from the WAN port to the ONT.

@OzarkEdge do you know how ASUS numbers their ports internally ?
I initially spent time researching and trying to figure this out. What confused me is every sys log report I found where people had port issues, the port was always 'Ext port 1/2/3/4', where as mine is 'Int port'... I couldn't really find others with an int port issue, and I'm unsure what the difference is. I did also plug only my switch into the other ports (previously unused, and unplugged the items from the switch) to try and rule that out, and received the same port 4 error regardless of which port it was plugged into.
 
Last edited:
Thank you!

I saw it had the speeds, but didn't think about using it to test. I don't know if it means anything, but my WAN port (on the system status such as below and your image) switches from 1 Gbps to 100 Mbps when the issue happens. It doesn't go back up to 1 Gbps unless I reset the router.

View attachment 41838

Dumb question, when testing the ONT port and cables/jack, I can plug those into LAN ports and it's fine right? Or should I still be using WAN to test even though it could be the issue.
you can use any port to test link speed.
 
I just pulled off the wall plate for the ONT connection to ensure it was at least a 5e cable, and this is the connection order on the jack. Going by the instructions I looked at, this looks like it could be incorrect? Or does it only matter depending on how the other end is connected? I feel like this might be the culprit, since 100 mbps only technically needs 2 pairs while 1000 needs all 4, unless what I read is not right? Top-to-bottom order is (left) blue, green, brown, white brown - (right) blue white, blue green, white orange, orange.

1655158315271.png
 
Thank you!

I saw it had the speeds, but didn't think about using it to test. I don't know if it means anything, but my WAN port (on the system status such as below and your image) switches from 1 Gbps to 100 Mbps when the issue happens. It doesn't go back up to 1 Gbps unless I reset the router.

Yes, that's the issue we're troubleshooting... unstable WAN link rate.

Dumb question, when testing the ONT port and cables/jack, I can plug those into LAN ports and it's fine right? Or should I still be using WAN to test even though it could be the issue.

If router WAN to ONT LAN (a technically correct connection) gives you a stable 1Gbps link rate, then both ports are ok and I would proceed to test using the router WAN port... why not.

Of course, I don't normally do any of this so be prepared to think about what you observe.

OE
 
Last edited:
I just pulled off the wall plate for the ONT connection to ensure it was at least a 5e cable, and this is the connection order on the jack. Going by the instructions I looked at, this looks like it could be incorrect? Or does it only matter depending on how the other end is connected? I feel like this might be the culprit, since 100 mbps only technically needs 2 pairs while 1000 needs all 4, unless what I read is not right? Top-to-bottom order is (left) blue, green, brown, white brown - (right) blue white, blue green, white orange, orange.

View attachment 41848

There may be more than one wiring standard, and you don't know what the other end is doing... and in between. I would test ports first. While you have it open, inspect the integrity of the assembly, conductors, contacts for any small defects... it looks tidy from here.

OE
 
There may be more than one wiring standard, and you don't know what the other end is doing... and in between. I would test ports first. While you have it open, inspect the integrity of the assembly, conductors, contacts for any small defects... it looks tidy from here.

OE
Yep! I will use the rest of the night testing ports. Thank you both for the help so far! It's very much appreciated!
 

Latest threads

Sign Up For SNBForums Daily Digest

Get an update of what's new every day delivered to your mailbox. Sign up here!
Top