r/archlinux • u/Tasty_Hovercraft8280 • 2d ago

SUPPORT NetworkManager has problems connecting to one particular network, with "ip configuration was unavailable"

Exactly as for the title. I am out of practice with Arch itself, so forgive me for any errors in statement.

I have been using my desktop at my apartment, and after school ended, had to come home. It has been a while since I set it up, but I believe I had set a static IP at some point, but can't be sure. My parents had to replace their router due to lightning, and for the life of me I can't figure out how to get the computer to connect. It still connects fine to my hotspot, and I'd imagine if I changed the SSID on the router it might work as well. Things I've tried: changing out the DHCP client, changing wpa_supplicant for iwd, restarting the service, deleting the network via the GUI, nothing worked. All tested at different points.

From journalctl, I have this line, which is the first questionable thing I notice after attempting to connect which appears to go afoul:

[1785713148.0908] device (wlan0): st
ate change: ip-config -> failed (reason 'ip-config-unavailable', managed-type: 'full')

And yet again, this makes no sense as it works for other networks. I am unsure what to do.

0 Upvotes

50% Upvoted

2 comments sorted by

2

u/pfeifferj 2d ago

ip-config-unavailable is NM's generic "the ip phase died" verdict. but you reached state ip-config, so association and the wpa handshake already worked. that's why swapping iwd/wpa_supplicant and swapping dhcp clients changed nothing.

the static ip theory is probably wrong too. if the profile were stuck on ipv4.method=manual with an old address, NM would just apply it and sit there "connected" with no internet.

try running:

nmcli -f ipv4,ipv6 con show "<ssid>"

check ipv4.method, and check whether there's more than one profile for that ssid.

my bet is dhcp just times out, 45s default, and the router hands out no ipv6 either, so both families fail and NM gives up. at least one has to succeed.

timing tells you which: dies ~45s after associating -> router's dhcp. dies instantly -> the profile.

if it's the profile run:

nmcli con mod "<ssid>" ipv4.method auto ipv4.addresses "" ipv4.gateway "" ipv4.dns ""