5 years of support..!!??

Nils Kassube kassube at gmx.net
Fri Mar 2 19:34:22 UTC 2012


gene heskett wrote:
> On Friday, March 02, 2012 12:46:04 PM Nils Kassube did opine:
> > auto wlan0
> > iface wlan0 inet static
> > # Configuration for WPA2 / CCMP
> > 
> >     wpa-driver wext
> >     wpa-ssid MYSSID
> >     wpa-ap-scan 2
> >     wpa-proto WPA2
> >     wpa-pairwise CCMP
> >     wpa-key-mgmt WPA-PSK
> >     wpa-psk long hash phrase
> >     # psk from the command "wpa_passphrase MYSSID passphrase"
> >     address 192.168.2.59
> >     network 192.168.2.0
> >     netmask 255.255.255.0
> >     broadcast 192.168.2.255
> >     gateway 192.168.2.1
> 
> Interesting.
> 
> Where are the manpages that explain all these wpa-**** settings?

Good question! I had to search a bit to find the file with the relevant 
info which I probably used: /usr/share/doc/wpasupplicant/README.modes.gz

What I didn't mention, though: If you use that static setup you should 
write your nameserver to "/etc/resolv.conf".

> However, my interfaces file is much simpler than that, and I never
> heard of that command you used to generate the key hash.

It comes with the wpasupplicant package.

> Here, I
> have it setup using a phrase that could be the opening paragraph of
> a novel I'll likely never write, but which is easy enough for me to
> remember.  A neighbors frontier net connection went south just this
> past Monday & she brought her winders lappy over, I entered that
> 160+ character passphrase and it worked flawlessly.

160+ characters? For a WPA/WPA2 passphrase there is a limit of 63 
characters. I suppose I used something like "pwgen -cns 63" to generate 
the passphrase - it is stored in a text file and copy & paste prevents 
typos.

> Your recipe above, with mods because I too use fixed addresses on my
> home network, may be just what the doctor ordered, thank you very
> much for sharing.  I did wipe out that hash though, no use
> propagating that all over the cosmos leading to an exploit of your
> system.

LOL! Of course it wasn't my hash, but thanks for your concern. Actually 
I literally used the command mentioned to get the hash.


Nils




More information about the kubuntu-users mailing list