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

    Wep - problem on Beta2

    Scheduled Pinned Locked Moved Wireless
    34 Posts 7 Posters 15.5k 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
      Dr. Gno
      last edited by

      Updated to RC1 and brief ran the WAP to see if the card would work.  No luck, smae gross symptom.  Will try to capture on logs one night this week.

      1 Reply Last reply Reply Quote 0
      • A
        artur_filipowicz
        last edited by

        I tried run wep on RC1 and it still don't work….
        Regards
        Artur

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

          After upgrade to RC1 all wirelless stuff working worse. Now i have problem with WPA to (not only WEP) - clients cannot associate. So, in this moment i come back to version B4 despite to on this version dont working WEP  but WPA working fine. In wersion RC1 all cryptography stuff (wirrelles) not working.

          1 Reply Last reply Reply Quote 0
          • H
            hoba
            last edited by

            I just did some extensive testing with WPA and WEP on my WRAP with CM9 in turbo A mode, dedicated subnet, non bridged:

            • WPA always works fine in hostap and infrstructure mode
            • changing WPA settings works fine, no need to reboot
            • WEP only works the first few seconds after saving settings at the webgui and dies after some time though the client stays authenticated. This seems to be somehow driver related, we are still debugging. It sometimes stays up but that is not very likely from my debuging tests atm.
            • due to a logic bug at the webgui it always generates "authentication" "shared key authentication" no matter what is entered at the webgui. Set your clients to use shared key until this bug is fixed when using WEP
            • WEP seems to work fine when configured at bootup (this points even more into direction of driver issues)
            • going from broken WEP config back to WPA via webgui always works fine for me without reboot

            So what to do when trying to run WEP for the meantime:

            • clients have to be set to "shared key"
            • reboot the pfsense after enabling WEP

            In case you still have issues please let us know what hardware you are running this on (system, nics, wireless driver utilized, bridged config, seperate subnet, …anything that might be special about your config).

            1 Reply Last reply Reply Quote 0
            • H
              hoba
              last edited by

              All bugs except the probably driver related ones were just fixed by Scott. In case you have a full install run a "cvs_sync.sh RELENG_1" or manually update your files via webgui diagnostics>edit file if you are on embedded platforms:
              http://cvstrac.pfsense.com/chngview?cn=12715
              http://cvstrac.pfsense.com/chngview?cn=12713

              1 Reply Last reply Reply Quote 0
              • A
                Always
                last edited by

                WPA seems to work ok, previous problems with beta4 have disappeared, haven't tried wpa+captive portal yet but I'm going to try now.

                1 Reply Last reply Reply Quote 0
                • H
                  hoba
                  last edited by

                  We did some extensive tests with WPA and Captive Portal and fixed a bug there. Should work.

                  1 Reply Last reply Reply Quote 0
                  • A
                    Always
                    last edited by

                    Confirmed that wpa+captive portal works, I only have problems when setting a redirect page, in that case, I authenticate and when trying to redirect I am sent to the captiveportal page again and again.

                    BTW, I could not edit any files with the "Edit file" option through web. Is this because I run on a WRAP box?

                    Thanks

                    1 Reply Last reply Reply Quote 0
                    • H
                      hoba
                      last edited by

                      @Always:

                      Confirmed that wpa+captive portal works, I only have problems when setting a redirect page, in that case, I authenticate and when trying to redirect I am sent to the captiveportal page again and again.

                      BTW, I could not edit any files with the "Edit file" option through web. Is this because I run on a WRAP box?

                      Thanks

                      I have used edit file from the webgui a lot of times on a wrap for debugging or just replacing an old file with a newer version. Works without any issues. Not sure what might be the problem here.

                      1 Reply Last reply Reply Quote 0
                      • A
                        Always
                        last edited by

                        Maybe I wasn't using the correct route to the file I wished to modify. It kept saying that the file could not be found.

                        Thanks

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

                          Route?  You mean path?  Unix uses /path/to/file.

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