wpa_supplicant connects to non-working networks

momu · 2018-09-04 07:19:12

I have a small problem. My router doesn't work properly for some reason, but when it is on wpa_supplicant automatically connects to it. When it is connected to it, there is no Internet at all but I do have an IP address and iwgetid returns the name of the network.

This is my config file entry example:

network={
	ssid="NAME"
	key_mgmt=WPA-PSK
	psk="password"
	priority=5
	scan_ssid=1
}

My bad network is declared according to this blueprint. Currently, the only ways I know to stop my wpa_supplicant from connecting to this network are:
1. Adding disabled=1 to the network declaration.
2. Commenting the whole network

Meanwhile, other OSs (Android, Windows and Linux Mint) know that this network is invalid and don't detect it all, let alone connect to it. How can I get my Arch to behave that way?

brebs · 2018-09-04 10:10:15

You just gave 2 ways, then you're asking for a way?

It's not wpa_supplicant's problem that your router doesn't provide a decent Internet connection. It connects, as you've told it to do

Edit: iwd might be more "friendly" than wpa_supplicant.

Last edited by brebs (2018-09-04 10:20:19)

momu · 2018-09-04 13:58:46

brebs wrote:

You just gave 2 ways, then you're asking for a way?
It's not wpa_supplicant's problem that your router doesn't provide a decent Internet connection. It connects, as you've told it to do
Edit: iwd might be more "friendly" than wpa_supplicant.

Correct, but I want it to not connect automatically if it detects that network is bad. As I've said, Android, Windows and Linux Mint have no problem with this. Even on Arch, when I used Xfce, my system didn't connect to bad networks.

Also, if I turn the router on (meaning it was off), Arch connects immediately and has no Internet access for some time while other OSs wait and connect only when there is valid Internet signal.

Btw, if someone is interested, my router stopped working properly after a thunderbolt hit somewhere around my area. Not sure if those two things are connected, though.

loqs · 2018-09-04 17:04:23

momu wrote:

Even on Arch, when I used Xfce, my system didn't connect to bad networks.

This was using wpa_supplicant?

brebs · 2018-09-04 18:04:27

momu wrote:

Arch connects immediately and has no Internet access for some time while other OSs wait and connect only when there is valid Internet signal.

What is their alternative method of getting Internet access, that you haven't yet mentioned?

R00KIE · 2018-09-04 21:08:00

I'm not sure I follow, you don't want wpa_supplicant to connect to a bad network but you have explicitly added it in your wpa_supplicant configuration file?

Mind you, wpa_supplicant is working just fine as it handles _only_ the authentication with the network, once that is done getting IP addresses and checking for proper connectivity is the job of other tools.

Your intended behaviour is the result of a few different tools working together, you might get similar results if you use one of the several network connection manager programs available on the repos instead of your current setup.

momu wrote:

Arch connects immediately and has no Internet access for some time while other OSs wait and connect only when there is valid Internet signal.

Are you sure? They probably authenticate, get an IP via dhcp, then check if connectivity is working, since it's not they tear down the connection and start over.

Arch Linux

#1 2018-09-04 07:19:12

wpa_supplicant connects to non-working networks

#2 2018-09-04 10:10:15

Re: wpa_supplicant connects to non-working networks

#3 2018-09-04 13:58:46

Re: wpa_supplicant connects to non-working networks

#4 2018-09-04 17:04:23

Re: wpa_supplicant connects to non-working networks

#5 2018-09-04 18:04:27

Re: wpa_supplicant connects to non-working networks

#6 2018-09-04 21:08:00

Re: wpa_supplicant connects to non-working networks

Board footer