Page 1 of 4
reassociation problem
Posted: Wed Jun 03, 2009 8:00 am
by crisman
I'm using latest bleeding-edge of gargoyle with my fonera to connect to my main wireless router. I set fonera as gateway and in wireless mode I choose Client+AP. In the second virtual interface ( the AP) I set a wpa2 key. I have problems because fonera disconnects me every few seconds. This is the log from logread command:
Code: Select all
Jun 3 12:48:27 OpenWrt daemon.info hostapd: ath1: STA 00:1f:3c:30:0d:fb IEEE 802.11: associated
Jun 3 12:48:27 OpenWrt daemon.info hostapd: ath1: STA 00:1f:3c:30:0d:fb RADIUS: starting accounting session 00000420-00000000
Jun 3 12:48:27 OpenWrt daemon.info hostapd: ath1: STA 00:1f:3c:30:0d:fb WPA: pairwise key handshake completed (RSN)
Jun 3 12:48:27 OpenWrt daemon.info dnsmasq[4458]: DHCPREQUEST(br-lan) 192.168.247.129 00:1f:3c:30:0d:fb
Jun 3 12:48:27 OpenWrt daemon.info dnsmasq[4458]: DHCPNAK(br-lan) 192.168.247.129 00:1f:3c:30:0d:fb wrong network
Jun 3 12:48:31 OpenWrt daemon.info dnsmasq[4458]: DHCPDISCOVER(br-lan) 192.168.247.129 00:1f:3c:30:0d:fb
Jun 3 12:48:31 OpenWrt daemon.info dnsmasq[4458]: DHCPOFFER(br-lan) 192.168.1.136 00:1f:3c:30:0d:fb
Jun 3 12:48:31 OpenWrt daemon.info dnsmasq[4458]: DHCPREQUEST(br-lan) 192.168.1.136 00:1f:3c:30:0d:fb
Jun 3 12:48:31 OpenWrt daemon.info dnsmasq[4458]: DHCPACK(br-lan) 192.168.1.136 00:1f:3c:30:0d:fb Cris-PC
Jun 3 12:48:50 OpenWrt authpriv.info dropbear[4465]: Child connection from 192.168.1.6:52011
Jun 3 12:48:56 OpenWrt authpriv.notice dropbear[4465]: password auth succeeded for 'root' from 192.168.1.6:52011
Jun 3 12:51:01 OpenWrt cron.err crond[4129]: USER root pid 4475 cmd /usr/bin/set_kernel_timezone >/dev/null 2>&1
Jun 3 12:51:22 OpenWrt daemon.info hostapd: ath1: STA 00:1f:3c:30:0d:fb IEEE 802.11: associated
Jun 3 12:51:22 OpenWrt daemon.info hostapd: ath1: STA 00:1f:3c:30:0d:fb RADIUS: starting accounting session 00000420-00000001
Jun 3 12:51:22 OpenWrt daemon.info hostapd: ath1: STA 00:1f:3c:30:0d:fb WPA: pairwise key handshake completed (RSN)
Jun 3 12:51:34 OpenWrt daemon.info hostapd: ath1: STA 00:1f:3c:30:0d:fb IEEE 802.11: associated
Jun 3 12:51:34 OpenWrt daemon.info hostapd: ath1: STA 00:1f:3c:30:0d:fb RADIUS: starting accounting session 00000420-00000002
Jun 3 12:51:34 OpenWrt daemon.info hostapd: ath1: STA 00:1f:3c:30:0d:fb WPA: pairwise key handshake completed (RSN)
Jun 3 12:51:47 OpenWrt daemon.info hostapd: ath1: STA 00:1f:3c:30:0d:fb IEEE 802.11: associated
Jun 3 12:51:47 OpenWrt daemon.info hostapd: ath1: STA 00:1f:3c:30:0d:fb IEEE 802.11: associated
Jun 3 12:51:47 OpenWrt daemon.info hostapd: ath1: STA 00:1f:3c:30:0d:fb WPA: received EAPOL-Key 4/4 Pairwise with unexpected replay counter
Jun 3 12:51:49 OpenWrt daemon.info hostapd: ath1: STA 00:1f:3c:30:0d:fb IEEE 802.11: deauthenticated due to local deauth request
Jun 3 12:51:49 OpenWrt daemon.info hostapd: ath1: STA 00:1f:3c:30:0d:fb IEEE 802.11: disassociated
Jun 3 12:51:49 OpenWrt daemon.info hostapd: ath1: STA 00:1f:3c:30:0d:fb IEEE 802.11: associated
Jun 3 12:51:49 OpenWrt daemon.info hostapd: ath1: STA 00:1f:3c:30:0d:fb RADIUS: starting accounting session 00000420-00000003
Jun 3 12:51:49 OpenWrt daemon.info hostapd: ath1: STA 00:1f:3c:30:0d:fb WPA: pairwise key handshake completed (RSN)
Jun 3 12:51:50 OpenWrt daemon.info dnsmasq[4458]: DHCPREQUEST(br-lan) 192.168.1.136 00:1f:3c:30:0d:fb
Jun 3 12:51:50 OpenWrt daemon.info dnsmasq[4458]: DHCPACK(br-lan) 192.168.1.136 00:1f:3c:30:0d:fb Cris-PC
Jun 3 12:52:02 OpenWrt daemon.info hostapd: ath1: STA 00:1f:3c:30:0d:fb IEEE 802.11: associated
Jun 3 12:52:02 OpenWrt daemon.info hostapd: ath1: STA 00:1f:3c:30:0d:fb RADIUS: starting accounting session 00000420-00000004
Jun 3 12:52:02 OpenWrt daemon.info hostapd: ath1: STA 00:1f:3c:30:0d:fb WPA: pairwise key handshake completed (RSN)
Jun 3 12:52:14 OpenWrt daemon.info hostapd: ath1: STA 00:1f:3c:30:0d:fb IEEE 802.11: associated
Jun 3 12:52:14 OpenWrt daemon.info hostapd: ath1: STA 00:1f:3c:30:0d:fb RADIUS: starting accounting session 00000420-00000005
Jun 3 12:52:14 OpenWrt daemon.info hostapd: ath1: STA 00:1f:3c:30:0d:fb WPA: pairwise key handshake completed (RSN)
Jun 3 12:52:25 OpenWrt daemon.info hostapd: ath1: STA 00:1f:3c:30:0d:fb IEEE 802.11: associated
Jun 3 12:52:25 OpenWrt daemon.info hostapd: ath1: STA 00:1f:3c:30:0d:fb RADIUS: starting accounting session 00000420-00000006
Jun 3 12:52:25 OpenWrt daemon.info hostapd: ath1: STA 00:1f:3c:30:0d:fb WPA: pairwise key handshake completed (RSN)
Jun 3 12:52:37 OpenWrt daemon.info hostapd: ath1: STA 00:1f:3c:30:0d:fb IEEE 802.11: associated
Jun 3 12:52:37 OpenWrt daemon.info hostapd: ath1: STA 00:1f:3c:30:0d:fb RADIUS: starting accounting session 00000420-00000007
Jun 3 12:52:37 OpenWrt daemon.info hostapd: ath1: STA 00:1f:3c:30:0d:fb WPA: pairwise key handshake completed (RSN)
Jun 3 12:52:46 OpenWrt daemon.info hostapd: ath1: STA 00:1f:3c:30:0d:fb IEEE 802.11: associated
Jun 3 12:52:46 OpenWrt daemon.info hostapd: ath1: STA 00:1f:3c:30:0d:fb RADIUS: starting accounting session 00000420-00000008
Jun 3 12:52:46 OpenWrt daemon.info hostapd: ath1: STA 00:1f:3c:30:0d:fb WPA: pairwise key handshake completed (RSN)
As you can see my pc is being reassociated every 10 seconds. This is very annoying because the navigation is instable.
Have you any hints about this bug?
Best regards
Re: reassociation problem
Posted: Sun Jun 07, 2009 6:44 am
by Dan
I mentioned the problem about maintaining contact with the Main AP after power cycling in this post which turns out to be a known bug to be fixed:-
http://www.gargoyle-router.com/phpbb/vi ... ?f=6&t=163
You mention you are using WPA?
If you can try a different method and perhaps no encryption, it would be useful to Eric so he hunt down this bug.
In my case I am away from home and using the bleeding edge to associate with Unencrypted Hotspots. So I cannot test it.
Re: reassociation problem
Posted: Sun Jun 07, 2009 3:47 pm
by Eric
I have uploaded new firmware and I believe this problem is solved.
This issue had less to do with Gargoyle modifications and more to do with which version of the OpenWrt 8.09 branch it was using. Using the latest code seems to fix the problem. Please let me know if you're still having problems with this.
Re: reassociation problem
Posted: Sat Jun 20, 2009 8:51 am
by crisman
sorry to say that problem persist with the latest revision of gargoyle:
Code: Select all
Jun 20 13:43:42 OpenWrt daemon.info dnsmasq[3828]: DHCPREQUEST(br-lan) 192.168.1.136 00:1f:3c:30:0d:fb
Jun 20 13:43:42 OpenWrt daemon.info dnsmasq[3828]: DHCPACK(br-lan) 192.168.1.136 00:1f:3c:30:0d:fb Cris-PC
Jun 20 13:43:57 OpenWrt daemon.info hostapd: ath1: STA 00:1f:3c:30:0d:fb IEEE 802.11: associated
Jun 20 13:43:57 OpenWrt daemon.info hostapd: ath1: STA 00:1f:3c:30:0d:fb RADIUS: starting accounting session 00000164-00000003
Jun 20 13:43:57 OpenWrt daemon.info hostapd: ath1: STA 00:1f:3c:30:0d:fb WPA: pairwise key handshake completed (RSN)
Jun 20 13:44:11 OpenWrt daemon.info hostapd: ath1: STA 00:1f:3c:30:0d:fb IEEE 802.11: associated
Jun 20 13:44:11 OpenWrt daemon.info hostapd: ath1: STA 00:1f:3c:30:0d:fb RADIUS: starting accounting session 00000164-00000004
Jun 20 13:44:11 OpenWrt daemon.info hostapd: ath1: STA 00:1f:3c:30:0d:fb WPA: pairwise key handshake completed (RSN)
Jun 20 13:44:13 OpenWrt authpriv.info dropbear[4213]: Child connection from 192.168.1.136:50996
Jun 20 13:44:22 OpenWrt daemon.info hostapd: ath1: STA 00:1f:3c:30:0d:fb IEEE 802.11: associated
Jun 20 13:44:22 OpenWrt daemon.info hostapd: ath1: STA 00:1f:3c:30:0d:fb RADIUS: starting accounting session 00000164-00000005
Jun 20 13:44:22 OpenWrt daemon.info hostapd: ath1: STA 00:1f:3c:30:0d:fb WPA: pairwise key handshake completed (RSN)
Jun 20 13:44:23 OpenWrt authpriv.notice dropbear[4213]: password auth succeeded for 'root' from 192.168.1.136:50996
Jun 20 13:44:42 OpenWrt daemon.info hostapd: ath1: STA 00:1f:3c:30:0d:fb IEEE 802.11: associated
Jun 20 13:44:42 OpenWrt daemon.info hostapd: ath1: STA 00:1f:3c:30:0d:fb RADIUS: starting accounting session 00000164-00000006
Jun 20 13:44:42 OpenWrt daemon.info hostapd: ath1: STA 00:1f:3c:30:0d:fb WPA: pairwise key handshake completed (RSN)
Jun 20 13:44:55 OpenWrt daemon.info hostapd: ath1: STA 00:1f:3c:30:0d:fb IEEE 802.11: associated
Jun 20 13:44:55 OpenWrt daemon.info hostapd: ath1: STA 00:1f:3c:30:0d:fb RADIUS: starting accounting session 00000164-00000007
Jun 20 13:44:55 OpenWrt daemon.info hostapd: ath1: STA 00:1f:3c:30:0d:fb WPA: pairwise key handshake completed (RSN)
Jun 20 13:45:06 OpenWrt daemon.info hostapd: ath1: STA 00:1f:3c:30:0d:fb IEEE 802.11: associated
Jun 20 13:45:06 OpenWrt daemon.info hostapd: ath1: STA 00:1f:3c:30:0d:fb RADIUS: starting accounting session 00000164-00000008
Jun 20 13:45:06 OpenWrt daemon.info hostapd: ath1: STA 00:1f:3c:30:0d:fb WPA: pairwise key handshake completed (RSN)
Jun 20 13:45:09 OpenWrt authpriv.info dropbear[4213]: exit after auth (root): error reading: Connection reset by peer
Jun 20 13:45:17 OpenWrt daemon.info hostapd: ath1: STA 00:1f:3c:30:0d:fb IEEE 802.11: associated
Jun 20 13:45:17 OpenWrt daemon.info hostapd: ath1: STA 00:1f:3c:30:0d:fb RADIUS: starting accounting session 00000164-00000009
Jun 20 13:45:17 OpenWrt daemon.info hostapd: ath1: STA 00:1f:3c:30:0d:fb WPA: pairwise key handshake completed (RSN)
Jun 20 13:45:18 OpenWrt authpriv.info dropbear[4221]: Child connection from 192.168.1.136:51001
Jun 20 13:45:29 OpenWrt daemon.info hostapd: ath1: STA 00:1f:3c:30:0d:fb IEEE 802.11: associated
Jun 20 13:45:29 OpenWrt daemon.info hostapd: ath1: STA 00:1f:3c:30:0d:fb RADIUS: starting accounting session 00000164-0000000A
Jun 20 13:45:29 OpenWrt daemon.info hostapd: ath1: STA 00:1f:3c:30:0d:fb WPA: pairwise key handshake completed (RSN)
Jun 20 13:45:31 OpenWrt authpriv.notice dropbear[4221]: password auth succeeded for 'root' from 192.168.1.136:51001
Jun 20 13:45:42 OpenWrt daemon.info hostapd: ath1: STA 00:1f:3c:30:0d:fb IEEE 802.11: associated
Jun 20 13:45:42 OpenWrt daemon.info hostapd: ath1: STA 00:1f:3c:30:0d:fb RADIUS: starting accounting session 00000164-0000000B
Jun 20 13:45:42 OpenWrt daemon.info hostapd: ath1: STA 00:1f:3c:30:0d:fb WPA: pairwise key handshake completed (RSN)
Jun 20 13:46:05 OpenWrt daemon.info hostapd: ath1: STA 00:1f:3c:30:0d:fb IEEE 802.11: associated
Jun 20 13:46:05 OpenWrt daemon.info hostapd: ath1: STA 00:1f:3c:30:0d:fb RADIUS: starting accounting session 00000164-0000000C
Jun 20 13:46:05 OpenWrt daemon.info hostapd: ath1: STA 00:1f:3c:30:0d:fb WPA: pairwise key handshake completed (RSN)
If using no encryption all is OK, but when using WPA or WPA2 compare problem of reassociation.
I think it's openwrt related, but we need a solution to this because it's not good to have a unsecured wifi
Re: reassociation problem
Posted: Sun Jun 21, 2009 10:36 am
by Eric
Ok, thanks for reporting this. I'll see if I can figure out what's going on.
Re: reassociation problem
Posted: Sun Jun 28, 2009 4:47 am
by crisman
any news?
Re: reassociation problem
Posted: Sun Jun 28, 2009 11:08 am
by Eric
Looking at your log, I just realized you're connecting with WPA2 RADIUS instead of WPA2 PSK. It works for WPA2 PSK, which is why I originally thought it was corrected.
I think this is related to
this bug., which is, in a way, the opposite of what you report. AP+Client mode doesn't seem to work properly when no encryption is set, but with WPA or WPA2 PSK it seems to work. I guess that doesn't extend to WPA or WPA2 RADIUS.
I've been pulling my hair out all weekend trying to figure out what's going on with this bug, but it's nothing obvious. I'll do what I can but the problem may be buried deep in kernel driver code that I'm not particularly familiar with (at least not yet). This may end up being a "known issue" for some time.
Re: reassociation problem
Posted: Sun Jun 28, 2009 11:28 am
by Eric
Update, further characterization of the problem: It seems that it fails if you have both the AP and the client with the same type of encryption or lack thereof. So both wpa2 will fail, both open will fail while if you have ap=wpa2 and sta=open, it works.
Re: reassociation problem
Posted: Sun Jun 28, 2009 2:29 pm
by crisman
I'm not using wpa radius, but I selected wpa tkip. In log messages there are infos about an accounting radius session, but I did not set anything about radius, so I don't know why this strange message id displayed.
I tried with the following config:
main ap: wpa (1) tkip
client ap: connects to wpa (1) tkip and ap is wpa2 aes (tried also wpa1 tkip).
But the problem is present also.
The only thing I think is that I never read about this "bug". I tried Gargoyle, but problem is present also in kamikaze ( branch and trunk). The latest working version (for me) is based on a revision of the 7 november 2008. I don't know why anyone has notified this bug before.
I tried also compiling kamikaze with old version of hostapd like 0.6.4, but no luck. I don't know what's the problem, but this bug exists from november 2008 and as you said this may end up being a "known issue" for a very long time.
Re: reassociation problem
Posted: Tue Jun 30, 2009 12:23 pm
by crisman
Eric wrote:Update, further characterization of the problem: It seems that it fails if you have both the AP and the client with the same type of encryption or lack thereof. So both wpa2 will fail, both open will fail while if you have ap=wpa2 and sta=open, it works.
I'm not at home now and I can't make more tests. I have an idea: start hostapd by console with debug ( very verbose) enabled and see if we can find why reassociation is repeated every 10 seconds.
Is it a good idea? Can you try please?
Best regards