wireless not working.

[bsdnewbie999]

I configured the wpi0 as follow, to connect to network ABC for example.

# ifconfig wpi0 nwid ABC wpa wpapsk \
> $(wpa-psk ABC ABCpass)

then i do dhclient wpi0 and i keep get this messages.

# dhclient wpi0
DHCPDISCOVER on wpi0 to 255.255.255.255 port 67 interval 3
DHCPDISCOVER on wpi0 to 255.255.255.255 port 67 interval 4
DHCPDISCOVER on wpi0 to 255.255.255.255 port 67 interval 9
link state up -> down
link state down -> up
DHCPDISCOVER on wpi0 to 255.255.255.255 port 67 interval 4
DHCPDISCOVER on wpi0 to 255.255.255.255 port 67 interval 5
link state up -> down
link state down -> up
DHCPDISCOVER on wpi0 to 255.255.255.255 port 67 interval 7
DHCPDISCOVER on wpi0 to 255.255.255.255 port 67 interval 13
link state up -> down
link state down -> up
DHCPDISCOVER on wpi0 to 255.255.255.255 port 67 interval 6
DHCPDISCOVER on wpi0 to 255.255.255.255 port 67 interval 14

[jggimi]

Does a scan for access points show your "ABC" SSID?

If you're running 4.4-release:

# ifconfig -M wpi0

If you're running 4.5-release:

# ifconfig wpi0 scan

[ocicat]

Originally Posted by bsdnewbie999

# ifconfig wpi0 nwid ABC wpa wpapsk \
> $(wpa-psk ABC ABCpass)

Is your access point configured as WPA or WPA2? The ifconfig command above states that the assumption that it is WPA.

[bsdnewbie999]

Yes. My AP is WPA encryption.

[pik]

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

> $(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:

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.

[bsdnewbie999]

What if the AP is WEP encryption? I put

dhcp NONE NONE NONE nwkey example chan 6

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)?

[pik]

I don't claim to understand any of this (my exposure to wlans under openbsd began tonight) but I think you'd need something along the lines of:

ifconfig wpi0 nwid AP_NAME nwkey WEP_KEY

taking note of this particular section in the ifconfig man page

nwkey key
Enable WEP encryption for IEEE 802.11-based wireless network interfaces using the specified key. The key can either be a string, a series of hexadecimal digits (preceded by `0x')....

You may also want to fiddle with the "newkey persist" option, but I'm not sure.

Of course, after all of this you still need to

dhclient wpi0

[bsdnewbie999]

I got this error message when i connect to the WPA's AP

ifconfig: wpapsk: bad pre-shared key length

I use the command
ifconfig wpi0 nwid NETWORK_NAME wpa wpapsk 0x64_CHAR_HEX_KEY

[pik]

The password on my AP is a 256 bit (64 char) hex string, and was generated by https://www.grc.com/passwords.htm. ifconfig will only allow you to set a hex WPA key if it's the right length.

What you need to do is outline exactly the specifics of the network you're trying to connect to - ie which type of encryption (WEP, WPA, WPA2?)...

[bsdnewbie999]

Its WPA encryption.

[bsdnewbie999]

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?

dhcp My_Uni nwkey 26characters chan 6

[ocicat]

Originally Posted by bsdnewbie999

Can i use the following code?

dhcp My_Uni nwkey 26characters chan 6

The manpage to wpi(4) states:

EXAMPLES
     The following hostname.if(5) example configures wpi0 to join whatever
     network is available on boot, using WEP key ``0x1deadbeef1'', channel 11,
     obtaining an IP address using DHCP:

           dhcp NONE NONE NONE nwkey 0x1deadbeef1 chan 11

So, it appears that your syntax is wrong. "NONE NONE NONE" is required.

[bsdnewbie999]

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

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.

[iacbsd]

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.

[BSDfan666]

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.

[jggimi]

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.

[Oko]

Originally Posted by iacbsd

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.

[iacbsd]

Originally Posted by Oko

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