keith.jamieson@bt.com wrote [WITHOUT CREDITING PEOPLE CORRECTLY]:
"CDW (Linux)" cdw_alug@the-walker-household.co.uk wrote:
If I run wpa_cli, it produces the following :-
<2>WPA: 4-Way Handshake failed - pre-shared key may be incorrect
<2>CTRL-EVENT-DISCONNECTED - Disconnect event - remove keys <2>Associated with 00:0f:3d:34:d6:f6
and then repeats the above lines.
But the passphrase I'm using is the same one I'm using on my wife's laptop, plus her and my phones. So I know it's good.
But from the above classic "pre-shared key may be incorrect" situation, we know it's not good. How to resolve this?
I'd start by checking that it's the latest version of wpa_supplicant (I've checked and my wpa_cli really does know the scan_results and status commands - wpa_supplicant 0.5.7), that there's no bug reports for WPA with that hardware or distribution and that 00:0f:3d:34:d6:f6 is the right access point. I can't be the only one to spend 5 minutes debugging an accidental connection to someone else's AP!
Sorry if that's not much help. I hate networks.
Did you say "passphrase" ? This is the term for a "something to make the key". What you need to do it to put in the HEX or ASCII into the key fields. One manufactures "passphrase" makes different HEX to another. You do not have the manufactures software ( on Linux HAHAHAHH! ) then you will not be able to create the HEX needed.
Huh? I have a line that says psk="whatevermypasswordis" in my /etc/wpa_supplicant.conf, not hex.
Also, the original poster clearly said this is on DesktopBSD, so please stop laughing at Linux like a troll. ;-)