note:
You will see the following message if
...
WPA: Sending
...
EAPOL: SUPP_PAE entering state SUCCESS
EAP: EAP entering state SUCCESS
EAPOL: SUPP_PAE entering state AUTHENTICATED
EAPOL: SUPP_BE entering state IDLE
Note of wpa supplicant operation issue:
The WPA supplicant should be keep running during connection. If you press
3.7 Customization of VID/PID Table
Someone may want to drive any NIC with
In the source file, src/zdusb.c, A static structure,
3.8 Special Mode for Embedded Station Chariot Test
In an embedded system, mostly, there is no NetIQ chariot endpoint, for WiFi testing, to test performance. With this mode, we can bridge the Ethernet and WLAN. The PC behind the Ethernet runs endpoint and testing data go through the station¡¯s wireless interface to measure the performance.
The mechanism is to specify the MAC address for association with AP. Generally, we associate with AP using the station¡¯s MAC address. If we bridge the wired and wireless interfaces, data from wired interface will be dropped by AP. Because PC¡¯s MAC address is filled in source address of data frames. AP drops the frames because the source address is not in associated stations list. If we can use AP¡¯s address for association, we can run chariot on PC to test station wireless interface performance. This is just like what we do in AP mode.
Someone may say that "Can¡¯t I just set station¡¯s MAC as PC¡¯s via ifconfig ethX hw ether". Yes, perhaps, you can. But most bridge will drop the data when the source address is identical to its interfaces¡¯.Therefore, we must let the address for association and
13