Stuck Beacon . constantly why



  • Hi all,

    please could you have a look at my log and help me understand why i am constantly having stuck beacon on my wifi. Is there a fix ?

    Jul 15 19:06:36        syslogd: kernel boot file is /boot/kernel/kernel
        Jul 15 21:09:04        php-fpm: /index.php: Successful login for user 'admin' from: 10.0.8.10
        Jul 15 21:09:04        php-fpm: /index.php: Successful login for user 'admin' from: 10.0.8.10
        Jul 15 21:09:04        sshlockout[16846]: sshlockout/webConfigurator v3.0 starting up
        Jul 15 22:38:46        kernel: ath0: stuck beacon; resetting (bmiss count 4)
        Jul 15 23:41:21        kernel: ath0: stuck beacon; resetting (bmiss count 4)
        Jul 16 00:00:42        kernel: ath0: stuck beacon; resetting (bmiss count 4)
        Jul 16 00:02:44        kernel: ath0: stuck beacon; resetting (bmiss count 4)
        Jul 16 00:02:45        kernel: ath0: stuck beacon; resetting (bmiss count 4)
        Jul 16 00:04:49        kernel: ath0: stuck beacon; resetting (bmiss count 4)
        Jul 16 00:05:05        kernel: ath0: stuck beacon; resetting (bmiss count 4)
        Jul 16 00:05:40        kernel: ath0: stuck beacon; resetting (bmiss count 4)
        Jul 16 00:06:04        kernel: ath0: stuck beacon; resetting (bmiss count 4)
        Jul 16 00:08:10        kernel: ath0: stuck beacon; resetting (bmiss count 4)
        Jul 16 01:01:00        php: rc.dyndns.update: phpDynDNS (b*****.co.uk): No change in my IP address and/or 25 days has not passed. Not updating dynamic DNS entry.
        Jul 16 09:09:27        kernel: ath0: stuck beacon; resetting (bmiss count 4)
        Jul 16 09:20:06        kernel: ath0: stuck beacon; resetting (bmiss count 4)
        Jul 16 09:21:16        php-fpm[97035]: /index.php: Successful login for user 'admin' from: 192.168.4.37
        Jul 16 09:21:16        php-fpm[97035]: /index.php: Successful login for user 'admin' from: 192.168.4.37


  • Banned

    No, no fixes. Get a proper AP.



  • I can only suggest you use a version of pfSense above 2.2.1 because that beacon issue was resolved in 2.2.2. This was an old bug that got fixed. There are other error messages now -but not nearly as much. I would suggest doing a site survey with netstumbler or similar and find the gaps in frequencies. Beacon errors were about radio signal congestion.
    Please tell us if it helps.



  • Straight from the developers mouth:

    Which could be (and this isn't an exhaustive list):

    • due to DMA activity (eg, it can't DMA because the bus is busy);
    • due to incorrect programming (eg something I found w/ staggered
      beacons and the content-after-beacon window programming, this upset
      some of the later generation MACs);
    • due to busy air (ie the baseband thinks the air is constantly too
      busy to transmit);
    • due to incorrect radio programming (eg the ANI code changes the
      radio parameters in a way that makes things more sensitive to busy
      air);
    • due to incorrect antenna selection/programming/design - eg, the
      noise floor calibration occurs based on a non-attached antenna, but
      the busy air is received on the attached antenna, causing some very
      incorrect values to be programmed in.
    • completely busted hardware - eg, you may find your hardware has
      noise spurs in the 2.4ghz region. It's sometimes possible to program
      around these but quite often it isn't. (And who knows what the
      manufacturer put in their driver to work around this.)

    Quoted from an 2011 post by Adrain Chadd



  • @Phishfry:

    I can only suggest you use a version of pfSense above 2.2.1 because that beacon issue was resolved in 2.2.2.

    I still got it with 2.2.2 and 2.2.3. I've now moved to an external AP (still have the card plugged in, though). No congestion, I was on channel 9 (from memory) and at least a couple of channels of room between mine and any possible neighbors. Suburbia with good distance between houses and only about 6 networks max visible. Most of the time 3 networks.


Log in to reply