WIFI: ath0: stuck beacon; resetting (bmiss count 4)



  • Hi there,

    i'm using a brand new OPNsense router with AMD APU2C4 Board und WLAN-Modul (WLE200NX)
    i constantly get this kernel bacon system logs and Wifi is very slow on iOS devices. We changed everything again and again, channels, n or g standard whatsoever. Kernel errors never went away. Any idea what can be wrong?

    Dec 21 15:46:03 	kernel 		ath0: stuck beacon; resetting (bmiss count 4)
    Dec 21 15:46:03 	kernel 		ath0: stuck beacon; resetting (bmiss count 4)
    Dec 21 15:46:03 	kernel 		ath0: stuck beacon; resetting (bmiss count 4)
    Dec 21 15:46:03 	kernel 		ath0: stuck beacon; resetting (bmiss count 4)
    Dec 21 15:46:03 	kernel 		ath0: stuck beacon; resetting (bmiss count 4)
    Dec 21 15:46:04 	kernel 		ath0: stuck beacon; resetting (bmiss count 4)
    Dec 21 15:46:04 	kernel 		ath0: stuck beacon; resetting (bmiss count 4)
    Dec 21 15:46:04 	kernel 		ath0: stuck beacon; resetting (bmiss count 4)
    Dec 21 15:46:08 	kernel 		ath0: stuck beacon; resetting (bmiss count 4)
    Dec 21 15:46:09 	kernel 		ath0: stuck beacon; resetting (bmiss count 4)
    Dec 21 15:46:09 	kernel 		ath0: stuck beacon; resetting (bmiss count 4)
    Dec 21 15:46:09 	kernel 		ath0: stuck beacon; resetting (bmiss count 4)
    Dec 21 15:46:09 	kernel 		ath0: stuck beacon; resetting (bmiss count 4)
    Dec 21 15:46:10 	kernel 		ath0: stuck beacon; resetting (bmiss count 4)
    Dec 21 15:46:10 	kernel 		ath0: stuck beacon; resetting (bmiss count 4)
    Dec 21 16:18:56 	kernel 		ath0: stuck beacon; resetting (bmiss count 4) 
    
    

  • Rebel Alliance Developer Netgate

    @hirschferkel:

    i'm using a brand new OPNsense router

    You're on the wrong forum.

    Though if you want to use pfSense with wireless, use a 2.4 snapshot from https://snapshots.pfsense.org, the APU should use the serial memstick



  • Oh sorry for the missunderstanding introduction. I guess i'm in the right forum as we installed Pfsense on the OPNsense router.



  • So after installing the 2.4 snapshot, nothing changed…

    Jan 9 12:05:51 	kernel 		ath0: stuck beacon; resetting (bmiss count 4)
    Jan 9 12:06:02 	kernel 		ath0: stuck beacon; resetting (bmiss count 4)
    Jan 9 12:06:08 	kernel 		ath0: stuck beacon; resetting (bmiss count 4)
    Jan 9 12:10:50 	kernel 		ath0: stuck beacon; resetting (bmiss count 4)
    Jan 9 12:10:57 	kernel 		ath0: stuck beacon; resetting (bmiss count 4)
    Jan 9 12:10:57 	kernel 		ath0: bb hang detected (0x4)
    Jan 9 12:10:57 	kernel 		ath0: stuck beacon; resetting (bmiss count 4)
    Jan 9 12:11:01 	kernel 		ath0: stuck beacon; resetting (bmiss count 4)
    Jan 9 12:11:03 	kernel 		ath0: stuck beacon; resetting (bmiss count 4)
    Jan 9 12:11:46 	kernel 		ath0: stuck beacon; resetting (bmiss count 4)
    Jan 9 12:13:12 	kernel 		ath0: stuck beacon; resetting (bmiss count 4)
    Jan 9 12:13:13 	kernel 		ath0: stuck beacon; resetting (bmiss count 4)
    Jan 9 12:14:07 	kernel 		ath0: stuck beacon; resetting (bmiss count 4)
    Jan 9 12:14:19 	kernel 		ath0: stuck beacon; resetting (bmiss count 4)
    Jan 9 12:14:20 	kernel 		ath0: stuck beacon; resetting (bmiss count 4)
    Jan 9 12:14:25 	kernel 		ath0: stuck beacon; resetting (bmiss count 4) 
    


  • common issue on pfsense so either live with it or just get a dedicated AP or maybe just move to a Linux based firewall distribution. I actually had this issues with wide varieties of Atheros cards and all of them had the similar beacon issue, using a linux based firewall like openwrt immediately solved it, probably due to better driver implementation.

    but I had good experience with ralink based chipsets though, none of them had a beacon issue that I encounter, the bad thing is it doesnt have multiple SSID feature and doesnt support traffic shaping.



  • The only problem why living with it is difficult is that the stuck beacon issue causes network delays in loading internet connections… thought i would buy a professional hardware.


  • Banned

    @hirschferkel:

    thought i would buy a professional hardware.

    Yeah, indeed. Get an Access Point, hook it to your switch and move on. UBNT gear is good for this purpose, as an example.


  • Rebel Alliance Developer Netgate

    An external AP is definitely the way to go. That said, "stuck beacon" errors generally result from noise/busy channels. I used to see them on occasion but I haven't seen a single stuck beacon with wireless on 2.4.



  • O.k. but here we go… we use 2.4 and there is still the stuck beacon issue.
    @jimp:

    An external AP is definitely the way to go. That said, "stuck beacon" errors generally result from noise/busy channels. I used to see them on occasion but I haven't seen a single stuck beacon with wireless on 2.4.


  • Rebel Alliance Developer Netgate

    Then try another channel, or use an AP.

    There's a reason we don't recommend using wireless :-)

    It can work, but it's difficult to predict if it will work on any given environment. The 802.11 stack in FreeBSD 11 is much improved, but it's not without its flaws.



  • ^ trust me, we already done any kind of mix configuration like changing the regulation and country, channels, wireless standards and stuff, all of them lands on this "beacon" issue. Plus I dont agree with noisy environment issue thingy, because even the crappiest wireless router that I bough on alibaba works much better compared to pfsense paired with best miniPCIe wireless card that I had from ubiquity.

    As I mentioned above, all issues that I had is fixed by just moving distro. I point all of this issue with FreeBSD crappy wireless driver, I can assume that wireless drivers in FreeBSD works best on Client mode only, but not AP mode.

    Dont get me wrong though, pfsense is still a good firewall disto, but its just not up for job regarding witreless, I actually use pfsense as my main router firewall and a AP AC PRO dedicated AP from Ubiquity (which I should have done in the first place /sigh).


Log in to reply