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

    Pfsense AP not working with OS X/slow speed

    Scheduled Pinned Locked Moved Wireless
    13 Posts 4 Posters 2.2k 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.
    • K
      Koval88
      last edited by

      Hello,
      I have installed mini PCI-E Network Adapter and turned it into the bridge mode.  For some reason I cannot get my mac to obtain IP Address from DHCP and the internet is not working when I statically configure network settings.

      All the other devices work with it, including iPhones, iPads, androids, windows computers but not OS X running Mavericks. I've tried switching channels around instead of Auto and still does not work. I've reset network settings on mac but still no luck. I have another AP router in the bridge mode and it's working fine with my mac, wondering what could of be causing the compatibility issue or what's the problem. it's connected but I get this "!" which has no IP address and no internet access.

      NIC: Ubiquiti SR71-E PC-Express Card 802.11a/b/g/n 400mW

      I uploaded the screenshot of my configuration.

      Also, I noticed that my wifi speeds are pretty slow. When I stand right next to my wifi, I get speeds around 25Mbms and my internet speed is 105Mbps. Shouldn't I be getting at least half the speed with this NIC? I'd like to know if there's a way to improve that. I have 8dBi TP-Link dual antennas, and I'm across two rooms, get 2-3 bars and the speeds drop significantly, getting 2.5Mbps down and 2.1Mbps up. Don't have much interference here, switched around with channels but still crappy speeds, unusable speeds.

      Thanks!

      1.png
      1.png_thumb
      2.png
      2.png_thumb
      3.png
      3.png_thumb
      4.png
      4.png_thumb

      1 Reply Last reply Reply Quote 0
      • DerelictD
        Derelict LAYER 8 Netgate
        last edited by

        Maybe your expectations are too high. 300Mbps is marketing BS.

        2 rooms is not insignificant for wi-fi signal degradation, especially if you're at an oblique angle to any walls between you and the AP.

        Did you set the channel width to 40MHz on 5GHz (a)?  Are you on 2.4GHz or 5GHz?

        I think all the FreeBSD 10.1-CURRENT wi-fi/atheros code is incorporated into the latest 2.2.2 snapshots.  Yup.  https://redmine.pfsense.org/issues/4582  That's probably about as good a thing as you can do.

        Chattanooga, Tennessee, USA
        A comprehensive network diagram is worth 10,000 words and 15 conference calls.
        DO NOT set a source address/port in a port forward or firewall rule unless you KNOW you need it!
        Do Not Chat For Help! NO_WAN_EGRESS(TM)

        1 Reply Last reply Reply Quote 0
        • K
          Koval88
          last edited by

          @Derelict:

          Maybe your expectations are too high. 300Mbps is marketing BS.

          2 rooms is not insignificant for wi-fi signal degradation, especially if you're at an oblique angle to any walls between you and the AP.

          Did you set the channel width to 40MHz on 5GHz (a)?  Are you on 2.4GHz or 5GHz?

          I think all the FreeBSD 10.1-CURRENT wi-fi/atheros code is incorporated into the latest 2.2.2 snapshots.  Yup.  https://redmine.pfsense.org/issues/4582  That's probably about as good a thing as you can do.

          Oh definitely that's BS. It's the NIC I've been recommended. I'm at 2.4GHz. I had an issue with the 2.2 version installing on my hard drives. Maybe if I actually upgrade to 2.2.2 without doing a fresh install that might work but I've had trouble making the installation work for that matter. The wifi should definitely work better than what I am getting.
          Is the 2.2.2 fixes the OS X compatibility?
          thanks!

          1 Reply Last reply Reply Quote 0
          • DerelictD
            Derelict LAYER 8 Netgate
            last edited by

            No idea what the OS X incompatibility is or if it's fixed.  All I know is that if I was trying to run atheros wifi on pfSense, I'd be running the latest code level as was practical.

            Chattanooga, Tennessee, USA
            A comprehensive network diagram is worth 10,000 words and 15 conference calls.
            DO NOT set a source address/port in a port forward or firewall rule unless you KNOW you need it!
            Do Not Chat For Help! NO_WAN_EGRESS(TM)

            1 Reply Last reply Reply Quote 0
            • K
              Koval88
              last edited by

              I see that it has 2.2.2 on the link you gave me, but in the downloads section there's only 2.2.1. Anywhere I can get a firmware upgrade to the 2.2.2?
              I can definitely try the update.
              Thanks!

              1 Reply Last reply Reply Quote 0
              • DerelictD
                Derelict LAYER 8 Netgate
                last edited by

                It's a snapshot.  Equivalent to a beta.  There are only a handful of changes though for 2.2.2.  snapshots.pfsense.org.  Or just try 2.2.1.

                Chattanooga, Tennessee, USA
                A comprehensive network diagram is worth 10,000 words and 15 conference calls.
                DO NOT set a source address/port in a port forward or firewall rule unless you KNOW you need it!
                Do Not Chat For Help! NO_WAN_EGRESS(TM)

                1 Reply Last reply Reply Quote 0
                • K
                  Koval88
                  last edited by

                  I just uploaded to 2.2.1. Still having issues with the OS X not getting internet access. The odd part is the Mac is getting IP address from DCHP after a minute or so, takes a while to kick in while on the other networks I do not have any issues or with other computers that connect to the WIFI AP. No wifi performance after the update, getting 2Mbps down and 3Mpbs up. Weird, not sure what is going on with that.

                  Edit: I was sitting right next to AP and was getting 6 down and 12 up. Still unsure what might be causing the issue.
                  Thanks!

                  1 Reply Last reply Reply Quote 0
                  • K
                    Koval88
                    last edited by

                    Upgraded to 2.2.2 Still experiencing the same issue with OS X and speeds. Any updates on that?

                    thanks!

                    1 Reply Last reply Reply Quote 0
                    • DerelictD
                      Derelict LAYER 8 Netgate
                      last edited by

                      If you insist on using a wi-fi card instead of getting an AP you get what you get.

                      Chattanooga, Tennessee, USA
                      A comprehensive network diagram is worth 10,000 words and 15 conference calls.
                      DO NOT set a source address/port in a port forward or firewall rule unless you KNOW you need it!
                      Do Not Chat For Help! NO_WAN_EGRESS(TM)

                      1 Reply Last reply Reply Quote 0
                      • D
                        doktornotor Banned
                        last edited by

                        Not to mention that Apple OSes wifi implementation has been a disaster for the past year or so.

                        1 Reply Last reply Reply Quote 0
                        • DerelictD
                          Derelict LAYER 8 Netgate
                          last edited by

                          Yeah, not so much from what I can tell.  There were a couple issues with 8.0-ish iOS but OS X has been reasonably solid.

                          Chattanooga, Tennessee, USA
                          A comprehensive network diagram is worth 10,000 words and 15 conference calls.
                          DO NOT set a source address/port in a port forward or firewall rule unless you KNOW you need it!
                          Do Not Chat For Help! NO_WAN_EGRESS(TM)

                          1 Reply Last reply Reply Quote 0
                          • K
                            Koval88
                            last edited by

                            @doktornotor:

                            Not to mention that Apple OSes wifi implementation has been a disaster for the past year or so.

                            That could be an issue, I never had problems with wifi, recently my Mac has been dropping connection. When I am connecting to my AP, often it would stay in a self assigned IP stage, then in few minutes it might obtain the IP from the DHCP. But once it got the IP, it still cannot access to the net or can't even communicate locally.

                            I was wondering if it may be some compatibility issue with the OS X and pfsense AP settings. Other than that, the wifi in OS X is pretty stable.

                            Thanks!

                            1 Reply Last reply Reply Quote 0
                            • dennypageD
                              dennypage
                              last edited by

                              For what it's worth, I have a fair number of OS X and iOS devices. I have a number of devices connected via Apple APs on the LAN segment, and I also have several devices connected to an guest network AP running on a WLE200NX (Atheros AR9280) inside the pfSense box itself. DHCP is being provided by pfSense. I have no problems with either.

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