I'm trying to setup an AP with a run0 interface on latest 8-STABLE but
apparently 802.11 association fails:
Oct 31 16:21:30 ursaminor hostapd: wlan0: STA 00:22:69:07:30:9e IEEE
802.11: associated
Oct 31 16:21:33 ursaminor hostapd: wlan0: STA 00:22:69:07:30:9e IEEE
802.11: deauthenticated due to local deauth request
Oct 31 16:21:33 ursaminor hostapd: wlan0: STA 00:22:69:07:30:9e IEEE
802.11: deassociated
Oct 31 16:21:35 ursaminor hostapd: wlan0: STA 00:22:69:07:30:9e IEEE
802.11: associated
Oct 31 16:21:38 ursaminor hostapd: wlan0: STA 00:22:69:07:30:9e IEEE
802.11: deauthenticated due to local deauth request
Oct 31 16:21:38 ursaminor hostapd: wlan0: STA 00:22:69:07:30:9e IEEE
802.11: deassociated
etc. Apparently the client never comes to the phase to receive DHCP address.
The client in this case is WinXP and the setup did work with 7-STABLE,
though with a bug in the rum driver which caused regular kernel panics
on the AP.
The devices are configured like this:
rum0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 2290
ether 00:1c:f0:9d:08:b3
media: IEEE 802.11 Wireless Ethernet autoselect mode 11g <hostap>
status: running
wlan0: flags=8943<UP,BROADCAST,RUNNING,PROMISC,SIMPLEX,MULTICAST>
metric 0 mtu 1500
ether 00:1c:f0:9d:08:b3
inet6 fe80::21c:f0ff:fe9d:8b3%wlan0 prefixlen 64 scopeid 0x6
inet 10.0.0.3 netmask 0xffffff00 broadcast 10.0.0.255
media: IEEE 802.11 Wireless Ethernet autoselect mode 11g <hostap>
status: running
ssid Cosmos channel 1 (2412 Mhz 11g) bssid 00:1c:f0:9d:08:b3
country US authmode WPA privacy MIXED deftxkey 3 TKIP 2:128-bit
TKIP 3:128-bit txpower 0 scanvalid 60 protmode CTS dtimperiod 1 -dfs
hostapd.conf contains:
interface=wlan0
debug=3
ctrl_interface=/var/run/hostapd
ctrl_interface_group=wheel
ssid=Cosmos
wpa=1
wpa_passphrase=something
wpa_key_mgmt=WPA-PSK
wpa_pairwise=TKIP
Any ideas?
On 10/31/09, Ivan Voras <ivoras@gmail.com> wrote:> I'm trying to setup an AP with a run0 interface on latest 8-STABLE but > apparently 802.11 association fails: > > Oct 31 16:21:30 ursaminor hostapd: wlan0: STA 00:22:69:07:30:9e IEEE > 802.11: associated > Oct 31 16:21:33 ursaminor hostapd: wlan0: STA 00:22:69:07:30:9e IEEE > 802.11: deauthenticated due to local deauth request > Oct 31 16:21:33 ursaminor hostapd: wlan0: STA 00:22:69:07:30:9e IEEE > 802.11: deassociated > Oct 31 16:21:35 ursaminor hostapd: wlan0: STA 00:22:69:07:30:9e IEEE > 802.11: associated > Oct 31 16:21:38 ursaminor hostapd: wlan0: STA 00:22:69:07:30:9e IEEE > 802.11: deauthenticated due to local deauth request > Oct 31 16:21:38 ursaminor hostapd: wlan0: STA 00:22:69:07:30:9e IEEE > 802.11: deassociated > > etc. Apparently the client never comes to the phase to receive DHCP address. > > The client in this case is WinXP and the setup did work with 7-STABLE, > though with a bug in the rum driver which caused regular kernel panics > on the AP. >I tried same one with rum(4) as AP and ndis(4) as client on same machine(some version of 8.0 - CURRENT). ndis client (configured via wpa_supplicant) would keep auth and deauth all the time. I came to conclusion that rum is broken. But I think I remmember that bwi(4) (as a client) did not have such problem ... (I will test again to see)
On 10/31/09, Paul B Mahol <onemda@gmail.com> wrote:> On 10/31/09, Ivan Voras <ivoras@gmail.com> wrote: >> I'm trying to setup an AP with a run0 interface on latest 8-STABLE but >> apparently 802.11 association fails: >> >> Oct 31 16:21:30 ursaminor hostapd: wlan0: STA 00:22:69:07:30:9e IEEE >> 802.11: associated >> Oct 31 16:21:33 ursaminor hostapd: wlan0: STA 00:22:69:07:30:9e IEEE >> 802.11: deauthenticated due to local deauth request >> Oct 31 16:21:33 ursaminor hostapd: wlan0: STA 00:22:69:07:30:9e IEEE >> 802.11: deassociated >> Oct 31 16:21:35 ursaminor hostapd: wlan0: STA 00:22:69:07:30:9e IEEE >> 802.11: associated >> Oct 31 16:21:38 ursaminor hostapd: wlan0: STA 00:22:69:07:30:9e IEEE >> 802.11: deauthenticated due to local deauth request >> Oct 31 16:21:38 ursaminor hostapd: wlan0: STA 00:22:69:07:30:9e IEEE >> 802.11: deassociated >> >> etc. Apparently the client never comes to the phase to receive DHCP >> address. >> >> The client in this case is WinXP and the setup did work with 7-STABLE, >> though with a bug in the rum driver which caused regular kernel panics >> on the AP. >> > > I tried same one with rum(4) as AP and ndis(4) as client on same > machine(some version of 8.0 - CURRENT). ndis client (configured via > wpa_supplicant) > would keep auth and deauth all the time. > I came to conclusion that rum is broken. But I think I remmember that > bwi(4) (as a client) > did not have such problem ... (I will test again to see)Well, I tried again and I got similar output like yours if I use wrong password. And with correct password client reauth all the time, maybe I need to setup ndis_events(8) ....
Ivan Voras
2009-Nov-01 22:20 UTC
hostapd "deauthenticated due to local deauth request" - possibly a rum(4) problem?
Paul B Mahol wrote:> On 10/31/09, Paul B Mahol <onemda@gmail.com> wrote: >> On 10/31/09, Ivan Voras <ivoras@gmail.com> wrote: >>> I'm trying to setup an AP with a run0 interface on latest 8-STABLE but >>> apparently 802.11 association fails: >>> >>> Oct 31 16:21:30 ursaminor hostapd: wlan0: STA 00:22:69:07:30:9e IEEE >>> 802.11: associated >>> Oct 31 16:21:33 ursaminor hostapd: wlan0: STA 00:22:69:07:30:9e IEEE >>> 802.11: deauthenticated due to local deauth request >>> Oct 31 16:21:33 ursaminor hostapd: wlan0: STA 00:22:69:07:30:9e IEEE >>> 802.11: deassociated >>> >>> etc. Apparently the client never comes to the phase to receive DHCP >>> address. >>> >>> The client in this case is WinXP and the setup did work with 7-STABLE, >>> though with a bug in the rum driver which caused regular kernel panics >>> on the AP. >>> >> I tried same one with rum(4) as AP and ndis(4) as client on same >> machine(some version of 8.0 - CURRENT). ndis client (configured via >> wpa_supplicant) >> would keep auth and deauth all the time. >> I came to conclusion that rum is broken. But I think I remmember that >> bwi(4) (as a client) >> did not have such problem ... (I will test again to see) > > Well, I tried again and I got similar output like yours if I use wrong > password. And with correct password client reauth all the time, maybe > I need to setup ndis_events(8) ....I Googled a bit and it looks like in the Linuxworld problems such as this appear to be caused at the driver level :( It seems the only improvement in rum(4) between 7-stable and 8-stable are that it doesn't promptly panic the kernel any more :)