ZyDAS USB2.0 WLAN



  • Hi

    When I plug in my USB wifi device I get this msg

    "ugen0: <zydas 2="" 255="" usb2.0="" wlan,="" class="" rev="" 2.00="" 48.10,="" addr="">on uhub1"

    How do I use it after I have plugged it in ?

    TIA Daniel</zydas>



  • You assign it under "Interfaces" –> "Assign"
    And then configure it like all other interface.
    Dont forget to create firewall rules allowing traffic.



  • @GruensFroeschli:

    You assign it under "Interfaces" –> "Assign"
    And then configure it like all other interface.
    Dont forget to create firewall rules allowing traffic.

    I checked there, can't find it there.
    Just fine le0 and em0.

    WAN and LAN



  • @varazir:

    When I plug in my USB wifi device I get this msg

    "ugen0: <zydas 2="" 255="" usb2.0="" wlan,="" class="" rev="" 2.00="" 48.10,="" addr="">on uhub1"</zydas>

    The device name ugen means the device has been claimed by the generic USB device driver which allows a few "generic USB device" operations but not networking. See FreeBSD ugen man page for more information.

    In short, the kernel doesn't have a device driver for it and so you can't use it with standard pfSense installation.  It might be that the device driver is not built in the standard pfSense kernel. (I had this problem with udav, USB ethernet device, some time ago.)

    If you can identify a FreeBSD device driver that supports your WLAN NIC and can get that device driver from a suitable FreeBSD install it may be possible to get your USB NIC operational.



  • @wallabybob:

    The device name ugen means the device has been claimed by the generic USB device driver which allows a few "generic USB device" operations but not networking. See FreeBSD ugen man page for more information.

    In short, the kernel doesn't have a device driver for it and so you can't use it with standard pfSense installation.  It might be that the device driver is not built in the standard pfSense kernel. (I had this problem with udav, USB ethernet device, some time ago.)

    If you can identify a FreeBSD device driver that supports your WLAN NIC and can get that device driver from a suitable FreeBSD install it may be possible to get your USB NIC operational.

    This driver supports my usb device http://www.freebsd.org/cgi/man.cgi?query=zyd&sektion=4&manpath=FreeBSD+7.2-RELEASE



  • What version of pfSense are you using? (displayed on the home page).



  • @wallabybob:

    What version of pfSense are you using? (displayed on the home page).

    1.2.3-RELEASE , maybe need to add I'm running in a VMware server



  • I expect 1.2.3-RELEASE doesn't have zyd driver built in.

    If you have access to a FreeBSD 7.2 you could copy the driver if_zyd.ko to your pfSense system.


  • Rebel Alliance Developer Netgate

    FYI- The FreeBSD zyd(4) driver only supports station and monitor modes. Even if you manage to get it operational, it cannot be used in hostap mode as an access point. You could only use it for a wireless WAN connection.



  • @wallabybob:

    I expect 1.2.3-RELEASE doesn't have zyd driver built in.

    If you have access to a FreeBSD 7.2 you could copy the driver if_zyd.ko to your pfSense system.

    Okay thanks.

    @jimp:

    FYI- The FreeBSD zyd(4) driver only supports station and monitor modes. Even if you manage to get it operational, it cannot be used in hostap mode as an access point. You could only use it for a wireless WAN connection.

    Well then I have to look for another usb wireless adapter

    Thanks for all the help

    //Daniel



  • @varazir:

    Well then I have to look for another usb wireless adapter

    I've had positive experience with USB adapters based on the Ralink chipset (rum driver). I've used a D-Link DWL G122 and a TP-Link TL-WN321G. Unfortunately D-Link have the practice of changing the chipset in their devices without changing the model number, making it a bit hard to be sure that you are buying a device with a chipset supported by FreeBSD. The D-Link I bought on eBay was a hardware rev C and that seemed to work OK with the FreeBSD rum driver, though it didn't get a lot of use.

    When last I looked, I couldn't find any adapters based on the earlier Ralink chipset supported by the ural driver.



  • @wallabybob:

    @varazir:

    Well then I have to look for another usb wireless adapter

    I've had positive experience with USB adapters based on the Ralink chipset (rum driver). I've used a D-Link DWL G122 and a TP-Link TL-WN321G. Unfortunately D-Link have the practice of changing the chipset in their devices without changing the model number, making it a bit hard to be sure that you are buying a device with a chipset supported by FreeBSD. The D-Link I bought on eBay was a hardware rev C and that seemed to work OK with the FreeBSD rum driver, though it didn't get a lot of use.

    When last I looked, I couldn't find any adapters based on the earlier Ralink chipset supported by the ural driver.

    Hi, how could you make the rum driver work, I have a belkin one, I believe it is the ralink chipset as well and it is in the freebsd hardware list



  • @wallabybob:

    @varazir:

    Well then I have to look for another usb wireless adapter

    I've had positive experience with USB adapters based on the Ralink chipset (rum driver). I've used a D-Link DWL G122 and a TP-Link TL-WN321G. Unfortunately D-Link have the practice of changing the chipset in their devices without changing the model number, making it a bit hard to be sure that you are buying a device with a chipset supported by FreeBSD. The D-Link I bought on eBay was a hardware rev C and that seemed to work OK with the FreeBSD rum driver, though it didn't get a lot of use.

    When last I looked, I couldn't find any adapters based on the earlier Ralink chipset supported by the ural driver.

    Borrow a D-link rev C adepter from a friend and it worked great


Log in to reply