What's new
  • 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!

RT-AC5300 - Ethernet not being assigned IPs, DHCP issues?

JoshuaW22

Occasional Visitor
RT-AC5300 - Ethernet not being assigned IPs, DHCP issues?


Hello All,

Working on a seperate network at home for a homelab type project, but having issues with ethernet connectivity.

It is presenting in two fashions, so may actually be two issues?
1) A device is assigned an IP address, but otherwise does not actually gain connectivity, but does appear in the network map.
2) Device intermittently appears in the network map as expected.

Interestingly, wifi works fine, but direct ethernet connection is having troubles across a dozen devices.

At first decided that the issue must be the old switch I was using, so I purchased a new managed switch (netgear) and the issue persisted.

While trying to get it fixed, I actually ended up realizing that even devices connected directly to the router are exhibiting the issue periodically? Even now, I am writing from wifi, but if I switch to ethernet only, I lose connectivity to the internet.


I don't think it's related really, but I earlier enabled link bonding/aggregation (lan1, lan2), as my synology nas has that functionality, but thought I should mention it.


I still suspect the switch, but have gone through 4 of them at this point testing, and am not sure whats going on. If I connect straight to the router then the likihood of an issue is much lower, but periodically I am still seeing troubles...


Hoping someone can steer me towards the right testing to figure this out. Not sure how to debug ethernet, as normally wifi has been my issue, haha.
 
Yeah, I tried the same, no luck. :'(

Any other low hanging fruit to look into?

Are there known issues with DHCP behind switches for the AC-5300 or something? A quick google search didn't turn up anything useful.
 
Do a factory reset with initialize and dont turn it on again, maybe something stays in NVRAM even if you turn it off.
 
Last edited:
Try some new Ethernet cables. Especially between the router and switch. If you make your own cables double check the cables are made to TIA/EIA 568B. Gig Ethernet can be picky.
 
Looks like the issue was likely related to NVRAM. I had previously used this router for another project, so I beleive something stuck behind. Another (so two total) factory resets, seems to be working as expected on an initial set of test devices.

Going to roll out more devices, and be sure to report back if I run into issues. If this is the last post, all was fixed!
 

Latest threads

Support SNBForums w/ Amazon

If you'd like to support SNBForums, just use this link and buy anything on Amazon. Thanks!

Sign Up For SNBForums Daily Digest

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