Wireless AP not visible to connect



  • I'm trying to get an access point up.  I've been through everything several times and can't figure out what the issue is.

    Everything seems fine but no device can see the wireless network let alone connect.

    2.1.4-RELEASE (i386)
    built on Fri Jun 20 12:59:29 EDT 2014
    FreeBSD 8.3-RELEASE-p16

    Ralink 3070

    I followed this to get it to load the driver:
    https://forum.pfsense.org/index.php?topic=31000.msg160393#msg160393

    dmesg output:

    <snip>ugen7.3: <ralink>at usbus7
    run0: <1.0> on usbus7
    run0: MAC/BBP RT3070 (rev 0x0201), RF RT3020 (MIMO 1T1R), address 74:f0:6d:61:d3:55
    run0: firmware RT2870 loaded</ralink></snip>

    The dashboard shows the interface up and in hostap mode. It's on another subnet from the LAN.  DHCP is on.  SSID is broadcast.

    The wireless system log shows once in a while:
    hostapd: run0_wlan0: IEEE 802.11 Fetching hardware channel/rate support not supported.

    Help?



  • I was having the same issue when I installed 2.1.5. I was fiddling with interface settings and couldn't get it right - looked like it was up but nothing could connect. I finally re-loaded my backup config (from 2.1.4) and the wireless started working. However I am now getting these messages in the log:

    
    $ dmesg|grep run0
    run0: <.0> on usbus4
    run0: MAC/BBP RT3070 (rev 0x0201), RF RT3020 (MIMO 1T1R), address <edited out="">run0: firmware RT2870 loaded
    wlan0: changing name to 'run0_wlan0'
    run0_wlan0: ieee80211_new_state_locked: pending RUN -> SCAN transition lost
    run0_wlan0: ieee80211_new_state_locked: pending RUN -> SCAN transition lost
    run0_wlan0: ieee80211_new_state_locked: pending RUN -> SCAN transition lost
    run0_wlan0: ieee80211_new_state_locked: pending RUN -> SCAN transition lost
    run0: device timeout
    run0: device timeout
    run0_wlan0: ieee80211_new_state_locked: pending RUN -> SCAN transition lost
    run0_wlan0: ieee80211_new_state_locked: pending RUN -> SCAN transition lost
    run0: device timeout
    run0: device timeout
    run0: device timeout
    run0: device timeout
    run0: device timeout</edited> 
    

    Now it's all timeout messages, two or three a minute. Again, the wireless seems to work from the user's point of view.

    2.1.4 did work with wireless and did not crank out these messages.



  • Well, I spoke too soon. It stopped working again. It's still cranking out timeout messages. So I went back to 2.1.4.

    Here is the same dmesg for 2.1.4:

    
    $ dmesg|grep run0
    run0: <.0> on usbus4$ dmesg|grep run0
    run0: <.0> on usbus4
    run0: MAC/BBP RT3070 (rev 0x0201), RF RT3020 (MIMO 1T1R), address <edited out="">run0: firmware RT2870 loaded
    wlan0: changing name to 'run0_wlan0'</edited> 
    

    Strange, looks like the driver is the same. I wonder why it would act differently.



  • You're not trying to use n-mode (i.e., "ng" or "na" or some such) by any chance, are you? That is pretty much guaranteed to not work on pfSense 2.1.



  • I wasn't. My device (run0) does not offer it in any case.



  • Hello everyone,

    I'm having the same problem with a Tenda W322P PCI card (ralink 3060 chip) on 2.2-Release. Setting up everything in pfSense, status shows it as running but none of the clients can see the wireless connection and obviously cannot connect. Tried in AP or adhoc or business mode, bridged or in different subnet, nothing seems to work so far. Any idea?

    Thanks,
    Daniel