Date: Mon, 19 Jan 2015 17:52:43 -0800 From: Adrian Chadd <adrian@freebsd.org> To: =?UTF-8?Q?Olivier_Cochard=2DLabb=C3=A9?= <olivier@cochard.me> Cc: "freebsd-wireless@freebsd.org" <freebsd-wireless@freebsd.org> Subject: Re: Fragmented EAP ACK problem on -current Message-ID: <CAJ-Vmo==p-o7DUCsi0Wh9LRizmrHdrvC%2Bx70D1kT%2BYw2v=jR=A@mail.gmail.com> In-Reply-To: <CA%2Bq%2BTcp5Yp0ia0oWdyTxv2ThswU9cWHcyBi1pEMvPXOpEP76dg@mail.gmail.com> References: <CA%2Bq%2BTcp5Yp0ia0oWdyTxv2ThswU9cWHcyBi1pEMvPXOpEP76dg@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
how are they being fragmented? 802.11 fragments? Or just separate MPDUs, but not 802.11 fragments? -a On 19 January 2015 at 09:18, Olivier Cochard-Labb=C3=A9 <olivier@cochard.me= > wrote: > Hi, > I'm using FreeBSD 11.0-CURRENT r277315 and meet a problem with my FreeBSD > Access Point. > I'm using WPA2-Enterprise (EAP-TLS) authentication with hostapd. > > The problem: > During EAP-TLS authentication, the Authenticator (FreeBSD/hostapd) > correctly send a EAP fragmented "Server Hello, Certificate, Certificate > Request" message to the supplicant. > The supplicant (MS Windows native client) correctly ACK each of theses > fragmented EAP packets with an empty EAP-TLS packet. > > Once the supplicant re-assemble the full EAP Certificate request from the > Authenticator, it send a response (EAP fragmented too). > But FreeBSD/hostapd never ACK the first fragmented packet received from t= he > supplicant > =3D> Then the authentication phase time out. > > I've tried with 3 different wireless card as hostap: > - Atheros 9280 (ath) > - Atheros AR2425 (ath) > - Ralink RT2573 (rum) > And all these have the same problem. > > Does anyone is using an EAP-TLS setup with hostapd successfully on -curre= nt > ? > _______________________________________________ > freebsd-wireless@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-wireless > To unsubscribe, send any mail to "freebsd-wireless-unsubscribe@freebsd.or= g"
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAJ-Vmo==p-o7DUCsi0Wh9LRizmrHdrvC%2Bx70D1kT%2BYw2v=jR=A>