hostapd frequent deauthenticates

[KojiroAK]

Binary package hint: hostapd

1.)Start hostapd
2.)Connect to hostapd with a device
3.)use the connection
After a while deauthenticates happen. Then I reconnect to the Network but it happens again and again and again.
(Actually I'm not quite sure where the Problem is, in hostapd or in my HTC Tattoo, but I would be glad if somebody could check if there is something one can do on the side of hostapd)

That's with Atheros AR5001 wlan-modul.

ProblemType: Bug
DistroRelease: Ubuntu 10.04
Package: hostapd 1:0.6.9-3
ProcVersionSignature: Ubuntu 2.6.32-21.31-generic 2.6.32.11+drm33.2
Uname: Linux 2.6.32-21-generic i686
Architecture: i386
Date: Mon Apr 26 11:40:44 2010
ExecutablePath: /usr/sbin/hostapd
InstallationMedia: Xubuntu 10.04 "Lucid Lynx" - Alpha i386 (20100411)
ProcEnviron:
 PATH=(custom, no user)
 LANG=de_CH.UTF-8
 SHELL=/bin/bash
SourcePackage: hostapd

[KojiroAK (kojiroak)]

Oh completly forgot 00:23:76:87:e6:25 is the MAC-address of the Tattoo. (in hostapd12.txt which was gahtered with -dddd)

My config is the file which comes with this Post.

[KojiroAK (kojiroak)]

O.k. I found a workaround set wpa_group_rekey=86400
But there should be paid attention, if hostapd has some problems with reauthentication.

[KojiroAK (kojiroak)]

The Problem reappeared this Time it was an Windows XP client. But it also effectet my Tattoo
00:11:95:93:08:14 is the MAC of the Windows client.

But was also happened was, that the network was showed me twice on my Tattoo, but one as wep secured. But it is secured with wpa.

[KojiroAK (kojiroak)]

Here is the config I use with hostapd

[benkillin (bennyhur)]

I also have this problem. It may be because I am sitting too close to my computer which is the ap. However, i don't believe that is the case because I should not have to reaauth just because I am too close to the ap. But, I'm not a radio expert.

So,my setup is I have a router that also provides dhcp services which is connected to a switch which is connected to my ubuntu 10.04 laptop that has a broad com wifi card using the b43 wifi driver. I wanted this computer set up as an ap so I can use my iPad in my dorm (wired only Internet). so I
Researched and set up my ubuntu laptop up so it has a bridge between eth0 and wlan0 so I don't have to run dnsmasq or dhcp3-server on my laptop since those services are already provided by my router. In my hostapd config file I have it set up so that the driver is the nl80211 and I have the bridge set to br0. So, after getting this to finally work by using the 'brctl setfd br0 0' command and setting up the hostapd config to have wpa2 authenticAtion, I was able to share the wired connection with my wifi only devices. However, for some reason i will frequently get deathbed and my device will reauth Automatically. It was happening much more frequently than the 10 minutes specified as the default value for the wpa rekeying specified in this bug.

As a side note, I had to do all of this because the network gui in ubuntu did not make it so I could just click the share button and share my wired connection over wifi. For some reason, the wireless network just did not show up. Probably becaUse of driver issues with my wifi card because if I did iwconfig wlan0 mode Master I would get an error saying it could not set the mode. 'SET failed on device wlan0 ; Invalid argument' I even followed the directions on the wiki for doing Internet sharing over wifi using ubuntu, and it did not work. This way using a bridge between wlan and eth0 And using hostapd I am able to share my wired connection securely with my devices.

[Charlie Kravetz (cjkgeek)]

Thanks for reporting this bug and any supporting documentation. Since this bug has enough information provided for a developer to begin work, I'm going to mark it as confirmed and let them handle it from here. Thanks for taking the time to make Ubuntu better!

[Charlie Kravetz (cjkgeek)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. The issue you are reporting is an upstream one and it would be nice if somebody having it could send the bug to the developers of the software by following the instructions at https://wiki.ubuntu.com/Debian/Bugs. If you have done so, please tell us the number of the upstream bug (or the link), so we can add a bugwatch that will inform us about its status. Thanks in advance.