• Categories
  • Recent
  • Tags
  • Popular
  • Users
  • Search
  • Register
  • Login
Netgate Discussion Forum
  • Categories
  • Recent
  • Tags
  • Popular
  • Users
  • Search
  • Register
  • Login

Wireless issues with 1.2.3RC1 (stuck beacon)

Scheduled Pinned Locked Moved 1.2.3-PRERELEASE-TESTING snapshots - RETIRED
3 Posts 2 Posters 2.3k Views
Loading More Posts
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • M
    matrix200
    last edited by Apr 30, 2009, 8:57 PM Apr 30, 2009, 5:37 PM

    Not sure if this is the right forum (maybe I should post it in Wireless?)
    I have an atheros 5212 card and today I was no longer able to see my pfsense wireless.
    Correction (wistron cm9 is actually 5213 based even though reported as 5212).
    This is what comes in the logs :
    ath0: stuck beacon; resetting (bmiss count 4)
    Strange enough after a few minutes (maybe 10 or 15) the problem kinda solved itself as I was longer getting these messages and connection was restored.
    The pfsense is running on ALIX2C2 with 4 gigabyte microdrive

    Well to update on the issue , 11g became very unstable afterwards and I reverted to 11b which is somewhat more stable.
    The signal is pretty low even when standing next to the router (25-30db compared to my Asus router which is giving 50-55db).
    some pings are spiking up to 50ms or even more and lots of i/o errors show up on the interface (I think i/o errors were from the beginning but I didn't pay attention).

    Current network "hardware" :
    Running 2.2RC in Virtualbox 4.2.16.

    Retired:
    ALIX2C2 , 4 gigabyte disk cf card running 2.0 (official release).

    1 Reply Last reply Reply Quote 0
    • C
      ChillyWilly
      last edited by May 6, 2009, 10:04 AM

      I get the same error messages with my AR5416. But after doing a clean install last week and using build: 1.2.3-RC1 built on Mon Apr 27 06:14:08 EDT 2009 I haven't seen the error (yet).

      1 Reply Last reply Reply Quote 0
      • M
        matrix200
        last edited by Jun 22, 2009, 12:50 PM

        Just to update on the issue ( in case it might be interesting to others experiencing the same) I must say that the issue is still present in 1.2.3 from 0616.
        Yesterday again there was a storm in logs with the stuck beacon message but its hard to tell whether or not AP was down at the moment when it happened.
        Luckily it recovered and is working ok for now.
        After some googling it looks like the problem is in the driver and most likely won't be solved anytime soon :(
        See for example :
        http://www.daemonforums.org/showthread.php?p=24538
        or
        http://markmail.org/message/mvqea7gke52cexpd
        or even
        http://kerneltrap.org/mailarchive/madwifi-devel/2008/9/9/3237624 (not sure whether its related though).
        There is some patch that is supposed to fix this but the patch is for Linux.

        I wonder how are things in 2.0 with FreeBSD 8?

        Current network "hardware" :
        Running 2.2RC in Virtualbox 4.2.16.

        Retired:
        ALIX2C2 , 4 gigabyte disk cf card running 2.0 (official release).

        1 Reply Last reply Reply Quote 0
        • First post
          Last post
        Copyright 2025 Rubicon Communications LLC (Netgate). All rights reserved.
          [[user:consent.lead]]
          [[user:consent.not_received]]