deassociated / associated

Joachim Schiele js at dune2.de
Thu Jun 30 05:36:57 EDT 2005


On Thursday 30 June 2005 11:12, Joachim Schiele wrote:
Dear listmembers,

*ha* it's working now.
The problem was the 
eap_message=hello
eapol_key_index_workaround=0

After removing these two entries it worked!
Thanks anyway!

Regards,
Joachim

> Dear listmembers,
>
> Using hostapd I can't ping the server side.
> So here is what I did:
>
> 1. ./hostapd madwifi.conf &
> 2.  ifconfig ath0 192.168.178.10 up
>
> on a client in issue then:
> 3. iwlist s
> and i can see the access point up & running
> 4. iwconfig ath0 ap st:ra:ng:e0
> 5. iwconfig ath0 essid "foobar"
> now i can see that it gets associated on the server side but after pinging
> or whatever i get deassociated again, associated, dis... and so on.
> 6. ifconfig ath0 192.168.178.5
>
> Using wpa_supplicant I can't ping the hostapd side altough there are
> messages that I'm associated (which can be seen from the iwlist output
> also).
>
> ping 192.168.178.10 results in a "Destination Host Unreachable"
>
> Maybe I'm doing something completely wrong and I simply can't see it.
>
> Thanks in advice,
> Joachim
>
> ======= my config ===========
>
> interface=ath0
> driver=madwifi
> logger_syslog=-1
> logger_syslog_level=2
> logger_stdout=-1
> logger_stdout_level=2
> debug=4
> dump_file=/tmp/hostapd.dump
> ssid=wpa-test
> eap_message=hello
> eapol_key_index_workaround=0
> # bit1 = IEEE 802.11i/RSN (WPA2)
> wpa=0
> wpa_psk=0e6529e1fc2430fff55b08419b7963eaea569a0bacf68a6089a892465f18c8a3
> wpa_key_mgmt=WPA-PSK WPA-EAP
> wpa_pairwise=TKIP
> wpa_group_rekey=600
> wpa_gmk_rekey=86400
>
> ======= output of the serverside ===============
>
> root at moon:/usr/src/hostap/hostapd# Wireless event: cmd=0x8b19 len=12
> Wireless event: cmd=0x8c03 len=20
> ath0: STA 00:0e:35:63:3e:f2 IEEE 802.11: associated
>   New STA
> madwifi_sta_clear_stats: addr=00:0e:35:63:3e:f2
> Wireless event: cmd=0x8c02 len=100
> Custom wireless event: 'STA-TRAFFIC-STAT
> mac=00:0e:35:63:3e:f2
> rx_packets=1
> tx_packets=0
> rx_bytes=18
> tx_bytes=0
> '
> Wireless event: cmd=0x8c04 len=20
> ath0: STA 00:0e:35:63:3e:f2 IEEE 802.11: deassociated
> Wireless event: cmd=0x8c03 len=20
> ath0: STA 00:0e:35:63:3e:f2 IEEE 802.11: associated
>   New STA
> madwifi_sta_clear_stats: addr=00:0e:35:63:3e:f2
> Wireless event: cmd=0x8c02 len=100
> Custom wireless event: 'STA-TRAFFIC-STAT
> mac=00:0e:35:63:3e:f2
> rx_packets=1
> tx_packets=0
> rx_bytes=18
> tx_bytes=0
> '
> Wireless event: cmd=0x8c04 len=20
> ath0: STA 00:0e:35:63:3e:f2 IEEE 802.11: deassociated
> Wireless event: cmd=0x8c03 len=20
> ath0: STA 00:0e:35:63:3e:f2 IEEE 802.11: associated
>   New STA
> madwifi_sta_clear_stats: addr=00:0e:35:63:3e:f2
> Wireless event: cmd=0x8c02 len=100
> Custom wireless event: 'STA-TRAFFIC-STAT
> mac=00:0e:35:63:3e:f2
> rx_packets=1
> tx_packets=0
> rx_bytes=18
> tx_bytes=0
> '
> Wireless event: cmd=0x8c04 len=20
> ath0: STA 00:0e:35:63:3e:f2 IEEE 802.11: deassociated
> Wireless event: cmd=0x8c03 len=20
> ath0: STA 00:0e:35:63:3e:f2 IEEE 802.11: associated
>   New STA
> madwifi_sta_clear_stats: addr=00:0e:35:63:3e:f2
> Wireless event: cmd=0x8c02 len=100
> Custom wireless event: 'STA-TRAFFIC-STAT
> mac=00:0e:35:63:3e:f2
> rx_packets=1
> tx_packets=0
> rx_bytes=18
> tx_bytes=0
> '
> Wireless event: cmd=0x8c04 len=20
> ath0: STA 00:0e:35:63:3e:f2 IEEE 802.11: deassociated
> Wireless event: cmd=0x8c03 len=20
> ath0: STA 00:0e:35:63:3e:f2 IEEE 802.11: associated
>   New STA
> madwifi_sta_clear_stats: addr=00:0e:35:63:3e:f2



More information about the HostAP mailing list