TLDR;

Test Computer -> cat5 cable -> New Router -> Switch -> Bridged Router -> Router -> Spectrum Cable fails

Test Computer -> WIFI -> New Router -> Switch -> Bridged Router -> Router -> Spectrum Cable works

 

I bought a TPLink AC1750 router as part of me hardwiring the house for ethernet. I can get some wifi, but prefer the wired if possible. Anyway, changed it to access point mode, changed the admin password and SSID name and not much else. I connected the incoming internet line (WAN port?) to a switch which is connected to another router in bridge mode which finally connects to the incoming line from Spectrum. As I type this, I anticipate the comments on complexity. I'm with you, but bear with me.

 

Anyway, before hanging the new router in it's new home, I tested another computer against it. This test computer can do a wifi connection just fine to the suspect router. But if I connect it via a wire, it fails.

My journalctl shows the following

 

Dec 15 00:16:00 woodsman-office-closet NetworkManager[14858]: <warn>  [1639545360.8675] dhcp4 (eno1): request timed out
Dec 15 00:16:00 woodsman-office-closet NetworkManager[14858]: <info>  [1639545360.8675] dhcp4 (eno1): state changed unknown -> timeout
Dec 15 00:16:00 woodsman-office-closet NetworkManager[14858]: <info>  [1639545360.8756] dhcp4 (eno1): canceled DHCP transaction, DHCP client pid 16326
Dec 15 00:16:00 woodsman-office-closet NetworkManager[14858]: <info>  [1639545360.8756] dhcp4 (eno1): state changed timeout -> done
Dec 15 00:16:00 woodsman-office-closet NetworkManager[14858]: <info>  [1639545360.8759] device (eno1): state change: ip-config -> failed (reason 'ip-config-unavailable', sys-iface-state: 'managed')
Dec 15 00:16:00 woodsman-office-closet NetworkManager[14858]: <warn>  [1639545360.8767] device (eno1): Activation: failed for connection 'eno1'

 

When I connect the same cat5 cable from the test computer to another router, it works fine, so I ruled out the cable.

 

What else should I check?

 

Test computer is Linux FC30.