wpa_supplicant fixes sent upstream?

[Jeremy C. Reed]

(Cc'd to the RESPONSIBLE.)

Have the wpa_supplicant fixes been sent upstream?

I have been spending time patching the latest 0.6.6 development release
for NetBSD support (to build a pkgsrc package to test on my NetBSD 4.0
system), and can build but failing at run-time:

Starting AP scan (broadcast SSID)
ioctl[SIOCS80211, op 1, len 0]: Invalid argument
Failed to initiate AP scan.

I then saw the custom driver_netbsd.c in NetBSD -current.

I don't see any __NetBSD__ only code in official wpa_supplicant.

If the improvements haven't been shared, can someone submit them?

Thanks,

Jeremy C. Reed

p.s. You can see my problems and attempts in the hostap mailing list.

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

[Christos Zoulas]

Post by Jeremy C. Reed
(Cc'd to the RESPONSIBLE.)
Have the wpa_supplicant fixes been sent upstream?
I have been spending time patching the latest 0.6.6 development release
for NetBSD support (to build a pkgsrc package to test on my NetBSD 4.0
Starting AP scan (broadcast SSID)
ioctl[SIOCS80211, op 1, len 0]: Invalid argument
Failed to initiate AP scan.
I then saw the custom driver_netbsd.c in NetBSD -current.
I don't see any __NetBSD__ only code in official wpa_supplicant.
If the improvements haven't been shared, can someone submit them?
Thanks,
Jeremy C. Reed
p.s. You can see my problems and attempts in the hostap mailing list.

There is only one NetBSD ifdef, and support for a couple of ioctls.
The rest are all bug fixes. It is only like 300 lines of diff.

christos


--
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 Christos Zoulas
There is only one NetBSD ifdef, and support for a couple of ioctls.
The rest are all bug fixes. It is only like 300 lines of diff.

Can you point me to the NetBSD ifdef and the ioctl changes? I can't find
them when comparing original wpa_supplicant-0.6.4 with src/dist/wpa.

Also what about the src/usr.sbin/wpa/wpa_supplicant/driver_netbsd.c --
that isn't upstream at all. (I assume it should just be merged into
upstream's driver_bsd.c.)

(My iwi wireless connection has probably dropped over 50 times and it is
becoming unusable. I am hoping to be able to use the latest wpa_supplicant
to see if that helps.)

--
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
(My iwi wireless connection has probably dropped over 50 times and it is
becoming unusable. I am hoping to be able to use the latest wpa_supplicant
to see if that helps.)

I packaged 0.6.6 as pkgsrc/net/wpa_supplicant and I am using on NetBSD
4.0. It includes a patch partially based on NetBSD's driver_netbsd.c.

It doesn't solve my connection problems. It works but no improvement over
older version.

Review of the patch-aa is appreciated. Then I will submit upstream.

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

[Christos Zoulas]

Post by Jeremy C. Reed

Post by Christos Zoulas
There is only one NetBSD ifdef, and support for a couple of ioctls.
The rest are all bug fixes. It is only like 300 lines of diff.

Can you point me to the NetBSD ifdef and the ioctl changes? I can't find
them when comparing original wpa_supplicant-0.6.4 with src/dist/wpa.

cvs diff -ur v0_6_4

Post by Jeremy C. Reed
Also what about the src/usr.sbin/wpa/wpa_supplicant/driver_netbsd.c --
that isn't upstream at all. (I assume it should just be merged into
upstream's driver_bsd.c.)

I just did this.

Post by Jeremy C. Reed
(My iwi wireless connection has probably dropped over 50 times and it is
becoming unusable. I am hoping to be able to use the latest wpa_supplicant
to see if that helps.)

Good luck!

christos


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