I've just thrown an intel 3945 nic into my aspire one and I'm having trouble with a similar issue. In my reading of the man page for ifconfig, I've come to think that the

Quote:

> $(wpa-psk ABC ABCpass)

is actually generating a passkey from the phrase 'ABCpass', as opposed to specifying the pass 'ABCpass'.

My network is currently set for a 256 bit ASCII key, which OpenBSD doesn't seem to support (bash plays up a bit when I try). Once I'm able to temporarily change the key for my network, I think I'll have to try something along the lines of:

Quote:

sudo ifconfig wpi0 nwid NETWORK_NAME wpa wpapsk 0x64_CHAR_HEX_KEY

Hopefully I haven't misinterpreted the man page .

[update]: Can confirm that this works . It's been a long road to get wifi working on this laptop, the default atheros card is very poorly supported but this intel 3945 card works a treat.

in the hostname.wpi0 file. but at bootup the system said the nwkey string is too long(because my Uni has 26 characters).
How do i connect to the WEP connection by issuing the command(if i don't know the gateway)?

I tried to put 0x at the beginning of the password but i got the same error. The password is a combination of 26 numbers and alphabeticals. How do i connect to my Uni(WEP encryption) with these 26 characters under nwid of my Uni? Can i use the following code?

I know it uses "NONE NONE NONE" to connect to a AP which is using the certain nwkey at bootup. But what if i just want to connect to a AP without matching the nwkey to each AP in the detected networks. I have tried

Code:

dhcp NONE NONE NONE nwkey 0x1deadbeef1 chan 11

But it doesn't work for my Uni, i just got the error for the nwkey it saids nwkey string too long.

Then your Oxblahblahblah string is to long. I know you have probably solved this by now also i never have to put the channel or nwid to get my wifi interface to work. Also to get wpa to work you need madwifi driver and the wpa_supplicant i believe due to the licensing of wpa.

That is totally inaccurate information about WPA iacbsd.. OpenBSD doesn't use "madwifi" or "wpa_supplicant", it has it's own implementation.. and there are no licencing issues, it is fully standardized.

Well, there *were* licensing issues, but it was the other-way-'round, an apparent misuse of reyk@'s ISC-licensed code developed for OpenBSD. The gory details can be found on misc@ and on the linux-kernel mailing list, mid-September, 2007.

Then your Oxblahblahblah string is to long. I know you have probably solved this by now also i never have to put the channel or nwid to get my wifi interface to work. Also to get wpa to work you need madwifi driver and the wpa_supplicant i believe due to the licensing of wpa.

Nonsense. Please refrain from giving any "help" if you do not know what are you talking about. We are talking about OpenBSD not about FreeBSD. wpa-supplicant port from OpenBSD tree has only wire support. OpenBSD has completely different implementation of WPA for WiFi devices.

Nonsense. Please refrain from giving any "help" if you do not know what are you talking about. We are talking about OpenBSD not about FreeBSD. wpa-supplicant port from OpenBSD three has only wire support. OpenBSD has completely different implementation of WPA for WiFi devices.

yeah your right madwifi and wpa suplicant was for linux my bad its been along time since i got wpa2 working on openbsd but wpa2 i think did require some configuration file if i am not mistaken as far wep however the network key is to long i know because i have done this before too :P