rin67630
Posts: 185
Joined: Fri Mar 04, 2016 10:15 am

Trap in WPA_supplicant priority is read the unusual way!

Mon Dec 03, 2018 3:24 pm

Hi Folks

I just discoverd a trap in WPA_supplicant: the parameter priority is understood in a a rather unusual way!

A priority 1 is understood lower than a priority 3.

Usually it is just considered the other way!

That is really not nice., but probably hard to correct now.

epoch1970
Posts: 2401
Joined: Thu May 05, 2016 9:33 am
Location: Paris, France

Re: Trap in WPA_supplicant priority is read the unusual way!

Mon Dec 03, 2018 9:54 pm

Maybe you're not the first to report that usability concern, but it's been like that for a long time. Since day one, in fact, soon to be 15 years ago:

Code: Select all

author	Jouni Malinen <j@w1.fi>	2004-07-18 00:14:46 (GMT)
https://w1.fi/cgit/hostap-history/tree/wpa_supplicant/wpa_supplicant.conf?h=hostap_0_2_4 wrote:# priority: priority group (integer)
# By default, all networks will get same priority group (0). If some of the
# networks are more desirable, this field can be used to change the order in
# which wpa_supplicant goes through the networks when selecting a BSS. The
# priority groups will be iterated in decreasing priority (i.e., the larger the
# priority value, the sooner the network is matched against the scan results).
The feature is not documented before wpa_supplicant.conf v. 0_2_4 ;)
"S'il n'y a pas de solution, c'est qu'il n'y a pas de problème." Les Shadoks, J. Rouxel

rin67630
Posts: 185
Joined: Fri Mar 04, 2016 10:15 am

Re: Trap in WPA_supplicant priority is read the unusual way!

Tue Dec 04, 2018 8:37 pm

Yes, but it still has the potential to harm users, who will not await priority to work that way and will find it out the painful way like me...
At least a warning in the default file could help.
Raspberry Pi users who want to work headless are more exposed than others.

Return to “Raspbian”