The way I usually use cable internet, is to connect another router via ethernet to the cable modem/router, and then connect all my devices to that second router. This way, I could use the provider's router (sometimes the model they provide can't be changed), and at the same time use a better router for my devices.
this post was submitted on 24 Apr 2024
22 points (95.8% liked)
Linux
48208 readers
773 users here now
From Wikipedia, the free encyclopedia
Linux is a family of open source Unix-like operating systems based on the Linux kernel, an operating system kernel first released on September 17, 1991 by Linus Torvalds. Linux is typically packaged in a Linux distribution (or distro for short).
Distributions include the Linux kernel and supporting system software and libraries, many of which are provided by the GNU Project. Many Linux distributions use the word "Linux" in their name, but the Free Software Foundation uses the name GNU/Linux to emphasize the importance of GNU software, causing some controversy.
Rules
- Posts must be relevant to operating systems running the Linux kernel. GNU/Linux or otherwise.
- No misinformation
- No NSFW content
- No hate speech, bigotry, etc
Related Communities
Community icon by Alpár-Etele Méder, licensed under CC BY 3.0
founded 5 years ago
MODERATORS
Do you have a VPN running on those devices to the same network that you are trying to connect to?
Had something like this using WireGuard once
What have you tried so far?
manually setting my ip usually fixed it, but not this time
That seems to be indicative of dhcp issues, not WiFi issues.
Unless the spotty wifi connection is causing the DHCP issue
Unlikely, since DHCP is a pretty short conversation, and other clients aren't having issues.
client or server side?
Yes.
I'd start by pulling NetworkManager, wpa_supplicant and iwd logs (journalctl -u networkmanager.service --since -2h and so on). Check dmesg as well.
both don't show anything weird
I'd still paste it, redacting SSID and MAC addresses.
Even if it's just info messages, it'll still give us an idea of what it does or doesn't do.
I saw the other comment thread about using a static IP sometimes fixing it. We should see that DHCP attempt in the logs. Maybe it succeeds, maybe it's like "btw the router handed me option 42 and I don't know how to deal with that", maybe it's using the wrong DHCP client (dhclient vs dhcpd) but clues are clues.
Could also tail the entire system log (journalctl -f) so you'll see live output of every service. Maybe it connects fine but something else immediately kicks in and breaks it.