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

    DWL-AG530 "no carrier" problem

    Scheduled Pinned Locked Moved Wireless
    21 Posts 5 Posters 17.0k 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.
    • GruensFroeschliG Offline
      GruensFroeschli
      last edited by

      Could you show a screenshot of the config page of your WLAN?
      Are you certain that you enabled the interface?

      We do what we must, because we can.

      Asking questions the smart way: http://www.catb.org/esr/faqs/smart-questions.html

      1 Reply Last reply Reply Quote 0
      • A Offline
        AceBalboa
        last edited by

        Is this the page you're looking for?

        http://members.shaw.ca/acebalboa/Interfaces_Optional1.jpg

        RC

        1 Reply Last reply Reply Quote 0
        • GruensFroeschliG Offline
          GruensFroeschli
          last edited by

          yes. Thank you.

          The config looks good.
          It should just work like this.

          If that doesnt work, i'm out of ideas…

          It might be worth a try to unassign the interface (interfaces --> assign),
          restart,
          and reassign the interface.

          We do what we must, because we can.

          Asking questions the smart way: http://www.catb.org/esr/faqs/smart-questions.html

          1 Reply Last reply Reply Quote 0
          • A Offline
            AceBalboa
            last edited by

            Tried un-assigning and re-assigning.  Didn't work.

            It's strange because I can change every setting except the channel and status.  And I don't get any error messages.

            RC

            1 Reply Last reply Reply Quote 0
            • A Offline
              AceBalboa
              last edited by

              Hey

              I finally got my wireless card working as an access point.  I tried many things before stumbling over success.

              First, I tried booting up with the FreeSBIE-2.0.1 (Live CD) to see if it could get my wireless card working … it could not (although PCLinuxOS could).

              Next, I moved the card to a different computer ... it still didn't work.

              Then, I moved the wireless card back to the first computer.  I placed the card in the 3rd slot (instead of the 1st slot) this time, re-installed pfSense, and the wireless card worked.

              So it appears that moving the wireless card to a different slot seemed to work.  I'm sure a clean install didn't hurt!

              RC

              1 Reply Last reply Reply Quote 0
              • A Offline
                AceBalboa
                last edited by

                Okay,

                I think the clean install had more to do with my earlier success then the different PCI slot.  After installing a few packages (snort, squid, phpSysInfo, nmap & bandwidthd) and rebooting, my wireless card stopped working.  Same problem as before.

                RC

                1 Reply Last reply Reply Quote 0
                • A Offline
                  AceBalboa
                  last edited by

                  Un-installed the 5 packages (snort, squid, phpSysInfo, nmap & bandwidthd) then rebooted and my wireless card works again.

                  I'll (eventually) re-install them one at the time (and reboot between each) to figure out which package causes the problem.

                  RC

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

                    @AceBalboa:

                    Un-installed the 5 packages (snort, squid, phpSysInfo, nmap & bandwidthd) then rebooted and my wireless card works again.

                    I'll (eventually) re-install them one at the time (and reboot between each) to figure out which package causes the problem.

                    Let us know, that's odd. Maybe promiscuous mode messes with hostap, though I haven't heard of that being an issue. If that's the case, either snort or bandwidthd could be the culprit.

                    1 Reply Last reply Reply Quote 0
                    • A Offline
                      AceBalboa
                      last edited by

                      I've re-built my firewall a dozen times since my last post … seems like there's some kind of bug around renaming the Optional Interface Configuration Description (from 'OPT1' to anything else ... I tried 'WLAN'). Anyways ... I've re-installed from scratch, again, and didn't rename OPT1, and now I can't get my ATH WIFI card to work in any mode except for Ad-Hoc.  Before re-installing, I moved my ATH card up one slot and replace a pair of D-Link 10/100 NICs with a dual-head Compaq NIC.

                      RC

                      1 Reply Last reply Reply Quote 0
                      • A Offline
                        AceBalboa
                        last edited by

                        I noticed, on the monitor plugged into my pfSense firewall, that it says: "ath0: Unable to reset hardware; hal status 0" (several times … probably once for every time I tried to bring my wireless card up).  I've tried rebooting and it didn't go away.  So I did a little googling and found several 'ath' man pages (such as http://www.ipnom.com/FreeBSD-Man-Pages/ath.4.html) that say:

                        ath%d: unable to reset hardware; hal status %u  The Atheros Hardware Access Layer was unable to reset the hardware as requested.  The status code is explained in the HAL include file sys/contrib/dev/ath/ah.h.  This should not happen.

                        … this shouldn't happen?  Well, it is happening!  I'm not sure where the ah.h file is located in pfSense, so I googled it and found a copy of it on kernel.org (http://kernel.org/pub/linux/kernel/people/mcgrof/openhal-2006-08-03/ah.h) ... I know it's Linux, not BSD, but I'm assuming/hoping the error codes are the same.  Looks like "Hal status 0' means "No error".

                        So I'm getting an error that I shouldn't get that's telling me there's no error?  Anyone have any idea what's going on here?

                        Thx,
                        RC

                        1 Reply Last reply Reply Quote 0
                        • D Offline
                          deepdish
                          last edited by

                          @AceBalboa:

                          I noticed, on the monitor plugged into my pfSense firewall, that it says: "ath0: Unable to reset hardware; hal status 0" (several times … probably once for every time I tried to bring my wireless card up).  I've tried rebooting and it didn't go away.  So I did a little googling and found several 'ath' man pages (such as http://www.ipnom.com/FreeBSD-Man-Pages/ath.4.html) that say:

                          ath%d: unable to reset hardware; hal status %u  The Atheros Hardware Access Layer was unable to reset the hardware as requested.  The status code is explained in the HAL include file sys/contrib/dev/ath/ah.h.  This should not happen.

                          … this shouldn't happen?  Well, it is happening!  I'm not sure where the ah.h file is located in pfSense, so I googled it and found a copy of it on kernel.org (http://kernel.org/pub/linux/kernel/people/mcgrof/openhal-2006-08-03/ah.h) ... I know it's Linux, not BSD, but I'm assuming/hoping the error codes are the same.  Looks like "Hal status 0' means "No error".

                          So I'm getting an error that I shouldn't get that's telling me there's no error?  Anyone have any idea what's going on here?

                          Thx,
                          RC

                          Look into this web-site as it is describing the same problem I had a few months ago:
                          http://www.maroouch.com/index.php/D-Link_AG530_/_%27_ath0:unable_to_reset_hardware%3B_hal_status_0%27_error

                          Once thats done, upgrade your pfsense to v1.2 beta, the one that is using the FreeBSD 6.3 kernel. You can find the link here:
                          http://cvs.pfsense.org/~sullrich/testing_images/6/FreeBSD_RELENG_6_3/pfSense_RELENG_1_2/

                          Afterwards, your wireless should be working fine. Even though you will see a lot of in/out errors they can be safely ignored as it does not seem to be performance impacting.

                          1 Reply Last reply Reply Quote 0
                          • A Offline
                            AceBalboa
                            last edited by

                            Hey

                            Looks like you might be right.  I did a little searching on Google and found a web page (Gentoo Wiki) the suggests I run "sysctl dev.wifi0.regdomain".  This command returned "dev.wifi0.regdomain = 18" … which they say means unknown regdomain.  They say I can fix it by running "ath_info -w

                            <address>regdomain <regdomain></regdomain>", but ath_info doesn't appear to be included in pfSense.  I haven't had much time to work on this issue lately, but I'll post the results once I find time.

                            Thanks,
                            RC</address>

                            1 Reply Last reply Reply Quote 0
                            • J Offline
                              jmontes4
                              last edited by

                              I had this exact problem with this card, changing the country worked for me.

                              http://forum.pfsense.org/index.php/topic,1407.0.html

                              Good luck and let us know how it all works out.

                              1 Reply Last reply Reply Quote 0
                              • A Offline
                                AceBalboa
                                last edited by

                                Hey

                                I finally got around to following the directions mentioned here: http://www.maroouch.com/ar5215/ar5215.html

                                I set my RegDomain and now my card works perfectly.  I didn't need to install pfSense v1.2 beta as suggested in an earlier post.

                                Thanks everyone.
                                RC

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