Can I say first off that I'm trying to make wpa_supplicant work with DesktopBSD so apologies if some of you feel I shouldn't be asking for help here.
I have an old IBM Thinkpad and having tried various brands of Linux, DesktopBSD was the only OS that installed correcly. I then wanted to make it to talk to my other machines which meant networking. It doesn't have a LAN port so I bought what I thought was a good wireless card. I was wrong. It's a Netgear WG511v2 and I've had to install it using ndisgen. I can get the thing to recognise my wireless LAN and if I run ifconfig, it reports :- ndis0: flags=8842<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1500 ether 00:1b:2f:d0:69:59 media: IEEE 802.11 Wireless Ethernet autoselect (DS/11Mbps) status: associated ssid ss2_scanning channel 11 bssid 00:0f:3d:34:d6:f6 authmode WPA privacy OFF txpowmax 100 bmiss 7
My /etc/wpa_supplicant.conf file looks like this ctrl_interface=/var/run/wpa_supplicant ctrl+interface_group=wheel
network={ ssid="ss2_scanning" proto=WPA key_mgmt=WPA-PSK pairwise=TKIP group=TKIP psk="c:(vo.............$-" }
So the question is, does the psk data have to be in quotes and in hex? If so, how do I translate my ascii line into hex?
I've read lots and lots of stuff online about all this and to be honest, I'm thoroughly confused.
I'd appreciate any help.
On Thursday 23 October 2008 23:20:45 CDW (Linux) wrote:
It's a Netgear WG511v2 and I've had to install it using ndisgen. I can get the thing to recognise my wireless LAN and if I run ifconfig, it reports :- ndis0: flags=8842<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1500 ether 00:1b:2f:d0:69:59 media: IEEE 802.11 Wireless Ethernet autoselect (DS/11Mbps) status: associated ssid ss2_scanning channel 11 bssid 00:0f:3d:34:d6:f6 authmode WPA privacy OFF txpowmax 100 bmiss 7
My /etc/wpa_supplicant.conf file looks like this ctrl_interface=/var/run/wpa_supplicant ctrl+interface_group=wheel
That should probably be ctrl_interface_group. And I guess you're probably right to set it to "wheel", it must be some BSD thing (mine's "root").
network={ ssid="ss2_scanning" proto=WPA key_mgmt=WPA-PSK pairwise=TKIP group=TKIP psk="c:(vo.............$-" }
As always with configurations, start simple. You probably only need ssid, key_mgmt=WPA-PSK, and psk="...". If it doesn't work with just those, only then try adding more options.
So the question is, does the psk data have to be in quotes and in hex? If so, how do I translate my ascii line into hex?
No, as it's PSK you just type in the password exactly as you set it on your router.
I've read lots and lots of stuff online about all this and to be honest, I'm thoroughly confused.
I know the feeling.
I'd appreciate any help.
The next thing you need to do is tell your network configuration mechanism to use wpa_supplicant when it brings the interface up. I don't how it's configured with DesktopBSD, but in Debian it's /etc/network/interfaces and may look something like this:
iface ndis0 inet dhcp wireless-essid ss2_scanning pre-up wpa_supplicant -B -D wext -i \ ndis0 -c /etc/wpa_supplicant/wpa_supplicant.conf post-down killall -q wpa_supplicant
Cheers, Richard
"CDW (Linux)" cdw_alug@the-walker-household.co.uk wrote:
I'd appreciate any help.
Besides the other comments, I'd suggest running wpa_cli and it should print messages about what the supplicant is doing. Also, the commands "status" and "scan_results" are useful IIRC (as is "help").
Some wireless cards are better than others, sadly.
Good luck!
MJ Ray wrote:
"CDW (Linux)" cdw_alug@the-walker-household.co.uk wrote:
I'd appreciate any help.
Besides the other comments, I'd suggest running wpa_cli and it should print messages about what the supplicant is doing. Also, the commands "status" and "scan_results" are useful IIRC (as is "help").
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.
I'm unclear on how I use the status and scan_results commands. If I type in those commands, it tells me it's not a valid command. Sorry.
Some wireless cards are better than others, sadly.
I thought I'd bought one that was known to work but it seems that Netgear have more than one version of it sadly.
MJ Ray wrote:
"CDW (Linux)" cdw_alug@the-walker-household.co.uk wrote:
I'd appreciate any help.
Besides the other comments, I'd suggest running wpa_cli and it should. print messages about what the supplicant is doing. Also, the commands "status" and "scan_results" are useful IIRC (as is "help").
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.
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.
What you need to do is to enter the keys in HEX. Can I suggest trying all ones to get it working ? Then I use the calculator to make some numbers and use these with a bit of "keyboard bashing" to create my key.
I thought I'd bought one that was known to work but it seems that Netgear have more than one version of it sadly.
Just when they are setup correctly :)
Keith
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. ;-)
MJ Ray wrote:
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. ;-)
I tired of trying to fix the compile errors on wpa so blew away DesktopBSD, installed Mandriva 2008.1 (the same as I'm running on this machine when in Linux mode) and swapped out the network card. It was previously a Netgear WG511 v2 so thought I'd do the sensible thing and buy one which was known to work under Linux.
I bought an Edimax card from the Linux Emporium, bunged it in and after a few attemptes at installing the same key I tried with the Netgear, it all works.
So thanks for your help.
All I need to do now is fix the screensize which is stuck at 800x600 but I think there's been some discussion on something similar here recently so I'll be trawling through the archives for a solution to that.
If I was a real glutton for punishment, I guess I could reinstall DesktopBSD as that sorted out the screensize on its own and see if it also coped with the new Edimax card but I'm not sure I can be bothered to go through all that ;-)
Anyway, thanks again for your help. Much appreciated.
On Mon, 27 Oct 2008 14:15:07 -0000 keith.jamieson@bt.com allegedly wrote:
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.
What you need to do is to enter the keys in HEX. Can I suggest trying all ones to get it working ? Then I use the calculator to make some numbers and use these with a bit of "keyboard bashing" to create my key.
Huh? I have no clue what you mean here. Are you on the right list?
Mick ---------------------------------------------------------------------
The text file for RFC 854 contains exactly 854 lines. Do you think there is any cosmic significance in this?
Douglas E Comer - Internetworking with TCP/IP Volume 1
http://www.ietf.org/rfc/rfc854.txt ---------------------------------------------------------------------
-
CDW (Linux) -
keith.jamieson＠bt.com -
mbm -
MJ Ray -
Richard Lewis