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

    Wireless Dies in 1.2-Beta-1

    Scheduled Pinned Locked Moved
    Wireless
    7
    12
    7.5k
    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.
    • R
      rneily
      last edited by

      @sullrich:

      Make sure your bios is the latest version.  This can happen with prior bios versions.

      I've been running 1.11 for some time…  anything else to check?

      1 Reply Last reply Reply Quote 0
      • C
        cmb
        last edited by

        Wireless in FreeBSD 6.2 seems to have some issues that cause the interface to drop. No known solution at this time. Do you see anything in the logs at the time of failure?

        1 Reply Last reply Reply Quote 0
        • R
          rneily
          last edited by

          @cmb:

          Wireless in FreeBSD 6.2 seems to have some issues that cause the interface to drop. No known solution at this time. Do you see anything in the logs at the time of failure?

          I was able to check out the logs tonight right after the wireless took it's dump.  Here is what I saw:

          Jun 30 20:28:41 last message repeated 3 times
          Jun 30 20:36:11 kernel: sis0: discard frame w/o packet header
          Jun 30 20:36:47 last message repeated 4 times
          Jun 30 20:36:54 kernel: sis0: discard frame w/o packet header
          Jun 30 20:36:56 kernel: ath0: stuck beacon; resetting (bmiss count 4)
          Jun 30 20:36:56 kernel: ath0: ath_reset: unable to reset hardware; hal status 3
          Jun 30 20:37:19 kernel: ath0: device timeout
          Jun 30 20:37:20 kernel: ath0: stuck beacon; resetting (bmiss count 4)
          Jun 30 20:37:20 kernel: ath0: ath_reset: unable to reset hardware; hal status 3
          Jun 30 20:37:37 kernel: ath0: device timeout

          I am having to reboot the WRAP box about twice a day because the wireless problem…

          1 Reply Last reply Reply Quote 0
          • R
            rneily
            last edited by

            I am assuming that since 1.2 is based on FreeBSD 6.2 that will will continue to have problems with wireless…

            1 Reply Last reply Reply Quote 0
            • C
              cmb
              last edited by

              Yup. Might be something in the works to avoid that, but you may be stuck with 1.0 for the time being. I'm hoping that's not the case. Stay tuned to the blog (pfsense.blogspot.com) for updates.

              1 Reply Last reply Reply Quote 0
              • R
                rneily
                last edited by

                I just loaded 1.2-BETA-2 to see if there is any difference….  I am importing my config from 1.01 to the Beta for 1.2.  Maybe I should start clean and not import my config and see if that helps...

                1 Reply Last reply Reply Quote 0
                • B
                  baskin
                  last edited by

                  @rneily:

                  I just loaded 1.2-BETA-2 to see if there is any difference….  I am importing my config from 1.01 to the Beta for 1.2.  Maybe I should start clean and not import my config and see if that helps...

                  Please report any findings. I have three pfsense boxes, all with wireless, working in a wireless community network and i want to upgrade them as soon as everything is ok with the wireless interfaces.

                  I'm planning to install two more so please be quick. ;)

                  1 Reply Last reply Reply Quote 0
                  • G
                    GoldServe
                    last edited by

                    Getting this problem in 1.2-RC1 as well.

                    Jul 27 08:48:10 kernel: ath0: ath_reset: unable to reset hardware; hal status 3
                    Jul 27 08:48:10 kernel: ath0: stuck beacon; resetting (bmiss count 4)
                    Jul 27 08:47:43 kernel: ath0: device timeout
                    Jul 27 08:47:38 hostapd: ath0: STA 00:13:02:4c:xx:xx IEEE 802.11: deassociated
                    Jul 27 08:47:38 hostapd: ath0: STA 00:13:02:4c:xx:xx IEEE 802.11: deauthenticated due to local deauth request
                    Jul 27 08:47:37 kernel: ath0: ath_reset: unable to reset hardware; hal status 3
                    Jul 27 08:47:37 kernel: ath0: stuck beacon; resetting (bmiss count 4)
                    Jul 27 08:47:37 kernel: ath0: device timeout
                    Jul 27 08:47:23 kernel: ath0: ath_reset: unable to reset hardware; hal status 3
                    Jul 27 08:47:23 kernel: ath0: stuck beacon; resetting (bmiss count 4)

                    1 Reply Last reply Reply Quote 0
                    • R
                      rockbochs
                      last edited by

                      Any word on this problem yet? We're finding the same issues dating from the current 1.2-RC1 as well as older snapshots from earlier this year. Is there a fix in sight?

                      Wireless in FreeBSD 6.2 seems to have some issues that cause the interface to drop. No known solution at this time. Do you see anything in the logs at the time of failure?

                      At this point, if _stable_wireless is a needed feature, should we look at going back to the 1.0-RELEASE of pfSense? I believe it's core is FreeBSD 6.0… which did not have the wireless issues present. Am I correct?

                      --Tim

                      Creator of world class Linux/FreeBSD appliances, including the popular StrongBochs pfSense appliance.

                      1 Reply Last reply Reply Quote 0
                      • B
                        bretti_kivi
                        last edited by

                        i'm not sure which thread is the right one, but….i have lots of wireless issues that smell like this.

                        I'm using the latest build from last week (i have to check the version); before i went away for the weekend i spend a very fraught evening trying to sort everything out. I have three laptops at home, 2 IBMs and 1 Dell, 1 IBM runs Vista, the others all run XP.
                        The Vista Box and the Dell box could both get onto the net through WLAN, with WPA2. The other XP IBM didn't get a DNS server, which meant that a server I could use didn't any more.

                        The Vista box also couldn't get onto the net when i got home last night, though the Dell then suffered the same problem as the IBM had before, i.e. connection but no DNS. Through the cable everything is fine.

                        I will check what the status is tonight, but this is really annoying. I don't want to have to go back to IpCop, but I need a functional firewall :(

                        Did I miss a really good howto on the rules I must set up? Is there something silly i must check? (the encryption should be fine)....

                        thanks

                        Bret

                        1 Reply Last reply Reply Quote 0
                        • First post
                          Last post