Wireless stoped working
-
OK guys I think we are onto something here. in the system logs it says this.
Mar 28 05:38:11 hostapd: ral0: STA 00:19:d2:4e:9a:5c WPA: group key handshake completed (RSN)
Mar 28 05:37:55 dnsmasq[746]: using nameserver 194.106.56.6#53
Mar 28 05:37:55 dnsmasq[746]: using nameserver 194.106.33.42#53
Mar 28 05:37:55 dnsmasq[746]: reading /etc/resolv.conf
Mar 28 05:37:55 dhcpd: uid lease 10.255.0.97 for client 00:20:d2:4e:9a:5c is duplicate on 10.255.0/24
Mar 28 05:37:55 hostapd: ral0: STA 00:19:d2:4e:9a:5c WPA: pairwise key handshake completed (RSN)
Mar 28 05:37:55 hostapd: ral0: STA 00:19:d2:4e:9a:5c IEEE 802.11: associatedBut in the DHCP sevrer I have
00:20:d2:4e:9a:5c 10.255.0.7
The IP address I get assigned is 10.255.0.7. I have rebooted the system a few times but same thing.
-
The wireless is now working after laptop being connected to anouther wireless and now it seems to be working again. I have this in my system logs.
Mar 28 16:39:12 hostapd: ral0: STA 00:20:d2:4e:9a:5c WPA: group key handshake completed (RSN)
Mar 28 16:38:12 hostapd: ral0: STA 00:20:d2:4e:9a:5c WPA: group key handshake completed (RSN)
Mar 28 16:37:29 PingMonitor[84158]: 10.2.1.14 is DOWN, previous state was UP .. Running /usr/local/pkg/tinydns_down.php
Mar 28 16:37:12 last message repeated 2 times
Mar 28 16:35:12 last message repeated 2 times
Mar 28 16:33:12 hostapd: ral0: STA 00:20:d2:4e:9a:5c WPA: group key handshake completed (RSN)
Mar 28 16:32:12 hostapd: ral0: STA 00:20:d2:4e:9a:5c WPA: group key handshake completed (RSN)
Mar 28 16:31:58 PingMonitor[82613]: 10.2.1.14 is DOWN, previous state was UP .. Running /usr/local/pkg/tinydns_down.php
Mar 28 16:31:12 hostapd: ral0: STA 00:20:d2:4e:9a:5c WPA: group key handshake completed (RSN)
Mar 28 16:30:12 last message repeated 2 times
Mar 28 16:28:12 hostapd: ral0: STA 00:20:d2:4e:9a:5c WPA: group key handshake completed (RSN)
Mar 28 16:27:12 hostapd: ral0: STA 00:20:d2:4e:9a:5c WPA: group key handshake completed (RSN)
Mar 28 16:26:27 PingMonitor[81157]: 10.2.1.14 is DOWN, previous state was UP .. Running /usr/local/pkg/tinydns_down.php
Mar 28 16:26:12 hostapd: ral0: STA 00:20:d2:4e:9a:5c WPA: group key handshake completed (RSN)
Mar 28 16:25:12 hostapd: ral0: STA 00:20:d2:4e:9a:5c WPA: group key handshake completed (RSN)
Mar 28 16:24:12 hostapd: ral0: STA 00:20:d2:4e:9a:5c WPA: group key handshake completed (RSN)
Mar 28 16:24:05 hostapd: ral0: STA 00:20:d2:4e:9a:5c WPA: pairwise key handshake completed (RSN)
Mar 28 16:24:05 hostapd: ral0: STA 00:20:d2:4e:9a:5c IEEE 802.11: associatedSo I am wondering if it is having truble with the DHCP.
-
I have a very similar issue. I have found that I am forced to login to the web configurator, then disable save, then re-enable and save. After that it works again for a while.
The wireless is now working after laptop being connected to anouther wireless and now it seems to be working again. I have this in my system logs.
Mar 28 16:39:12 hostapd: ral0: STA 00:20:d2:4e:9a:5c WPA: group key handshake completed (RSN)
Mar 28 16:38:12 hostapd: ral0: STA 00:20:d2:4e:9a:5c WPA: group key handshake completed (RSN)
Mar 28 16:37:29 PingMonitor[84158]: 10.2.1.14 is DOWN, previous state was UP .. Running /usr/local/pkg/tinydns_down.php
Mar 28 16:37:12 last message repeated 2 times
Mar 28 16:35:12 last message repeated 2 times
Mar 28 16:33:12 hostapd: ral0: STA 00:20:d2:4e:9a:5c WPA: group key handshake completed (RSN)
Mar 28 16:32:12 hostapd: ral0: STA 00:20:d2:4e:9a:5c WPA: group key handshake completed (RSN)
Mar 28 16:31:58 PingMonitor[82613]: 10.2.1.14 is DOWN, previous state was UP .. Running /usr/local/pkg/tinydns_down.php
Mar 28 16:31:12 hostapd: ral0: STA 00:20:d2:4e:9a:5c WPA: group key handshake completed (RSN)
Mar 28 16:30:12 last message repeated 2 times
Mar 28 16:28:12 hostapd: ral0: STA 00:20:d2:4e:9a:5c WPA: group key handshake completed (RSN)
Mar 28 16:27:12 hostapd: ral0: STA 00:20:d2:4e:9a:5c WPA: group key handshake completed (RSN)
Mar 28 16:26:27 PingMonitor[81157]: 10.2.1.14 is DOWN, previous state was UP .. Running /usr/local/pkg/tinydns_down.php
Mar 28 16:26:12 hostapd: ral0: STA 00:20:d2:4e:9a:5c WPA: group key handshake completed (RSN)
Mar 28 16:25:12 hostapd: ral0: STA 00:20:d2:4e:9a:5c WPA: group key handshake completed (RSN)
Mar 28 16:24:12 hostapd: ral0: STA 00:20:d2:4e:9a:5c WPA: group key handshake completed (RSN)
Mar 28 16:24:05 hostapd: ral0: STA 00:20:d2:4e:9a:5c WPA: pairwise key handshake completed (RSN)
Mar 28 16:24:05 hostapd: ral0: STA 00:20:d2:4e:9a:5c IEEE 802.11: associatedSo I am wondering if it is having truble with the DHCP.
-
I have posted some more of my findings here.
http://forum.pfsense.org/index.php?topic=4127.0
The devs have been very quiet on this problem but I think they have been very busy on other things. This is a problem that comes more aparant the more people you have on the wireless and if you have high traffic.
It seems to me it is a routing problem when in bridge mode. I had 2 devices on the wireless yesterday and the whole connection droped out. I have found that WPA2 on AES seems to be more stable. Would be nice to find out if we need a driver upgrade from the manufacture webby or if this is something that needs to be tweeked in pfsense.
-
Either way this is a FreeBSD kernel issue, not a pfSense issue. That is why we have been quiet. We have been fixing pfSense specific bugs.
-
no problm sullrich I had gatherd that you were very busy with this time filewall thing etc. is somthing that can be fixed??? if not or maybe somtime in distant futurencan we lock the thread and just list it as a known problem.
-
It's driver/freebsd related. We can't fix it on the pfSense end. Also this doesn't seem to happen with all the wireless interfaces/drivers that are available.
-
so would it be worth changing the inbuilt drivers for new ones???
-
We use what freebsd provides mostly and don't add third party drivers usually.
-
Well me and programing don't go tryed it and failed. I have found this if anyone knows what they are doing and wants to tinker.
http://www.freebsd.org/cgi/man.cgi?query=ural&sektion=4&manpath=FreeBSD+6.0-RELEASE
http://damien.bergamini.free.fr/ral/
http://rt2x00.serialmonkey.com/wiki/index.php?title=Main_Page
http://www.ralinktech.com/ralink/Home/Support/Linux.html
I guess we will have to see what freeBSD do or if someone devlops a more reliable driver.