Belkin USB Wireless Adapter F5D6050



  • Following up on this post: http://forum.pfsense.org/index.php?topic=678.0

    I was curious whether anyone has gotten this model to work as an access point? I see that it says it doesn't work with freeBSD 6.1 so I assume it doesn't work with the latest pfSense which is freeBSD 7.2 based??

    If anyone has any suggestions of wireless usb adapters that work with the present pfSense release as an access point and are still available either in stores or online that would be great? Most of the devices listed in this list: http://www.freebsd.org/releases/7.2R/hardware.html#WLAN appear to be discontinued or unavailable.

    Thanks!



  • I have had good results with the Tenda W311U which is supported in pfSense 2.0 and later.
    I have also had good results with the TP-Link TL-WN321G. My devices were supported in pfSense 1.2.3 and later but it appears newer revisions might need pfSense 2.0 due to a change in chipset.

    I have used both devices as access points only.



  • Okay, so I bought a couple of TP-Link TL-WN321G adapters hoping they would work. They are version 4.1 and they don't seem to be registering. I found this link http://forum.pfsense.org/index.php?action=printpage;topic=21471.0 and followed the process of copying the if_rum driver over and adding it to loader.conf. When I did this I got the error listed in this link http://freebsd-forums.liquidneon.com/showthread.php?t=15682. So I still currently have an un-recognized, by ifconfig (rum), device.

    Can you help??



  • After doing a little more research I found this link http://www.wikidevi.com/wiki/TP-LINK_TL-WN321G_v4 which obviously shows that the v4 and v4.1 are RT2070, not RT2571W.

    Does anyone know how to install the RT2070 driver in pfSense?



  • @broncoBrad:

    followed the process of copying the if_rum driver over and adding it to loader.conf.

    What version of pfSense are you using? rum driver is built in pfSense 1.2.3 and pfSense 2.0 snapshot builds.

    A quick scan of the run driver sources suggests your device should be recognised by the run driver in pfSense 2.0 snapshot builds.



  • I am running the 1.2.3 release. If it's supported in 2.0 does that mean that it's supported in a later version of freeBSD? I downloaded freeBSD 7.2 when I attempted the driver copy. So do I need to download a new freeBSD or is the only way to upgrade to 2.0? 2.0 is still in release candidate builds yes? I was hoping to wait until it became a production release before upgrading.



  • Just select new update path for your current setup, and install new one.

    Or are you running on compact flash?



  • Two things… number one I figured out that pfSense 2.0 is using the freeBSD 8.1 base, but from what I read on the freeBSD 8.1 hardware compatibility list it doesn't list the RT2070 chipset... am I missing something?

    If it is supported in 8.1, do I just need to download 8.1 and copy the if_rum.ko driver again?? If so, I'm worried I'm going to get the same error:

    module uhub/rum already exists
    module uhub/rum failed to register: 17

    Do I need to rebuild the kernel? How long is it going to be before a stable 2.0 is ready?

    Also Metu what do you mean by "just select new update path"? I guess this is more generalized question in how would I upgrade and do I need to save out my configuration before I upgrade?



  • Wallabybob, is this what you found? http://www.leidinger.net/FreeBSD/dox/dev_usb/html/d9/de8/if__run_8c_source.html I can't tell what version of FreeBSD this is based on except for possibly the "8" in the link, which might mean version 8.x, which would mean it's supported.

    I didn't really want to do a release candidate, but I think I'll try it later tonight to see if 2.0 solves my problem.

    Please see my questions in previous "replies" as I still need answers there. Thanks!



  • @broncoBrad:

    Wallabybob, is this what you found? http://www.leidinger.net/FreeBSD/dox/dev_usb/html/d9/de8/if__run_8c_source.html I can't tell what version of FreeBSD this is based on except for possibly the "8" in the link, which might mean version 8.x, which would mean it's supported.

    No. One of your earlier posted links contained the USB Vendor code and USB product code. These code are used to identify USB devices. The specific code values occur in the run driver in FreeBSD 8.1 suggesting that driver recognises your device as one it supports. pfSense 2.0 is built from FreeBSD 8.1 sources so pfSense 2.0 should also recognise it.

    @broncoBrad:

    Two things… number one I figured out that pfSense 2.0 is using the freeBSD 8.1 base, but from what I read on the freeBSD 8.1 hardware compatibility list it doesn't list the RT2070 chipset... am I missing something?

    The FreeBSD hardware compatibility list is not an exhaustive list of supported devices.

    @broncoBrad:

    If it is supported in 8.1, do I just need to download 8.1 and copy the if_rum.ko driver again??
    Do I need to rebuild the kernel? How long is it going to be before a stable 2.0 is ready?

    1. No the run driver is built into the FreeBSD kernel which is  included in the files installed when pfSense is installed.
    2. No, see 1.
    3. As long as it takes. I have been using pfSense 2.0 as my "production" firewall for months (probably at least a year) and it does what I want of it.



  • Well the link that I believe you're referring to that listed the vendor code and USB product code is this one: http://freebsd-forums.liquidneon.com/showthread.php?t=15682. Correct?

    If that's the case, that's not the device I'm using.  How do I go about finding my vendor and product codes in pfSense?

    And when I do where do I go to figure out whether it's compatible??

    This seems like way too much analysis, please still answer these questions (esp. the first one for my future reference), but I think I'm going to upgrade to 2.0 RC3 anyway and I'll let you know whether it worked.



  • @broncoBrad:

    Well the link that I believe you're referring to that listed the vendor code and USB product code is this one: http://freebsd-forums.liquidneon.com/showthread.php?t=15682. Correct?

    No, http://www.wikidevi.com/wiki/TP-LINK_TL-WN321G_v4

    @broncoBrad:

    How do I go about finding my vendor and product codes in pfSense?

    Plug in your USB device and type the following command to the pfSense shell :

    usbconfig dump_device_desc

    and then trawl through the output looking for appropriate idVendor and idProduct codes.

    @broncoBrad:

    And when I do where do I go to figure out whether it's compatible??

    Use the source Luke!  (FreeBSD kernel source)

    I saw from another topic in another pfSense forum that you have already seen that someone else had their WN321G V4 recognised by run driver in pfSense 2.0.



  • So I upgraded to 2.0RC3 tonight and after the initial upgrade I unplugged and plugged the usb adapter and it was found and showed up in ifconfig, but after a reboot it no longer appears and I'm seeing this error (from dmesg | grep run):

    run0: <1.0> on usbus3
    run0: MAC/BBP RT3070 (rev 0x0201), RF RT2020 (MIMO 1T1R), address 54:e6:fc:90:59:93
    runfw: root not mounted yet, no way to load image
    run0: failed loadfirmware of file runfw
    run0: could not load 8051 microcode
    device_attach: run0 attach returned 6

    Please help! Thanks!



  • @broncoBrad:

    runfw: root not mounted yet, no way to load image

    You need to have the line:

    runfw_load="YES"

    in pfSense file /boot/loader.conf.local so the boot loader loads the firmware when the kernel is loaded and hence it becomes accessible to the kernel before the root filesystem is loaded.



  • Okay.

    I've seen posts similar to that so it makes sense. Question though, why loader.conf**.local**?? And not just loader.conf??



  • @broncoBrad:

    Question though, why loader.conf**.local**?? And not just loader.conf??

    loader.conf.local is preserved over a pfSense firmware upgrade; loader.conf might not be preserved over a firmware upgrade.



  • local version exists between updates/upgrades
    normal conf gets written again by script and what it contains may not survive updates



  • Just so everyone is aware the TP-LINK TL-WN321G works great with pfSense 2.0 RC3!

    Thanks so much for everyone's help!


Log in to reply