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

    Wireless on SG-2440

    Scheduled Pinned Locked Moved Wireless
    33 Posts 6 Posters 7.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.
    • D
      doktornotor Banned
      last edited by

      For N, you need either WPA2 or no authentication whatsoever. WEP/WPA not supported.

      1 Reply Last reply Reply Quote 0
      • ?
        Guest
        last edited by

        Well I may not have been much help but i had to ask some of those basic questions..
        Good luck, i am sure the support crew will get you going in no time.

        1 Reply Last reply Reply Quote 0
        • stephenw10S
          stephenw10 Netgate Administrator
          last edited by

          Yeah, even if you choose wpa or both if you check the encryption used it's wpa2.

          Steve

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

            At a minimum, it would appear that pfSense isn't invoking ifconfig correctly:

            Even with a standard of 11na and channel 36 specified in the config, ifconfig ath0_wlan0 reports

            media: IEEE 802.11 Wireless Ethernet autoselect mode 11b <hostap>An explicit call to ifconfig specifying channel 36 will result in

            media: IEEE 802.11 Wireless Ethernet autoselect mode 11na <hostap></hostap></hostap>

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

              My current config if it helps:

              <opt2><if>ath0</if>
                                      <wireless><standard>11na</standard>
                                              <mode>hostap</mode>
                                              <protmode>off</protmode>
                                              <ssid>Test</ssid>
                                              <channel>36</channel>
                                              <authmode><txpower><distance><regdomain>fcc</regdomain>
                                              <regcountry>US</regcountry>
                                              <reglocation>indoor</reglocation>
                                              <auth_server_addr><auth_server_port><auth_server_shared_secret><auth_server_addr2><auth_server_port2><auth_server_shared_secret2><wme><enable></enable></wme>
                                              <txantenna>0</txantenna>
                                              <rxantenna>0</rxantenna>
                                              <wpa><macaddr_acl><auth_algs>1</auth_algs>
                                                      <wpa_mode>2</wpa_mode>
                                                      <wpa_key_mgmt>WPA-PSK</wpa_key_mgmt>
                                                      <wpa_pairwise>CCMP</wpa_pairwise>
                                                      <wpa_group_rekey>60</wpa_group_rekey>
                                                      <wpa_gmk_rekey>3600</wpa_gmk_rekey>
                                                      <passphrase><ext_wpa_sw></ext_wpa_sw></passphrase></macaddr_acl></wpa>
                                              <puren><enable></enable></puren></auth_server_shared_secret2></auth_server_port2></auth_server_addr2></auth_server_shared_secret></auth_server_port></auth_server_addr></distance></txpower></authmode></wireless>
                                      <enable><spoofmac><ipaddr>192.168.228.1</ipaddr>
                                      <subnet>24</subnet></spoofmac></enable></opt2>

              1 Reply Last reply Reply Quote 0
              • ?
                Guest
                last edited by

                The SG-2440 is rarely pretty new on the market and not so many peoples get their hands on
                but often if more then 2 or 3 miniPCIe slot where soldered on the board on is only for setting
                up an mSATA in it, because this ports is assigned to an SATA interface, could this be perhaps?

                So if so you might be only changing the miniPCIe WiFi card to another miniPCIe slot and all
                is fine then.  ;)

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

                  @dennypage:

                  At a minimum, it would appear that pfSense isn't invoking ifconfig correctly:

                  It's set correctly, but there is a bug in the FreeBSD wireless bits with specifying mode. Related to: https://redmine.pfsense.org/issues/4517

                  In 2.2.2, there is an option "auto" for standard, which leaves it unspecified. That will work around the issue you're showing there. We have a FreeBSD bug report opened on that. Though I've never seen that affect hostap mode.

                  The only difference I see in your config and what I've been testing with is setting the regdomain, country and location, where I left mine to defaults. I'll try that exact config you have there.

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

                    With this config I get a continual reboot/crash/reboot/crash cycle.

                    <opt2><if>ath0</if>
                                            <wireless><standard>11na</standard>
                                                    <mode>hostap</mode>
                                                    <protmode>off</protmode>
                                                    <ssid>Test</ssid>
                                                    <channel>36</channel>
                                                    <authmode><txpower><distance><regdomain><regcountry><reglocation><auth_server_addr><auth_server_port><auth_server_shared_secret><auth_server_addr2><auth_server_port2><auth_server_shared_secret2><wme><enable></enable></wme>
                                                    <wpa><macaddr_acl><auth_algs>1</auth_algs>
                                                            <wpa_mode>2</wpa_mode>
                                                            <wpa_key_mgmt>WPA-PSK</wpa_key_mgmt>
                                                            <wpa_pairwise>CCMP</wpa_pairwise>
                                                            <wpa_group_rekey>60</wpa_group_rekey>
                                                            <wpa_gmk_rekey>3600</wpa_gmk_rekey>
                                                            <passphrase><ext_wpa_sw></ext_wpa_sw></passphrase></macaddr_acl></wpa>
                                                    <puren><enable></enable></puren></auth_server_shared_secret2></auth_server_port2></auth_server_addr2></auth_server_shared_secret></auth_server_port></auth_server_addr></reglocation></regcountry></regdomain></distance></txpower></authmode></wireless>
                                            <enable><spoofmac><ipaddr>192.168.228.1</ipaddr>
                                            <subnet>24</subnet></spoofmac></enable></opt2>

                    If I change the two lines:

                    <regdomain>fcc</regdomain>
                    <regcountry>US</regcountry>

                    Then the unit will successfully boot.

                    I still have the crash report if you would like.

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

                      I worked with Denny via support to check this out on his system. Of the few configs that crash his system, and the other few that don't crash but don't work at all either, all of them work just fine for me here on the same hardware with no crashes. So seems this is a hardware issue of some sort with his system and we're facilitating a return. I'll take a look at the box when we get it back to further investigate the specific root cause. I'm guessing it's a bad wifi card but we'll see.

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

                        Once again, thanks for taking the time Chris.

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

                          Just to close this off, the problem was indeed a hardware problem. The pfSense folk sent out a replacement unit (overnight) and it works great.

                          I would like to extend my thanks to the folk at pfSense for taking good care of me.

                          1 Reply Last reply Reply Quote 0
                          • luckman212L
                            luckman212 LAYER 8
                            last edited by

                            Interesting thread.  Was this a flaw with just your specific unit or a general errata with an earlier PCB revision that has since been corrected?

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

                              My personal thought is that the hardware problem was actually the WLE200NX (mini-PCIe WiFi card). I believe Chris was going to have a look at the defective unit, perhaps he will comment.

                              @luckman212:

                              Was this a flaw with just your specific unit or a general errata with an earlier PCB revision that has since been corrected?

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

                                It ended up being a problem with the wireless card.

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