Hi Sam,
On Thu, 12 Nov 2009 03:53:17 pm Sam Leffler wrote:
> Setting HOSTAPD_CFLAGS directly is the intended mechanism. EAP_SERVER
> is the important one to define; past that you're just adding in some of
> the more esoteric mechanisms. I should probably enable it by default
> (it comes setup ou
Geoff Roberts wrote:
Hi Sam,
On Mon, 9 Nov 2009 03:48:41 am Sam Leffler wrote:
snip <
So your station associated and hostapd saw it but nothing in your logs
shows what hostapd did or did not do to complete the radius handshake.
All we see is that hostapd dropped the station--presumably because
Hi Sam,
On Mon, 9 Nov 2009 03:48:41 am Sam Leffler wrote:
> snip <
>
> So your station associated and hostapd saw it but nothing in your logs
> shows what hostapd did or did not do to complete the radius handshake.
> All we see is that hostapd dropped the station--presumably because it
> timed out
Geoff Roberts wrote:
> Hi,
>
> I had a working hostapd wireless access point configuration in FreeBSD 6.4.
> The access point is being used by Windows XP workstations.
>
> I was using WPA-EAP with freeradius authentication very successfully on the
> 6.4 backend.
>
> After making the changes fo
Hi,
I had a working hostapd wireless access point configuration in FreeBSD 6.4.
The access point is being used by Windows XP workstations.
I was using WPA-EAP with freeradius authentication very successfully on the
6.4 backend.
After making the changes for a new 8.0 RC2 (see below) system the
