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

    PfSense 2.0-BETA4 WPA/WPA2 Not Working

    Scheduled Pinned Locked Moved 2.0-RC Snapshot Feedback and Problems - RETIRED
    16 Posts 2 Posters 7.1k 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.
    • J
      John5788
      last edited by 

      $ ps -A | grep hostapd
  164  ??  S      0:00.01 sh -c ps -A | grep hostapd
  329  ??  S      0:00.01 grep hostapd
 8100  ??  Ss     0:00.07 /usr/sbin/hostapd -B /var/etc/hostapd_ath0_wlan0.conf

      all of my devices cannot authenticate with the wireless AP when I enable WPA. without WPA, the devices can connect just fine.

      I am using a very simple password: testtest

      1 Reply Last reply Reply Quote 0
      • E
        Efonnes
        last edited by

        Hmm, I'll need to update one of my systems and try it.

        1 Reply Last reply Reply Quote 0
        • J
          John5788
          last edited by

          is there a logging feature? maybe I can watch what happens when one of my devices try to connect to the AP?

          1 Reply Last reply Reply Quote 0
          • E
            Efonnes
            last edited by

            You could see if there is anything in the system log that gives a hint.

            1 Reply Last reply Reply Quote 0
            • J
              John5788
              last edited by 

              Nov 15 21:27:52 	hostapd: ath0_wlan0: STA 00:25:d3:e6:f7:f1 IEEE 802.11: associated
Nov 15 21:27:55 	hostapd: ath0_wlan0: STA 00:25:d3:e6:f7:f1 IEEE 802.11: deauthenticated due to local deauth request
Nov 15 21:27:55 	hostapd: ath0_wlan0: STA 00:25:d3:e6:f7:f1 IEEE 802.11: deassociated
Nov 15 21:27:57 	hostapd: ath0_wlan0: STA 00:25:d3:e6:f7:f1 IEEE 802.11: associated
Nov 15 21:28:01 	hostapd: ath0_wlan0: STA 00:25:d3:e6:f7:f1 IEEE 802.11: deauthenticated due to local deauth request
Nov 15 21:28:01 	hostapd: ath0_wlan0: STA 00:25:d3:e6:f7:f1 IEEE 802.11: deassociated
Nov 15 21:28:02 	hostapd: ath0_wlan0: STA 00:25:d3:e6:f7:f1 IEEE 802.11: associated
Nov 15 21:28:05 	hostapd: ath0_wlan0: STA 00:25:d3:e6:f7:f1 IEEE 802.11: deauthenticated due to local deauth request
Nov 15 21:28:05 	hostapd: ath0_wlan0: STA 00:25:d3:e6:f7:f1 IEEE 802.11: deassociated

              this is what I am seeing in System Log as my netbook is trying to connect with WPA enabled

              1 Reply Last reply Reply Quote 0
              • E
                Efonnes
                last edited by

                After updating it is still working fine for me, so I can't reproduce this, unfortunately.  It is also a card using the ath driver.

                1 Reply Last reply Reply Quote 0
                • J
                  John5788
                  last edited by

                  I updated to today's snapshot too.

                  lemme take a screenshot of my configuration for OPT1



                  any thoughts on my configuration?

                  1 Reply Last reply Reply Quote 0
                  • E
                    Efonnes
                    last edited by

                    MAC address spoofing is not currently supported on wireless access points when WPA is enabled. (hostapd bug)  It results in hostapd picking up the wrong MAC when it starts (because it is reading the wrong type, so both types have to match).

                    http://redmine.pfsense.org/issues/841

                    1 Reply Last reply Reply Quote 0
                    • J
                      John5788
                      last edited by

                      oh I'm not spoofing my MAC address, I clicked the insert link next to the textbox. It didn't make a difference leaving it there or not.

                      1 Reply Last reply Reply Quote 0
                      • E
                        Efonnes
                        last edited by

                        So you actually have it blank and have not saved the configuration with that filled in even once since the last time you booted up the system?  It is one of the fields that does not reset the internal setting to the default when you change back to the default setting until you have rebooted the system.

                        1 Reply Last reply Reply Quote 0
                        • J
                          John5788
                          last edited by

                          ah ha, thanks. it works now :)

                          I cleared the field, applied changes and rebooted. now devices are authenticating.

                          off topic slightly: 802.11ng mode doesnt seem to work, is this just a limitation of driver/software?

                          1 Reply Last reply Reply Quote 0
                          • E
                            Efonnes
                            last edited by

                            Yes, 802.11n doesn't work yet.  I don't know of any devices in particular that have a working driver with working 802.11n support.

                            By the way, I did notice earlier the existence of one of the 802.11n-specific fields in your screenshots; minimum wireless standard replaces the 802.11g-only setting when the driver lists 802.11n in the available modes.

                            The web gui is basically ready for 802.11n.  It is the drivers that are not.

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