I would like to try and fix the Atheros "stuck beacon" problem…
-
Where do I go to find the source code?
-
http://atheros.com ?
-
I thought Atheros didn't do the drivers? The FreeBSD site is a more likely starting point, but I need to know which version of the drivers are in (say) 1.2.3 of pfSense.
-
I think 1.2.3 Release is using the open HAL.
http://www.freebsd.org/cgi/cvsweb.cgi/src/sys/modules/ath/Makefile -
pfSense 1.2.3 is based on FreeBSD 7.2-RELEASE, so you can get the code by checking out RELENG_7_2 (security branch) from FreeBSD's cvs or svn repo.
-
Thanks - just need to work out how to get that out of the SVN system…
-
It may be easier to setup a pfSense builder, which as a part of its workings will also download the RELENG_7_2 FreeBSD source
http://devwiki.pfsense.org/DevelopersBootStrapAndDevIso
-
Thanks - I'll give that a go.
Mind you, after a bit of playing, it seems as if the stuck beacons aren't necessarily the problem.
I've been finding that the wireless stops working after some time and doesn't recover. However, I noticed that connecting something to the LAN port (which was unconnected but bridged to the AP) seemed to make the wireless come back to life. I've got another port of the pfSense box (not currently used) - connecting a lead from this to the LAN port seems to keep the wireless running (with about a 2% packet loss)…
-
Now that is another issue. If you are bridged to a wired LAN, then it will require something plugged into that interface in order to work.
It used to be as easy as plugging in a loopback adapter, but the last time I tried it really did require a switch.
Alternately, if you want to only occasionally use the LAN, assign your wireless interface as the LAN and then bridge your (wired) OPT interface to it. That should work.
-
Thanks, I hadn't thought of trying that :)