Fragmented EAP ACK problem on -current
Olivier Cochard-Labbé
olivier at cochard.me
Tue Jan 20 09:04:06 UTC 2015
On Tue, Jan 20, 2015 at 2:52 AM, Adrian Chadd <adrian at freebsd.org> wrote:
> how are they being fragmented? 802.11 fragments? Or just separate
> MPDUs, but not 802.11 fragments?
>
>
It's not a 802.11 fragment frame, but 802.1x/EAP-TLS fragment frame.
I believe this section should be managed by hostapd code
(src/contrib/wpa/src/eap_server/eap_server_tls.c) ?
But I didn't reach to display the wpa_printf(MSG_DEBUG,...) with hostapd in
debug mode.
Frame detail in text mode received by freebsd/hostapd (EAP-TLS "more
fragment" set), but no ACK (EAP-TLS empty) from freebsd/hostapd.
Frame 174: 1552 bytes on wire (12416 bits), 1552 bytes captured (12416 bits)
Radiotap Header v0, Length 24
IEEE 802.11 Data, Flags: .......T
Type/Subtype: Data (0x20)
Frame Control: 0x0108 (Normal)
Version: 0
Type: Data frame (2)
Subtype: 0
Flags: 0x1
.... ..01 = DS status: Frame from STA to DS via an AP (To DS: 1
>From DS: 0) (0x01)
.... .0.. = More Fragments: This is the last fragment
.... 0... = Retry: Frame is not being retransmitted
...0 .... = PWR MGT: STA will stay up
..0. .... = More Data: No data buffered
.0.. .... = Protected flag: Data is not protected
0... .... = Order flag: Not strictly ordered
Duration: 314
BSS Id: D-Link_58:79:3e (00:21:91:58:79:3e)
Source address: GemtekTe_35:8c:70 (20:10:7a:35:8c:70)
Destination address: D-Link_58:79:3e (00:21:91:58:79:3e)
Fragment number: 0
Sequence number: 263
Logical-Link Control
802.1X Authentication
Version: 802.1X-2001 (1)
Type: EAP Packet (0)
Length: 1492
Extensible Authentication Protocol
Code: Response (2)
Id: 51
Length: 1492
Type: TLS EAP (EAP-TLS) (13)
EAP-TLS Flags: 0xc0
1... .... = Length Included: True
.1.. .... = More Fragments: True
..0. .... = Start: False
EAP-TLS Length: 3524
More information about the freebsd-wireless
mailing list