Skip site navigation (1)Skip section navigation (2)
Date:      Thu, 05 Mar 2009 09:12:23 +0100
From:      Erwin Hoffmann <feh@fehcom.de>
To:        linimon@FreeBSD.org, freebsd-net@FreeBSD.org
Subject:   Re: kern/130820: [ndis] wpa_supplicant(8) returns 'no space on device'
Message-ID:  <55CF3225C5C074DD9DCB1564@[192.168.192.108]>
In-Reply-To: <200903050143.n251htES060465@freefall.freebsd.org>
References:  <200903050143.n251htES060465@freefall.freebsd.org>

next in thread | previous in thread | raw e-mail | index | archive | help
Hi

thanks for following my bug-report:

--On Donnerstag, 5. M=C3=A4rz 2009 01:43 +0000 linimon@FreeBSD.org wrote:

> http://www.freebsd.org/cgi/query-pr.cgi?pr=3D130820

From: "Paul B. Mahol" <onemda@gmail.com>
To: linimon@freebsd.org
Cc: freebsd-net@freebsd.org, freebsd-bugs@freebsd.org
Subject: Re: kern/130820: [ndis] wpa_supplicant(8) returns 'no space on
device'

Yet another invalid bug report.
OP should use -Dndis and not -Dbsd

--

I did not reply to the comment, because of it's obvious stupidness:

If you go thru the code source for the wpasuplicant (what I did trying to=20
fix the bug), you can see that (at least that's true for FreeBSD 6.3) the=20
wpasupplicant *only* supports the BSD driver for wlan cards and no other.

That is ok, if the documentation clearly would mention that.

However, it is completely misleading (and shows the ignorance on that=20
subject by Paul) even pretending FreeBSD's wpasuplicant can be used with=20
the driver option.

In fact, FreeBSD's wpasupplicant implementation is at best half baked.
It turned out, that one has to consider at least two different ndis =
drivers:

1. The generic one, which works for unencrypted and WEP connections (using=20
the chipset's internal de/encryption facilities).
2. A specific ndis driver different from (1.) used to talk to the wlan=20
adapter while encryption and authentication is done by wpasupplicant.

Since (2.) is missing, wpasupplicant tries to use the build-in BSD driver,=20
which of course fails with the error message mentioned in my bug report.

In order to follow up this subject, I would recommend to change the=20
category of the bug into something like 'documentation bug' straighten up=20
the docs and close it.

I'm inclined to set up a wpa reference page with a detailed description of=20
this issue and perhaps include some additional patches (wpasupplicant=20
latest version for FreeBSD and others). However, currently I'm busy with=20
other projects; so it is likely that this will we postponed after the=20
summer term.

Further, it would be great (and maybe I ask one of my students) to get the=20
ndis driver working for FreeBSD. But again: This will not happen until the=20
winter term.

regards.
--eh.



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?55CF3225C5C074DD9DCB1564>