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

    Ath_tx_default and stuck beacon errors. any STABLE wireless cards??

    Scheduled Pinned Locked Moved Wireless
    4 Posts 2 Posters 991 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.
    • S
      spartasolutions
      last edited by

      I've been trying to find a simple, stable configuration of pfsense 2.3 using a wireless card capable of ap mode with at least 3 SSID's.

      I've been trying every Atheros card under the sun (2 down and more on the way), but it's getting painfully obvious that there's little to no intention of getting any single card to work.

      To date, I've attempted to configure the wireless system using both an Atheros AR9462 and the AR9380. Both give a mediocre connection that continuously drops packets, disconnects clients, and gets locked up with the classic errors:

      ath0: stuck beacon; resetting (bmiss count 4)
      ath0: stuck beacon; resetting (bmiss count 4)
      ath_tx_default_comp: bf 0xfffffe0000bb1610: seqno 884: bf_next not NULL!
      ath_tx_default_comp: bf 0xfffffe0000bb1610: seqno 885: bf_next not NULL!
      ath_tx_default_comp: bf 0xfffffe0000bb1610: seqno 886: bf_next not NULL!
      .
      .
      .

      2.4 Bug fixes aren't even halfway completed at this point (~44%). Yes, I've heard about how terrible the wireless system is and how anyone not using an ubiquiti AP is clearly insane. But is it really that crazy to think there must exist one card that works with the system?? I'd like to consolidate all the components of this UTM into one enclosure rather than hook up a white glorified wifi-discus to each individual unit.

      If you've got a working card, I'd love to hear of it and possibly work to get this thing running as soon as possible.

      1 Reply Last reply Reply Quote 0
      • jimpJ
        jimp Rebel Alliance Developer Netgate
        last edited by

        Give 2.4 a try if you care about wireless.

        Judging 2.4 by the % of tickets closed isn't really fair. A good chunk of those tickets are things that were pushed from older releases and will likely be pushed forward again. The primary list to look at is the regressions and there are only 18 of those, most of which affect only certain specific use cases that many wouldn't hit: https://redmine.pfsense.org/projects/pfsense/issues?query_id=61

        I have not seen a single stuck beacon error on 2.4 with either a USB wireless (ralink) or Atheros mPCIe card

        Remember: Upvote with the ๐Ÿ‘ button for any user/post you find to be helpful, informative, or deserving of recognition!

        Need help fast? Netgate Global Support!

        Do not Chat/PM for help!

        1 Reply Last reply Reply Quote 0
        • S
          spartasolutions
          last edited by

          For now, I'm going to follow the herd and just get working on the AP's. Truth be told, I had almost bricked a unit I was working on after digging into the pfsense kernel and had tossed out any hope of a working solution.

          However, no errors with 2.4? What snapshot was it/which atheros mPCIe? Chances are I probably have an identical one lying around I could throw in.

          1 Reply Last reply Reply Quote 0
          • jimpJ
            jimp Rebel Alliance Developer Netgate
            last edited by

            No specific snapshot, whatever is latest.

            Remember: Upvote with the ๐Ÿ‘ button for any user/post you find to be helpful, informative, or deserving of recognition!

            Need help fast? Netgate Global Support!

            Do not Chat/PM for help!

            1 Reply Last reply Reply Quote 0
            • First post
              Last post
            Copyright 2025 Rubicon Communications LLC (Netgate). All rights reserved.