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

    Help me!!! pfsense doesn't detect dlink wireless DWA-525 card

    Scheduled Pinned Locked Moved Wireless
    24 Posts 6 Posters 18.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.
    • W
      wallabybob
      last edited by

      You have probably hit the 'unable to mount root filesystem' problem seen when a drive is connected so it has a different device name and /etc/fstab is not updated for the change in device name. In your case, your original drive was probably something like /dev/ad0 and /etc/fstab would have said the root file system was at /dev/ad0s1a. When you move that drive (or a copy) to a usb interface its device name changes to something like /dev/da0 so /etc/fstab should be changed in sympathy.

      If you search the forums for 'unable to mount root file system' you'll probably see a few examples of how to deal with this.

      1 Reply Last reply Reply Quote 0
      • B
        bartgrefte
        last edited by

        Uhm, I only wrote the snapshot image to the CF card and had my moms computer boot from it right after that, so where does the change take place ???. It was in the USB cardreader the whole time and nothing happened to it (as far as I know).
        Offtopic: to get to the console with a null-modem cable, I used a 486, or was it a 386, laptop with Windows 3.11 8). Was the only computer around and not in use that had a RS232 port….

        Anyway, I dug up an old 2GB hard drive, checked it for bad sectors with "just" 3MBps :P , then I did a full install and managed to get things going. The 552 is recognized out of the box, only had to add it to the interfaces list and then I could set it up as an AP.

        Well, it showed up on both my phone and laptop, but they could not connect to it at first, they tried to get an IP-address through DHCP (which I enabled) but they just stopped trying and then my phone said the network was out of range.
        After that I gave both my phone and laptop static IP's, then they could connect, but kept getting kicked off after a few sec for some reason. Couldn't even open up the webinterface of pfSense in that time.
        They automaticly reconnected though.

        In the system log I found this:

        Feb 6 14:14:25 dhclient[55700]: DHCPDISCOVER on ath0_wlan0 to 255.255.255.255 port 67 interval 10 
Feb 6 14:14:23 hostapd: ath0_wlan0: STA 78:47:1d:27:a0:2e IEEE 802.11: deassociated 
Feb 6 14:14:20 hostapd: ath0_wlan0: STA 00:18:de:00:ee:d8 IEEE 802.11: deassociated 
Feb 6 14:14:20 hostapd: ath0_wlan0: STA 78:47:1d:27:a0:2e WPA: pairwise key handshake completed (RSN) 
Feb 6 14:14:20 hostapd: ath0_wlan0: STA 78:47:1d:27:a0:2e RADIUS: starting accounting session 4D4EA97C-00000059 
Feb 6 14:14:20 hostapd: ath0_wlan0: STA 78:47:1d:27:a0:2e IEEE 802.11: associated 
Feb 6 14:14:17 hostapd: ath0_wlan0: STA 78:47:1d:27:a0:2e IEEE 802.11: deassociated 
Feb 6 14:14:17 hostapd: ath0_wlan0: STA 78:47:1d:27:a0:2e WPA: pairwise key handshake completed (RSN) 
Feb 6 14:14:17 hostapd: ath0_wlan0: STA 78:47:1d:27:a0:2e RADIUS: starting accounting session 4D4EA97C-00000058 
Feb 6 14:14:17 hostapd: ath0_wlan0: STA 00:18:de:00:ee:d8 WPA: pairwise key handshake completed (RSN) 
Feb 6 14:14:17 hostapd: ath0_wlan0: STA 00:18:de:00:ee:d8 RADIUS: starting accounting session 4D4EA97C-00000057 
Feb 6 14:14:17 hostapd: ath0_wlan0: STA 00:18:de:00:ee:d8 IEEE 802.11: associated 
Feb 6 14:14:17 hostapd: ath0_wlan0: STA 78:47:1d:27:a0:2e IEEE 802.11: associated 
Feb 6 14:14:15 hostapd: ath0_wlan0: STA 78:47:1d:27:a0:2e IEEE 802.11: deassociated 
Feb 6 14:14:14 dhclient[55700]: DHCPDISCOVER on ath0_wlan0 to 255.255.255.255 port 67 interval 11 
Feb 6 14:14:12 hostapd: ath0_wlan0: STA 00:18:de:00:ee:d8 IEEE 802.11: deassociated 
Feb 6 14:14:12 hostapd: ath0_wlan0: STA 78:47:1d:27:a0:2e WPA: pairwise key handshake completed (RSN) 
Feb 6 14:14:12 hostapd: ath0_wlan0: STA 78:47:1d:27:a0:2e RADIUS: starting accounting session 4D4EA97C-00000056 
Feb 6 14:14:12 hostapd: ath0_wlan0: STA 78:47:1d:27:a0:2e IEEE 802.11: associated 
Feb 6 14:14:10 dhclient[55700]: DHCPDISCOVER on ath0_wlan0 to 255.255.255.255 port 67 interval 4 
Feb 6 14:14:09 hostapd: ath0_wlan0: STA 78:47:1d:27:a0:2e IEEE 802.11: deassociated 
Feb 6 14:14:09 hostapd: ath0_wlan0: STA 78:47:1d:27:a0:2e WPA: pairwise key handshake completed (RSN) 
Feb 6 14:14:09 hostapd: ath0_wlan0: STA 78:47:1d:27:a0:2e RADIUS: starting accounting session 4D4EA97C-00000055 
Feb 6 14:14:09 hostapd: ath0_wlan0: STA 78:47:1d:27:a0:2e IEEE 802.11: associated 
Feb 6 14:14:09 hostapd: ath0_wlan0: STA 00:18:de:00:ee:d8 WPA: pairwise key handshake completed (RSN) 
Feb 6 14:14:09 hostapd: ath0_wlan0: STA 00:18:de:00:ee:d8 RADIUS: starting accounting session 4D4EA97C-00000054 
Feb 6 14:14:09 hostapd: ath0_wlan0: STA 00:18:de:00:ee:d8 IEEE 802.11: associated 
Feb 6 14:14:07 hostapd: ath0_wlan0: STA 78:47:1d:27:a0:2e IEEE 802.11: deassociated 
Feb 6 14:14:07 dhclient[55700]: DHCPDISCOVER on ath0_wlan0 to 255.255.255.255 port 67 interval 3 
Feb 6 14:14:05 dhclient[55700]: DHCPDISCOVER on ath0_wlan0 to 255.255.255.255 port 67 interval 2

        And on the screen of the computer that was running pfSense:

        
ath0: stuck beacon; resetting (bmiss count 4)
ath0: bb hang detected (0x80)

        I just Googled this, read reports of this having to do with the channel selection being on auto?
        Gonna try to set it manually later on.

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

          @bartgrefte:

          Uhm, I only wrote the snapshot image to the CF card and had my moms computer boot from it right after that, so where does the change take place ???. It was in the USB cardreader the whole time and nothing happened to it (as far as I know).

          In Freebsd SATA and PATA drives are called /dev/ad0, /dev/ad1 etc while USB drives are called /dev/da0, /dev/da1 etc. if you installed to /dev/ad0 your root file system will be something like /dev/ad0s1a and /etc/fstab will say so. (FreeBSD startup reads /etc/fstab on the boot drive to see what file systems need to be mounted.)

          Thus your CF card will have a /etc/fstab that says the root file system is /dev/ad0s1a but this won't be on your cf drive (which will be called something like /dev/da0).

          1 Reply Last reply Reply Quote 0
          • B
            bartgrefte
            last edited by

            Hmm, 'kay :)

            Btw, I am not sure how but got rid of the errors and the connection is not dropped and I can access pfSense's webinterface through the 552 ;D
            I couldn't do any speedtests, well, I could have tried but I don't think a speedtest between my phone and laptop would show the maximum :P
            (Just thought of the iperf package, but the computer I was trying this on did not have access to the internet.)

            At least I know this card seems to be working with pfSense ;D , eventhough the lack of N support, but hoping this might change.
            Now waiting for some antennas with cables (so that they do not have to be put away behind the pc case under the desk).
            The ANT24-0230 unfortunatly is not available outside of North America (and no shops willing to ship it here ???) so now waiting for some alternative I found on Ebay. :)

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