User's Manual

Describe "WPS Status Bar" -"PBC - xxx" as follow :
A successful PBC Configuration :
Start PBC connection ~> Scanning AP ~> Begin associating to WPS AP ~> Associated to WPS AP ~>
Sending EAPOL-Start ~> Sending EAP-Rsp (ID) ~> Receive EAP-Rsp (Start) ~> Sending M1 ~>
Received M2 ~> Sending M3 ~> Received M4 ~> Sending M5 ~> Received M6 ~> Sending M7 ~>
Received M8 ~> Sending EAP-Rsp (Done) ~> Configured ~> WPS status is disconnected ~> WPS
status is connected successfully-SSID
No PBC AP available :
Scanning AP ~> No PBC AP available ~> Scanning AP ~> No PBC AP available
~>...
Too Many PBC AP available :
Scanning AP ~> Too Many PBC AP available ~> Scanning AP ~> Too Many PBC AP available ~>...
WPS configuration doesn't complete after two-minute connection: WPS Eap process failed.
When Errors occur within two-minutes of establishing a connection, the WPS status bar might
report "WPS Eap process failed"
Error messages might be:
1. Receive EAP with wrong NONCE.
2. Receive EAP without integrity.
3. An inappropriate EAP-FAIL received.
Describe "Multiple PBC session overlaps" as follow:
Dual bands:
AP1 is a G-Band AP using PBC mode. (ID = 0x0004)
AP2 is a A-Band AP using PBC mode. (ID = 0x0004)
They have the same UUID-E.
STA would regard these two APs as a dual-radio AP and select one band to connect.
Different UUID-E:
AP1 is a G-Band AP using PBC mode. (ID = 0x0004)
40