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

    Wireless works fine… until I turn on security!?

    Scheduled Pinned Locked Moved Wireless
    20 Posts 3 Posters 7.9k 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.
    • W
      wallabybob
      last edited by

      @cmb:

      The DMCA-82 is what I use in my production AP actually, with WPA2, with 0 issues so that shouldn't be affected.

      There might be different chipset revisions or even different chipsets involved. It seems fairly common practice among the bigger WiFi device suppliers to change chipsets (even chipset manufacturers) without changing a device model name and number.

      @LuckyURE:

      Any ideas on how I can test specifically to see if this card is in fact subject to the aforementioned bug?

      I don't know the details of the referenced bug but it would probably be useful if you provided the output of the pfSense shell command pciconf -l -v to facilitate comparison of chipset in your device with others known to work.

      1 Reply Last reply Reply Quote 0
      • L
        LuckyURE
        last edited by

        dmesg says the following:

        ath0: <atheros 5413="">mem 0xe00c0000-0xe00cffff irq 9 at device 12.0 on pci0
        ath0: [ITHREAD]
        ath0: AR5413 mac 10.5 RF5413 phy 6.1</atheros>

        1 Reply Last reply Reply Quote 0
        • W
          wallabybob
          last edited by

          The dmesg snippet is useful, the pciconf output will be even more useful because it will include a revision number. Your chipset might have a different revision number than a working chipset.

          1 Reply Last reply Reply Quote 0
          • L
            LuckyURE
            last edited by

            $ pciconf -l
            hostb0@pci0:0:1:0: class=0x060000 card=0x20801022 chip=0x20801022 rev=0x33 hdr=0x00
            none0@pci0:0:1:2: class=0x101000 card=0x20821022 chip=0x20821022 rev=0x00 hdr=0x00
            vr0@pci0:0:9:0: class=0x020000 card=0x01061106 chip=0x30531106 rev=0x96 hdr=0x00
            vr1@pci0:0:10:0: class=0x020000 card=0x01061106 chip=0x30531106 rev=0x96 hdr=0x00
            vr2@pci0:0:11:0: class=0x020000 card=0x01061106 chip=0x30531106 rev=0x96 hdr=0x00
            ath0@pci0:0:12:0: class=0x020000 card=0x1600185f chip=0x001b168c rev=0x01 hdr=0x00
            isab0@pci0:0:15:0: class=0x060100 card=0x20901022 chip=0x20901022 rev=0x03 hdr=0x00
            atapci0@pci0:0:15:2: class=0x010180 card=0x209a1022 chip=0x209a1022 rev=0x01 hdr=0x00
            ohci0@pci0:0:15:4: class=0x0c0310 card=0x20941022 chip=0x20941022 rev=0x02 hdr=0x00
            ehci0@pci0:0:15:5: class=0x0c0320 card=0x20951022 chip=0x20951022 rev=0x02 hdr=0x00

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

              That's exactly the same card I have. Again, what hardware is it in?

              1 Reply Last reply Reply Quote 0
              • W
                wallabybob
                last edited by

                @cmb:

                Again, what hardware is it in?

                Do you need more information than:
                @LuckyURE:

                I'm using a Netgate m1n1wall 2D3/2D13 Alix board (http://store.netgate.com/Netgate-m1n1wall-2D3-2D13-Blue-P217C61.aspx).

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

                  Thanks I missed that post. I'll try putting mine in an ALIX in a bit.

                  1 Reply Last reply Reply Quote 0
                  • L
                    LuckyURE
                    last edited by

                    Any luck?  I'm eager to know how screwed up I am.  pfSense has been so rock solid that I just have to assume that it's me that is the problem.  :P

                    I patiently await your update.  Thanks for helping out on this!

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

                      I'm at a loss. I went through all my Atheros cards including the DCMA-82, on an ALIX, and had no issues with any of them. Jim @ Netgate gave me the idea that maybe it was related to the glxsb crypto accelerator on the ALIX so I made sure to try with that both on and off, and no diff either way, both ways work for me.

                      The only thing I can think of is somehow the hardware has changed in newer stock, the wireless gear I have is all 3-6 years old, though it should be identical since it's the same model and identifies itself the same. Netgate is going to test on new stock to compare.

                      1 Reply Last reply Reply Quote 0
                      • L
                        LuckyURE
                        last edited by

                        Is there anything else I can do to help troubleshoot this?  Should I pull the card out and provide any info off of it for you?  I'd really like to help get this working, not for just myself, but for everybody.  Anything I can do to help just let me know.

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

                          Not yet, but I'll definitely be in touch if Netgate can't replicate it either.

                          1 Reply Last reply Reply Quote 0
                          • L
                            LuckyURE
                            last edited by

                            I have good news.  No, scratch that, I have GREAT news!  ;D

                            I upgraded to the newly released 2.0.1 this morning and guess what.. the wireless works properly now!  There was no mention in the blog post regarding the new release of wireless fixes of this type but whatever the team did fixed my problem!

                            All clients can now connect to wpa/wpa2 secured networks (I have the WPA mode and WPA Pairwise each set to BOTH) and it's working great now.  Thanks pfSense & FreeBSD teams!

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

                              Hmm… well, that's great news, but I have no idea how that could have changed. Weird, the OS didn't change at all, nothing related to wireless changed either. Glad to hear it though!

                              1 Reply Last reply Reply Quote 0
                              • L
                                LuckyURE
                                last edited by

                                Just to clarify, I also have changed nothing other than updating to the new version as I was awaiting a response.  ::)  Thanks for your help through all of this!  Now back to my other forum post about bridging it now (fingers crossed): http://forum.pfsense.org/index.php/topic,43799.0.html

                                1 Reply Last reply Reply Quote 0
                                • L
                                  LuckyURE
                                  last edited by

                                  I have completed my bridging pfSense blog post.  It has a decent section that talks about configuring wireless in general.  If anyone is interested they can see it here:  http://blog.qcsitter.com/BSDay/index.php?/archives/2-Bridging-the-pfSense-2.x-wireless-divide.html

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