Disconnect after connect using WPS

Pascal K pascalkrauth
Wed Mar 5 02:09:26 PST 2014


Thanks for pointing that out.

I meanwhile discovered that the connection didn't work as expected because
I was using a Sony Xperia ZL Android 4.3 as a client.
With every other device I now tested it does work as I expected.

Anyway thanks for your time.

Pascal



2014-03-05 11:06 GMT+01:00 Avinash Patil <avinashapatil at gmail.com>:

> WPS spec mandates to break WPS association after successful/unsuccessful
> exchange.
> Client is supposed to connect on its own using new configuration. This is
> entirely out of scope of hostapd.
>
> -Avinash.
>
>
> On Wed, Mar 5, 2014 at 2:40 PM, Pascal K <pascalkrauth at gmail.com> wrote:
>
>> Hello Avinash,
>>
>> so I might did not understand the WPS process completly.
>>
>> What I try to do is start a AP and connect some clients (Android
>> Smarphones) to it. But they connect successfully using WPS and then
>> disconnect afterwards.
>> Am I supposed to handle the connection on the AP side?
>>
>> I thought that the Key get's exchange using WPS and afterwards the
>> connection will not drop.
>>
>> Best regards,
>> Pascal
>>
>>
>> 2014-03-05 9:46 GMT+01:00 Avinash Patil <avinashapatil at gmail.com>:
>>
>> Hello Paskal,
>>>
>>> Once WPS exchange is complete, you are supposed to initiated connection
>>> from external station device manually. WPS exchange is used to generate
>>> config file required for this connection. Deauthentication from mwifiex AP
>>> is expected after successful WPS exchange.
>>>
>>> Please let me know if you see any issues.
>>>
>>> Thanks,
>>> Avinash
>>>
>>>
>>> On Wed, Mar 5, 2014 at 1:51 PM, Pascal K <pascalkrauth at gmail.com> wrote:
>>>
>>>> Hello everyone,
>>>>
>>>> I use a Marvell SD8787 wifi card.
>>>> A AP is configured and working stable until I connect a device through
>>>> WPS
>>>>
>>>> $hostapd_cli wps_pbc
>>>>
>>>> my log shows "WPS-Success" and 2seconds later my device disconnects.
>>>> My config might be wrong. I use hostapd 2.0 on a 3.2 Linux Kernel with
>>>> backported drivers from 3.12.2-1 for my Mwifiex based card.
>>>>
>>>> Any suggestions?
>>>>
>>>> Best regards,
>>>> Pascal
>>>>
>>>> hostapd.conf
>>>>
>>>> #############################################
>>>> #
>>>> #       hostapd config for Access Point
>>>> #       with WPS functionality
>>>> #
>>>> #############################################
>>>>
>>>> #Basic Access Point configurations
>>>>
>>>> interface=uap0
>>>> driver=nl80211
>>>> ssid=IPEhub2_0002
>>>> hw_mode=g
>>>> ieee80211n=1
>>>> channel=3
>>>> macaddr_acl=0
>>>>
>>>> wpa=2
>>>> wpa_passphrase=123456789
>>>> wpa_key_mgmt=WPA-PSK WPA-EAP
>>>> wpa_pairwise=TKIP CCMP
>>>>
>>>> ## Wmm setting for IEEE 802.11 draft
>>>> # wmm_enabled=1
>>>>
>>>> ## Allow both Auth. algorithms
>>>> auth_algs=3
>>>>
>>>> ignore_broadcast_ssid=0
>>>> eap_reauth_period=0
>>>> eapol_version=1
>>>> #wpa_group_rekey=0
>>>> ctrl_interface=/var/run/hostapd
>>>> ctrl_interface_group=0
>>>> wpa_psk_file=/etc/hostapd.psk
>>>> eap_server=1
>>>>
>>>> wps_state=2
>>>> ap_setup_locked=1
>>>> #############################################
>>>>
>>>>
>>>> Information from log of hostapd -dd
>>>>
>>>> uap0: WPS-SUCCESS
>>>> EAP-WSC: WPS processing completed successfully - report EAP failure
>>>> EAP-WSC: MESG -> FAIL
>>>> EAP: EAP entering state SELECT_ACTION
>>>> EAP: getDecision: method failed -> FAILURE
>>>> EAP: EAP entering state FAILURE
>>>> EAP: Building EAP-Failure (id=142)
>>>> uap0: CTRL-EVENT-EAP-FAILURE 18:00:2d:9b:3f:96
>>>> IEEE 802.1X: 18:00:2d:9b:3f:96 BE_AUTH entering state FAIL
>>>> uap0: STA 18:00:2d:9b:3f:96 IEEE 802.1X: Sending EAP Packet (identifier
>>>> 142)
>>>> IEEE 802.1X: 18:00:2d:9b:3f:96 AUTH_PAE entering state HELD
>>>> uap0: STA 18:00:2d:9b:3f:96 IEEE 802.1X: unauthorizing port
>>>> Could not set station 18:00:2d:9b:3f:96 flags for kernel driver
>>>> (errno=97).
>>>> uap0: STA 18:00:2d:9b:3f:96 IEEE 802.1X: authentication failed - EAP
>>>> type: 0 ((null))
>>>> uap0: STA 18:00:2d:9b:3f:96 IEEE 802.1X: Supplicant used different EAP
>>>> type: 254 (expanded)
>>>> uap0: IEEE 802.1X: Force disconnection after EAP-Failure
>>>> ap_sta_disconnect: reschedule ap_handle_timer timeout for
>>>> 18:00:2d:9b:3f:96 (5 seconds - AP_MAX_INACTIVITY_AFTER_DEAUTH)
>>>> IEEE 802.1X: 18:00:2d:9b:3f:96 BE_AUTH entering state IDLE
>>>> IEEE 802.1X: 18:00:2d:9b:3f:96 AUTH_PAE entering state INITIALIZE
>>>> EAP: EAP entering state DISABLED
>>>> ....
>>>> uap0: Flushing old station entries
>>>> uap0: Deauthenticate all stations
>>>> wpa_driver_nl80211_set_key: ifindex=6 alg=0 addr=(nil) key_idx=0
>>>> set_tx=0 seq_len=0 key_len=0
>>>> wpa_driver_nl80211_set_key: ifindex=6 alg=0 addr=(nil) key_idx=1
>>>> set_tx=0 seq_len=0 key_len=0
>>>> wpa_driver_nl80211_set_key: ifindex=6 alg=0 addr=(nil) key_idx=2
>>>> set_tx=0 seq_len=0 key_len=0
>>>> wpa_driver_nl80211_set_key: ifindex=6 alg=0 addr=(nil) key_idx=3
>>>> set_tx=0 seq_len=0 key_len=0
>>>> nl80211: Skip disabling of Probe Request reporting nl_preq=0xbf680
>>>> while in AP mode
>>>> netlink: Operstate: linkmode=0, operstate=6
>>>> nl80211: Set mode ifindex 6 iftype 2 (STATION)
>>>> nl80211: Failed to set interface 6 to mode 2: -95 (Operation not
>>>> supported)
>>>> nl80211: Try mode change after setting interface down
>>>> nl80211: Set mode ifindex 6 iftype 2 (STATION)
>>>> nl80211: Failed to set interface 6 to mode 2: -95 (Operation not
>>>> supported)
>>>> nl80211: Interface mode change to 2 from 3 failed
>>>> nl80211: Unsubscribe mgmt frames handle 0xc0138 (deinit)
>>>> ELOOP: remaining socket: sock=11 eloop_data=0xc0180 user_data=0xbf680
>>>> handler=0x3b494
>>>>
>>>>
>>>>
>>>> _______________________________________________
>>>> HostAP mailing list
>>>> HostAP at lists.shmoo.com
>>>> http://lists.shmoo.com/mailman/listinfo/hostap
>>>>
>>>>
>>>
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.shmoo.com/pipermail/hostap/attachments/20140305/2f970173/attachment-0001.htm>



More information about the Hostap mailing list