small update hcxpcaptool:
detect NETWORK EAP authentication system and Wilibox specific authentication fields:
$ hcxpcaptool -V test.pcapng
start reading from test.pcapng
Summary:
file name....................: test.pcapng
file type....................: pcapng 1.0
file hardware information....: armv6l
file os information..........: Linux 4.14.59-1-ARCH
file application information.: hcxdumptool 4.2.1
network type.................: DLT_IEEE802_11_RADIO (127)
endianess....................: little endian
read errors..................: flawless
packets inside...............: 2
skipped packets..............: 0
packets with FCS.............: 0
authentications (OPEN SYSTEM): 1
authentications (NETWORK EAP): 1
authentications (WILIBOX)....: 1
Read more about NETWORK EAP here:
https://community.cisco.com/t5/wireless-...-p/3128082
I still don't know the secrets about that VENDOR specific field within the authentication frame. Not all devices use them.
detect NETWORK EAP authentication system and Wilibox specific authentication fields:
$ hcxpcaptool -V test.pcapng
start reading from test.pcapng
Summary:
file name....................: test.pcapng
file type....................: pcapng 1.0
file hardware information....: armv6l
file os information..........: Linux 4.14.59-1-ARCH
file application information.: hcxdumptool 4.2.1
network type.................: DLT_IEEE802_11_RADIO (127)
endianess....................: little endian
read errors..................: flawless
packets inside...............: 2
skipped packets..............: 0
packets with FCS.............: 0
authentications (OPEN SYSTEM): 1
authentications (NETWORK EAP): 1
authentications (WILIBOX)....: 1
Read more about NETWORK EAP here:
https://community.cisco.com/t5/wireless-...-p/3128082
I still don't know the secrets about that VENDOR specific field within the authentication frame. Not all devices use them.