ral(4) and wpa_supplicant?

[Geert Hendrickx]

Hi,

which wifi cards are supported by wpa_supplicant(8)? Lacking support for
my laptop's built-in BCM4315 card, I'm trying with an USB ral(4) card.
This is with NetBSD/i386 5.0_RC3.

I can connect to open or WEP-protected AP's using ifconfig(8) only. But
I'd prefer to use WPA/RSN instead.

Trying to connect to any network (open/WEP/WPA/RSN) with wpa_supplicant
results in:

CTRL-EVENT-SCAN-RESULTS
Trying to associate with 00:0b:86:33:7f:f1 (SSID='foo' freq=2437 MHz)
ioctl[SIOCS80211, op 21, len 42]: Invalid argument
Association request to the driver failed
Authentication with 00:0b:86:33:7f:f1 timed out.

I've tried both wpa_supplicant 0.6.4 shipped with 5.0_RC3 and 0.6.7 from
pkgsrc.


Geert

[Roy Marples]

Post by Geert Hendrickx
which wifi cards are supported by wpa_supplicant(8)?

iwi(4) works fine.

Post by Geert Hendrickx
Lacking support for
my laptop's built-in BCM4315 card, I'm trying with an USB ral(4) card.
This is with NetBSD/i386 5.0_RC3.
I can connect to open or WEP-protected AP's using ifconfig(8) only. But
I'd prefer to use WPA/RSN instead.

I see the same error with ral(4) using an rt2500 based pci card, so I'm
guessing it's a driver issue.

Thanks

Roy

--
Posted automagically by a mail2news gateway at muc.de e.V.
Please direct questions, flames, donations, etc. to news-***@muc.de

[Petar Bogdanovic]

Post by Geert Hendrickx
which wifi cards are supported by wpa_supplicant(8)?

I'm using ath(4) with wpa_supplicant(8) on NetBSD 4.0 and it works very
well. It's connected to the following WPA2-network 24h/7d:

IE: IEEE 802.11i/WPA2 Version 1
Group Cipher : CCMP
Pairwise Ciphers (1) : CCMP
Authentication Suites (1) : PSK



Petar Bogdanovic




--
Posted automagically by a mail2news gateway at muc.de e.V.
Please direct questions, flames, donations, etc. to news-***@muc.de

[FUKAUMI Naoki]

hi

At Mon, 30 Mar 2009 16:45:43 +0100,

Post by Roy Marples

Post by Geert Hendrickx
which wifi cards are supported by wpa_supplicant(8)?

iwi(4) works fine.

Post by Geert Hendrickx
Lacking support for
my laptop's built-in BCM4315 card, I'm trying with an USB ral(4) card.
This is with NetBSD/i386 5.0_RC3.
I can connect to open or WEP-protected AP's using ifconfig(8) only. But
I'd prefer to use WPA/RSN instead.

I see the same error with ral(4) using an rt2500 based pci card, so I'm
guessing it's a driver issue.

please try attached patch and rebuild wpa_supplicant.

it restores
src/dist/wpa/src/drivers/driver_bsd.c::wpa_driver_bsd_associate()
as same as
src/usr.sbin/wpa/wpa_supplicant/Attic/driver_netbsd.c

this problem was introduced in -current at Dec 12 2008, in netbsd-5 at
Jan 22 2009. NetBSD 5.0 has this problem.

--
FUKAUMI Naoki

[Roy Marples]

Post by FUKAUMI Naoki
please try attached patch and rebuild wpa_supplicant.
it restores
src/dist/wpa/src/drivers/driver_bsd.c::wpa_driver_bsd_associate()
as same as
src/usr.sbin/wpa/wpa_supplicant/Attic/driver_netbsd.c
this problem was introduced in -current at Dec 12 2008, in netbsd-5 at
Jan 22 2009. NetBSD 5.0 has this problem.

Fixes it for me - thanks!

Roy

--
Posted automagically by a mail2news gateway at muc.de e.V.
Please direct questions, flames, donations, etc. to news-***@muc.de

[Roy Marples]

Post by Roy Marples

Post by FUKAUMI Naoki
please try attached patch and rebuild wpa_supplicant.
it restores
src/dist/wpa/src/drivers/driver_bsd.c::wpa_driver_bsd_associate()
as same as
src/usr.sbin/wpa/wpa_supplicant/Attic/driver_netbsd.c
this problem was introduced in -current at Dec 12 2008, in netbsd-5 at
Jan 22 2009. NetBSD 5.0 has this problem.

Fixes it for me - thanks!

I've mirrored this in pkgsrc net/wpa_supplicant also.

Thanks

Roy


--
Posted automagically by a mail2news gateway at muc.de e.V.
Please direct questions, flames, donations, etc. to news-***@muc.de

[Roy Marples]

I've patched drivers/driver_bsd.c to remove and enable the code guarded
by this define.

I've checked against the FreeBSD driver which they maintain outside of
wpa_supplicant and they no longer have that define either. I've also
tested this against ral(4) and iwi(4). The patch has been sent upstream [1]

As netbsd-5 is affected, I've also requested pullup [2]

Thanks

Roy

[1] http://w1.fi/bugz/show_bug.cgi?id=312
[2] http://releng.netbsd.org/cgi-bin/req-5.cgi?show=755

--
Posted automagically by a mail2news gateway at muc.de e.V.
Please direct questions, flames, donations, etc. to news-***@muc.de

[FUKAUMI Naoki]

hi

At Wed, 13 May 2009 13:25:17 +0100,

Post by Roy Marples
I've patched drivers/driver_bsd.c to remove and enable the code guarded
by this define.
I've checked against the FreeBSD driver which they maintain outside of
wpa_supplicant and they no longer have that define either. I've also
tested this against ral(4) and iwi(4). The patch has been sent upstream [1]
As netbsd-5 is affected, I've also requested pullup [2]

Thank you!

(FYI, I've tested rum(4) and run(4) on NetBSD 5.0)

--
FUKAUMI Naoki

--
Posted automagically by a mail2news gateway at muc.de e.V.
Please direct questions, flames, donations, etc. to news-***@muc.de

[Jeremy C. Reed]

Sorry I changed topic somewhat below .. talking about netbsd-5 dhcpcd
below ...

I've patched drivers/driver_bsd.c to remove and enable the code guarded by
this define.
I've checked against the FreeBSD driver which they maintain outside of
wpa_supplicant and they no longer have that define either. I've also tested
this against ral(4) and iwi(4). The patch has been sent upstream [1]

From pkgsrc perspective ... iwi(4) doesn't work for me with latest
wpa_supplicant-0.6.9 with CPPFLAGS+= -DNEW_FREEBSD_MLME_ASSOC (and
also did with the patch too which should be identical). I get

ioctl[SIOCS80211, op 1, len 0]: Invalid argument
Failed to initiate AP scan.


ioctl[SIOCS80211, op 1, len 0]: Invalid argument
Failed to initiate AP scan.

So I reverted to older package wpa_supplicant-0.6.6.tgz.

On a different system using netbsd-5's /usr/sbin/wpa_supplicant and
/sbin/dhcpcd I had problems. The new wpa_supplicant would attach (before
it wouldn't with the ioctl invalid argument as mentioned in different
thread). But then it would lose connection repeatedly. I had to fall back
to use ifconfig to set my wifi settings. ... okay nevermind this ... my
problem is with dhcpcd ... after the following switched to dhclient and
now my networking is working ...

Also upgraded dhcpcd stopped working for me. I was using 5.0_RC2 version
or something like that (for a couple months) but now moved to latest
netbsd-5 today.

I am not sure if my rum device or my wireless router, but my rum0
frequently loses connection. With dhcpcd, it gets a lease and configures
it, but quickly if loses connection, it unconfigures my network.

So now I used dhclient and it works for me. For example the following is
when using dhclient

$ /sbin/ifconfig rum0
rum0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1500
ssid foo nwkey *****
powersave off
address: 00:11:aa:bb:a9:40
media: IEEE802.11 autoselect (DS1 mode 11g)
status: no network
inet 192.168.1.7 netmask 0xffffff00 broadcast 192.168.1.255
inet6 fe80::211:50ff:fec1:a940%rum0 prefixlen 64 scopeid 0x4
$ /sbin/ifconfig rum0
rum0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1500
ssid foo nwkey *****
powersave off
bssid 00:18:01:e0:8a:57 chan 6
address: 00:11:aa:bb:a9:40
media: IEEE802.11 autoselect (OFDM36 mode 11g)
status: active
inet 192.168.1.7 netmask 0xffffff00 broadcast 192.168.1.255
inet6 fe80::211:50ff:fec1:a940%rum0 prefixlen 64 scopeid 0x4

But when using netbsd-5 dhcpcd, when the status goes to "no network" the
"inet" becomes unconfigured. Maybe there is an option to not unconfigure.

By using dhclient, I can still use.

(So I went back to new wpa_supplicant. And is working.)

I was using "rum0" as my dhcpcd command line argument
(dhcpcd_flags="-C resolv.conf rum0") but rc.d script has;

pidfile=/var/run/$name.pid

So "status" and "stop" for the rc.d script do not work (rum0 is part of
pid file name).



--
Posted automagically by a mail2news gateway at muc.de e.V.
Please direct questions, flames, donations, etc. to news-***@muc.de

[Jeremy C. Reed]

Post by Jeremy C. Reed
But when using netbsd-5 dhcpcd, when the status goes to "no network" the
"inet" becomes unconfigured. Maybe there is an option to not
unconfigure.

Okay, found it: --nolink

Now I am using wpa_supplicant on rum0 and newer dhcpcd!

Thanks!

--
Posted automagically by a mail2news gateway at muc.de e.V.
Please direct questions, flames, donations, etc. to news-***@muc.de

[Roy Marples]

Trying to associate with 00:22:b0:cf:6d:35 (SSID='hendrickx44' freq=2447 MHz)
ioctl[SIOCS80211, op 21, len 42]: Invalid argument
Association request to the driver failed
Trying to associate with 00:22:b0:cf:6d:35 (SSID='hendrickx44' freq=2447 MHz)
Associated with 00:22:b0:cf:6d:35
WPA: Could not verify EAPOL-Key MIC - dropping packet
WPA: Could not verify EAPOL-Key MIC - dropping packet
WPA: Could not verify EAPOL-Key MIC - dropping packet
CTRL-EVENT-DISCONNECTED - Disconnect event - remove keys
(in a loop)

Well that shows that the interface is has associated (which is what the
patch fixed) and you now have a different error.

Try adding the wpa_supplicant -d flag to enable more debugging.
But I can't really help anymore as I don't know the actual guts of wireless.

Thanks

Roy

--
Posted automagically by a mail2news gateway at muc.de e.V.
Please direct questions, flames, donations, etc. to news-***@muc.de

[matthew sporleder]

Post by Roy Marples

Trying to associate with 00:22:b0:cf:6d:35 (SSID='hendrickx44' freq=2447

MHz)

ioctl[SIOCS80211, op 21, len 42]: Invalid argument
Association request to the driver failed
Trying to associate with 00:22:b0:cf:6d:35 (SSID='hendrickx44' freq=2447

MHz)

Associated with 00:22:b0:cf:6d:35
WPA: Could not verify EAPOL-Key MIC - dropping packet
WPA: Could not verify EAPOL-Key MIC - dropping packet
WPA: Could not verify EAPOL-Key MIC - dropping packet
CTRL-EVENT-DISCONNECTED - Disconnect event - remove keys
(in a loop)

Well that shows that the interface is has associated (which is what the
patch fixed) and you now have a different error.
Try adding the wpa_supplicant -d flag to enable more debugging.
But I can't really help anymore as I don't know the actual guts of wireless.

For what it's worth I have a system with an ath and a ral on current
and ath can use wpa_supplicant just fine but ral loops in the
"Association request to the driver failed" message. I haven't had a
chance to try wpa_supplicant from pkgsrc yet.

--
Posted automagically by a mail2news gateway at muc.de e.V.
Please direct questions, flames, donations, etc. to news-***@muc.de

[Geert Hendrickx]

Post by Roy Marples
Well that shows that the interface is has associated (which is what the
patch fixed) and you now have a different error.

FWIW, I tried using OpenBSD with the same ral(4) card and the same AP, and it
was able to associate with my AP succesfully, using both WPA-PSK and WPA2-PSK
(however OpenBSD uses ifconfig(8) arguments to configure wpa). This excludes
problems with the hardware or the AP configuration.

Post by Roy Marples
Try adding the wpa_supplicant -d flag to enable more debugging. But I
can't really help anymore as I don't know the actual guts of wireless.

wpa_supplicant debugging output is attached for those who can read it...


Geert