Skip to content


The new wpa_supplicant packages have removed the /etc/wpa_supplicant.conf file. Wireless LAN is now configured via special commands from /etc/network/interfaces, which looks like an elegant Debian way to do things.

While setting this up, I have learned the following:

  • an ESSID starting with "+" is not accepted
  • You don't enter the passphrase verbatim into /e/n/i, you use wpa_passphrase to hash it
  • wpa_supplicant debugs surprisingly well

Well done, maintainers! Thanks!

Next time I'll figure out how to configure wpa_supplicant to automatically associate to the correct wireless LAN regardless of location


No Trackbacks


Display comments as Linear | Threaded

Joachim Breitner on :

I recommend guessnet for that, it works quite well. Also, you'd need a roaming daemon, see

Reinhard Tartler on :

I'd suggest creating your own wpa_supplicant.conf, where you can define priorities in case several location are accessible.

Then create an action script, which calls whereami when you get connected. there you can configure your interface and start services as you wish.

Marc 'Zugschlus' Haber on :

Actually, I happen to like the one-/e/n/i-stanza-per network approach a lot. I'd like to use it instead of sticking to the old configuration method.

Kel Modderman on :

Hi, thanks for the great feedback!

You could add the passphrase verbatim into /e/n/i with a wpa-passphrase line (instead of wpa-psk), but be sure to mark that file as root-readable only ;-)

I'm not so sure about ssid's with strange characters, unless its converted to hex first, which is a bit strange (but easily possible i suppose).

Cheers, Kel.

Add Comment

Markdown format allowed
Enclosing asterisks marks text as bold (*word*), underscore are made via _word_.
Standard emoticons like :-) and ;-) are converted to images.
E-Mail addresses will not be displayed and will only be used for E-Mail notifications.
Form options