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

    Wep - problem on Beta2

    Scheduled Pinned Locked Moved
    Wireless
    7
    34
    14.0k
    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.
    • A
      Always
      last edited by

      Already tried two different notebooks and three different nics (the one with sonoma based centrino latops, buffalo abg and asus wireless card) and got same result. Is anyone running a pcengines wrap with a compex wlm54g atheros based wireless minipci nic?Will continue to look into this problems, try updating wifi drivers but my guess is that there is something more if problem repeats on two different laptops and 3 different nics. I'll update if anything new.

      Thanks

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

        I'm working closely with ASUS to see whether its a problem of the wifi card on their laptop or it isn't. Nobody has a similar setup with WRAP and enabled WPA? IF so, could he/she tell me what client NIC are they using and with what drivers?

        Thanks

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

          I have a wrap with a CM9 using WPA.

          Clients in use:

          • notebook with atheros based PCMCIA (b,g,a, turbo a):
              when used with netgear driver for WGA511 works fine
              when used with Philips driver CPWNA100 works fine
              when used with atheros reference driver the client utility is deauthenticating like yours but with windows config tool it works fine

          • notebook with Intel 2915abg
              when using the intel referencedriver with intel tool works fine, with windows tool too

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

            That's just what I needed, I have the abg buffalo card and will try out those card-driver combos. Do you have direct links to those driver sets?

            Could you tell me the exact versions of the drivers? Do you upgrade firmware too?

            Thanks

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

              This subject begins from WEP problems - now you discuss about WPA.
              I use pfsense beta4 with artheos cards (planet wl-8310) and WPA works fine.
              I have problems with WEP - i need use pfsense as AP and connect to him APC witch don't support WPA - only support WEP.
              When I configure pfsense as AP with disabled encryption all works fine, but when I enable WEP i cant connect….
              How I must configure pfsense to work with WEP?

              Regards
              Artur

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

                similiar problem here with same card ( planet wl-8310 - atheros based )
                i have those cards in my pfsense box and on my clients side.
                when i switch wep on, only one client can connect, others cant, i dont know what could it be…

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

                  Has anyone working WEP on card based on artheos? This is pfsense or card-chip bug?
                  Please help - it is very important to me.
                  Artur

                  1 Reply Last reply Reply Quote 0
                  • D
                    Dr. Gno
                    last edited by

                    I am running BETA4.  I have a some that work and some that don't.

                    I have Netgear WAG311 Atheros a/b/g mini-pci pulled from the PCI board and popped into my laptop.  It works with WEP.

                    However, I also have another laptop with an Intel 2100 internal mini-PCI and I can't get it to work with WEP.  I tried both the Intel Proset driver, it wouldn't even show the signal strenght, and the windows drivers, it showed a stong signal but won't get a DHCP lease. 
                    I had no problem with either when connecting to a Netgear wgt624.

                    I tried using a DLINK G630 PCMCIA card in the laptop with the internal 2100 mini-PCI disabled, it works fine with WEP.

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

                      Seems everything lies down to available drivers and firmware versions on the cards. Main problem is they can't authenticate. Please check the system log and copy/paste what you get there while trying to connect to the pfsense box.

                      1 Reply Last reply Reply Quote 0
                      • D
                        Dr. Gno
                        last edited by

                        I hope you're not saying it is the drivers that are at fault.  All of these drivers work fine with every other access point I've used.

                        When I get a chance I will try to capture evidence of the problem in the log files.  For now I've had to move back to using an off-the shelf access point because I need something that works.

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

                          Run a cvs_sync if you are using a full install. we fixed some hostap problems several days ago.

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

                            Is it possible to run a cvs_sync running on the embedded image for wrap systems? If not, how can I get thos latest changes to run on my wrap to test if they solve the problems with hostapd.

                            Thanks

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

                              @Always:

                              Is it possible to run a cvs_sync running on the embedded image for wrap systems? If not, how can I get thos latest changes to run on my wrap to test if they solve the problems with hostapd.

                              No.  It's not possible.  You need to wait till rc1.

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

                                Isn't there any way to update the file or edit the code to put in the changes you made? Maybe through the edit function on the webgui.

                                If not, could you give me an idea about when the RC1 will be available?

                                EDIT:Already read that RC1 will be out "very soon".

                                Thanks

                                1 Reply Last reply Reply Quote 0
                                • 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
                                            • First post
                                              Last post