On 07/27/2012 11:38 AM, Xavier de Almeida wrote:
Without touching anything it started to work:
Jul 27 18:34:27 HTPC hostapd: wlan0: STA 88:30:8a:52:ed:cd IEEE 802.11: association OK (aid 1)
Jul 27 18:34:27 HTPC hostapd: wlan0: STA 88:30:8a:52:ed:cd IEEE 802.11: associated (aid 1)
Jul 27 18:34:27 HTPC hostapd: wlan0: STA 88:30:8a:52:ed:cd MLME: MLME-ASSOCIATE.indication(88:30:8a:52:ed:cd)
Jul 27 18:34:27 HTPC hostapd: wlan0: STA 88:30:8a:52:ed:cd MLME: MLME-DELETEKEYS.request(88:30:8a:52:ed:cd)
Jul 27 18:34:27 HTPC hostapd: wlan0: STA 88:30:8a:52:ed:cd WPA: event 1 notification
Jul 27 18:34:27 HTPC hostapd: wlan0: STA 88:30:8a:52:ed:cd WPA: start authentication
Jul 27 18:34:27 HTPC hostapd: wlan0: STA 88:30:8a:52:ed:cd IEEE 802.1X: unauthorizing port
Jul 27 18:34:27 HTPC hostapd: wlan0: STA 88:30:8a:52:ed:cd WPA: sending 1/4 msg of 4-Way Handshake
Jul 27 18:34:27 HTPC hostapd: wlan0: STA 88:30:8a:52:ed:cd WPA: received EAPOL-Key frame (2/4 Pairwise)
Jul 27 18:34:27 HTPC hostapd: wlan0: STA 88:30:8a:52:ed:cd WPA: sending 3/4 msg of 4-Way Handshake
Jul 27 18:34:27 HTPC hostapd: wlan0: STA 88:30:8a:52:ed:cd WPA: received EAPOL-Key frame (4/4 Pairwise)
Jul 27 18:34:27 HTPC hostapd: wlan0: STA 88:30:8a:52:ed:cd IEEE 802.1X: authorizing port
Jul 27 18:34:27 HTPC hostapd: wlan0: STA 88:30:8a:52:ed:cd RADIUS: starting accounting session 5012BD3F-00000000
Jul 27 18:34:27 HTPC hostapd: wlan0: STA 88:30:8a:52:ed:cd WPA: pairwise key handshake completed (RSN)
but the signal is very weak so maybe that was one of the issues.
I am looking fwd to remove the power mgt stuff and maybe find out how to increase the signal power. Maybe I should be a kind of antennat but not sure this will work with a barebone like the xs36v.
I run mine, when I test AP mode, without any options.
I'm glad you got it working. Now you know why I recommend spending 40 euro for
an AP rather than trying to use a 600 euro computer for that purpose. BTW, I own
4 AP/routers.
Larry
--
To unsubscribe from this list: send the line "unsubscribe linux-wireless" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
