Riddle me this, batman; WTH is going on with my ER-X?!

notarat

2[H]4U
Joined
Mar 28, 2010
Messages
2,492
I'm having problems with my 3 month old EdgeRouter-X so I'll describe it and post what is quite possibly the most 3rd grade MS Paint example known to exist on the North American continent.

NetGear CM1000 Cable Modem feeds my EdgeRouter-X. CAT6 from Cable Modem goes to Port 0 on the ER-X

The ER-X serves as my DHCP Server for 2 Desktops and a TP Link Archer C-7 (to provide wireless access to my phone/tablets separate from my Desktops)

At least 2-3 times per month, Ports 1 & 2 on the ER-X suddenly stop functioning completely, resulting in no Internet connectivity for either desktop. They can't see the ER-X nor each other, nor the Cable Modem...however...the TP Link still functions just fine. I can unplug either (or both) desktops CAT6 cables from the ER-X and connect them to the ethernet ports on the TP Link, Perform a release/renew, and they immediately pull an IP from teh TP Link and regain internet connectivity.

wth.jpg


(Note: All ethernet cables are brand new, good-quality CAT6, less than 25ft long, and known-working (I tested them with our tester at work)

Thoughts? Suggestions?(other than, "Learn to MS PAINT, foo!")
 
A simple power cycle doesn't resolve the issue? I assume the firmware is up to date.

Are you sure the port goes down? It's not just the DHCP server on those ports failing somehow (i.e., static IP addressing has the same results)? What's the desktop NIC's status when this happens? The ER-X's port status?

Have you tried switching around which device is on which ER-X port? Does the AP behave fine on ports 1/2? If you move one of the desktops to port 3, does it start to fail? What about port 4? i.e., does the problem follow certain devices or stay with the same ports?

Long shot, but's possible the PSU is the issue. If you have another power brick with the same connector (mind the polarity), same voltage (required), and rated for the same amperage or higher (the ER-X will only pull what it needs), give it a shot.

May need to start lining up an RMA.
 
Why are you running 2 separate DHCP servers? Why not use the ER-X's DHCP server to serve both Ethernet and WiFi clients?

I am wondering if you are getting some kind of conflict between the 2 DHCP servers. The ER-X isn't fully down when your problem occurs because the TPlink still has Internet access, which means it isn't a total router failure (doesn't rule out bad hardware though).
 
Why are you running 2 separate DHCP servers? Why not use the ER-X's DHCP server to serve both Ethernet and WiFi clients?

I am wondering if you are getting some kind of conflict between the 2 DHCP servers. The ER-X isn't fully down when your problem occurs because the TPlink still has Internet access, which means it isn't a total router failure (doesn't rule out bad hardware though).


Eewww, missed all that. OP is double-NATing for the wireless clients. Eewww. Though it does look like the AP's DHCP server would be isolated to those.

OP, unless there's some odd reason for such a setup, disable it. Turn off DHCP and any other network services on the AP. Readdress it to the 192.168.1.0/24 subnet, and move the ethernet connection coming from the ER-X from the WAN to a LAN port.

This is unrelated to the original problem, though.
 
Eewww, missed all that. OP is double-NATing for the wireless clients. Eewww. Though it does look like the AP's DHCP server would be isolated to those.

OP, unless there's some odd reason for such a setup, disable it. Turn off DHCP and any other network services on the AP. Readdress it to the 192.168.1.0/24 subnet, and move the ethernet connection coming from the ER-X from the WAN to a LAN port.

This is unrelated to the original problem, though.

It might be related, depends on which port of the TPLink the OP plugs in the Ethernet cable from the ER-X (the diagram doesn't show which port is used):
  • If it is in the WAN port then you are correct, it is a double-NAT and it is unlikely there is a leakage of the DHCP from the TPLink to the ER-X. It also isn't the cause of the issue (although it is in itself enough of an issue that it should be addressed regardless).
  • If it is in a LAN port then it could very well be that the DHCP servers are colliding and that every once in a while the desktops get served from the TPLink and it breaks the connection, especially if the ER-X has storm control active on the ports.
OP, if you are having any sort of WiFi range, stability, or other issues you may want to seriously consider getting a Ubiquiti WAP like an AC-Lite or AC-Pro. I recently picked up an AC-Lite and the performance compared to the ASUS RT-66U it replaced is night and day. The AC-Lite/Pro will play nice with the ER-X, although you'll need a computer to run the control software (no problem if you have a server handy). As it is a pure WAP there is no worries about DHCP or other router functions in the AC-Lite/Pro to interfere with the operations of the ER-X.
 
Back
Top