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.
    • S
      Stiv32
      last edited by

      I have a problem with WEP on pfSense Beta2 - when i crete interface in AP-mode and enable WEP (64 or 128) clients cannot associate , disabling WEP - all works fine. On this same machine under Linux Slackware, with this same keys all was OK - so i think it is problem with pfSense - cann you proof this bug?

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

        I've having same problems with beta 3 and 4. I get a perfect dhcp lease when running without wpa and as soon as I set wpa on both wifi card on latop and wrap box and reboot both, I can associate with the wrap box accespoint interface but can't get no dhcp lease.

        Let's hope we can get an answer.

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

          Well, I further investigated this issue and reading the system log got me to notice this:

          May 12 11:06:10 hostapd: ath0: STA 00:15:f2💿19:19 IEEE 802.11: associated
          May 12 11:06:13 hostapd: ath0: STA 00:15:f2💿19:19 IEEE 802.11: deauthenticated due to local deauth request
          May 12 11:06:13 hostapd: ath0: STA 00:15:f2💿19:19 IEEE 802.11: deassociated

          And it repeats over and over again. Seems like laptop wifi card cannot really associate to the router when WPA-PSK is used. Anyone experiencing this issues? tried AES, TKIP and Both as authentication on both wrap and latop. Laptop con associate and navigate perfectly when associating to buffalo airstation AP configured with WPA-PSK with TKIP. What may be causing this association issue?

          Thanks

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

            I get this with my atheros based pcmcia when using the atheros tool. Using the windows tool with the same driver works without issues. Also using the same card with a netgear driver and the netgear tool works fine.

            In case your are still at beta2 please upgrade. We don't support older versions.

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

              The problem mentioned above appears when using beta4 and previously appeared using beta 3. The wifi card on the wrap is compex wlm54g and the one on the laptop is asus wireless b/g card. I'm currently using the asus tool and can connect with WPA TKIP enabled to a buffalo router and get dhcp lease but can't associate to the wrap box. I will try disabling the asus tool and post back.

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

                Just tried to associate and connect using the windows configuration tool (WZC) and had the same result as above, with the same message in the system logs. Please post if having the same problem. Without WPA I can associate flawlessly. Could it be a minipci wifi card driver related issue, maybe the driver doesn't support WPA onmy card, don't know.

                Thanks

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

                  Your CARD is an atheros chipset, so it should support WPA. Try what happens if you set "TKIP" at "WPA Pairwise" in the webgui for your wireless nic (at the bottom of the screen).

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

                    Tried both AES and TKIP with same result, the system log showing the message I posted above. What does "deauthenticated due to local deauth request" mean? The Wrap box is deauthenticating me or my laptop wifi is sending that request? It's strange because system log displays those messages repeating every 3 seconds over and over, while windows tells me that I am connected to the AP ang trying to get an ip adress. Should I try disabling DHCP and try if I manage to associate with a static IP?

                    I'm looking for latest laptop wifi drivers to try to focus where the problems are. Seems laptop nic isn't the problem because using another laptop with a buffalo a/b/g card gives same problems.

                    Hope we work this out.

                    Thanks

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

                      Like said earlier, for me it was a client problem. I tried with my second notebook and it worked. I updated the driver of the notebook that had issues and used the win-0-config utility and not the drivers utility and it worked. My client was also trying to get DHCP but I guess it was just not quick enough to show the permanent drops all the time.

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