USB RALINK



  • Guys,

    Just bought a new firewall and purchased a USB wireless Ralink RT5370. But its not appearing when the firewall boots. I can see it when it boots up and i believe it gets mounted. What am i doing wrong? Do i need to load additional drivers?

    Thank you! Any comments would be most greatful..



  • Please reboot with the dongle plugged in and then provide the output of the pfSense shell command```
    dmesg ; uname -a

    
    I suspect the chipset might be too new to be supported.


  • If i SSH into the box, and run the shell command. Whats the command to export the data you need? Or do shall i plug a serial cable in it and export the text? Sorry thank you for your help.



  • If you SSH from a windowing system into pfsense, login, select option 8 (Shell command), type (or copy and paste) the shell command and copy the output from the shell prompt and command through to the next shell command and then paste it into a reply.

    Alternatively, if you have access to the pfSense GUI, go to Diagnostics -> Command Prompt and type (or copy and paste) the shell command into the Command box, click on the Execute button, copy the ouput that will appear in a box above the Command box and paste it into a reply to this thread.

    Does that provide the details you are looking for?



  • Yea that does. But what is the command you need to type in? Sorry if its a dumb question.



  • Right ignore that! i worked it out. Here we go!

    Copyright © 1992-2010 The FreeBSD Project.
    Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994
    The Regents of the University of California. All rights reserved.
    FreeBSD is a registered trademark of The FreeBSD Foundation.
    FreeBSD 8.1-RELEASE-p6 #1: Mon Dec 12 18:23:46 EST 2011
        root@FreeBSD_8.0_pfSense_2.0-snaps.pfsense.org:/usr/obj./usr/pfSensesrc/src/sys/pfSense_SMP.8 i386
    Timecounter "i8254" frequency 1193182 Hz quality 0
    CPU: VIA C7 Processor 1000MHz (997.51-MHz 686-class CPU)
      Origin = "CentaurHauls"  Id = 0x6d0  Family = 6  Model = d  Stepping = 0
      Features=0xa7c9b9ff <fpu,vme,de,pse,tsc,msr,pae,mce,cx8,sep,mtrr,pge,cmov,pat,clflush,acpi,mmx,fxsr,sse,sse2,tm,pbe>Features2=0x4181 <sse3,est,tm2,xtpr>VIA Padlock Features=0xffcc <rng,aes,aes-ctr,sha1,sha256,rsa>real memory  = 536870912 (512 MB)
    avail memory = 484163584 (461 MB)
    netisr_init: forcing maxthreads to 1 and bindthreads to 0 for device polling
    wpi: You need to read the LICENSE file in /usr/share/doc/legal/intel_wpi/.
    wpi: If you agree with the license, set legal.intel_wpi.license_ack=1 in /boot/loader.conf.
    module_register_init: MOD_LOAD (wpi_fw, 0xc0988300, 0) error 1
    ipw_bss: You need to read the LICENSE file in /usr/share/doc/legal/intel_ipw/.
    ipw_bss: If you agree with the license, set legal.intel_ipw.license_ack=1 in /boot/loader.conf.
    module_register_init: MOD_LOAD (ipw_bss_fw, 0xc0789340, 0) error 1
    ipw_ibss: You need to read the LICENSE file in /usr/share/doc/legal/intel_ipw/.
    ipw_ibss: If you agree with the license, set legal.intel_ipw.license_ack=1 in /boot/loader.conf.
    module_register_init: MOD_LOAD (ipw_ibss_fw, 0xc07893e0, 0) error 1
    ipw_monitor: You need to read the LICENSE file in /usr/share/doc/legal/intel_ipw/.
    ipw_monitor: If you agree with the license, set legal.intel_ipw.license_ack=1 in /boot/loader.conf.
    module_register_init: MOD_LOAD (ipw_monitor_fw, 0xc0789480, 0) error 1
    wlan: mac acl policy registered
    kbd1 at kbdmux0
    cryptosoft0: <software crypto="">on motherboard
    padlock0: <aes-cbc,sha1,sha256>on motherboard
    acpi0: <cn700 awrdacpi="">on motherboard
    acpi0: [ITHREAD]
    acpi0: Power Button (fixed)
    acpi0: reservation of 0, a0000 (3) failed
    acpi0: reservation of 100000, 1ede0000 (3) failed
    Timecounter "ACPI-fast" frequency 3579545 Hz quality 1000
    acpi_timer0: <24-bit timer at 3.579545MHz> port 0x408-0x40b on acpi0
    cpu0: <acpi cpu="">on acpi0
    acpi_button0: <power button="">on acpi0
    pcib0: <acpi host-pci="" bridge="">port 0xcf8-0xcff on acpi0
    pci_link2: BIOS IRQ 5 for 0.16.INTC is invalid
    pci_link2: BIOS IRQ 5 for 0.17.INTC is invalid
    pci0: <acpi pci="" bus="">on pcib0
    agp0: <via 3314="" (p4m800ce)="" host="" to="" pci="" bridge="">on hostb0
    agp0: aperture size is 128M
    pcib1: <pci-pci bridge="">at device 1.0 on pci0
    pci1: <pci bus="">on pcib1
    vgapci0: <vga-compatible display="">mem 0xec000000-0xefffffff,0xf3000000-0xf3ffffff irq 11 at device 0.0 on pci1
    pcib2: <pci-pci bridge="">at device 8.0 on pci0
    pci2: <pci bus="">on pcib2
    pci2: <bridge>at device 0.0 (no driver attached)
    hme0: <sun 10="" 100="" hme="" ethernet="">mem 0xfcff8000-0xfcffffff irq 10 at device 0.1 on pci2
    miibus0: <mii bus="">on hme0
    ukphy0: <generic ieee="" 802.3u="" media="" interface="">PHY 1 on miibus0
    ukphy0:  10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto
    hme0: [ITHREAD]
    pci2: <bridge>at device 1.0 (no driver attached)
    hme1: <sun 10="" 100="" hme="" ethernet="">mem 0xfcff0000-0xfcff7fff irq 9 at device 1.1 on pci2
    miibus1: <mii bus="">on hme1
    ukphy1: <generic ieee="" 802.3u="" media="" interface="">PHY 1 on miibus1
    ukphy1:  10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto
    hme1: [ITHREAD]
    pci2: <bridge>at device 2.0 (no driver attached)
    hme2: <sun 10="" 100="" hme="" ethernet="">mem 0xfcfe8000-0xfcfeffff irq 10 at device 2.1 on pci2
    miibus2: <mii bus="">on hme2
    ukphy2: <generic ieee="" 802.3u="" media="" interface="">PHY 1 on miibus2
    ukphy2:  10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto
    hme2: [ITHREAD]
    pci2: <bridge>at device 3.0 (no driver attached)
    hme3: <sun 10="" 100="" hme="" ethernet="">mem 0xfcfe0000-0xfcfe7fff irq 11 at device 3.1 on pci2
    miibus3: <mii bus="">on hme3
    ukphy3: <generic ieee="" 802.3u="" media="" interface="">PHY 1 on miibus3
    ukphy3:  10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto
    hme3: [ITHREAD]
    atapci0: <via 8237="" udma133="" controller="">port 0x1f0-0x1f7,0x3f6,0x170-0x177,0x376,0xff00-0xff0f at device 15.0 on pci0
    ata0: <ata 0="" channel="">on atapci0
    ata0: [ITHREAD]
    ata1: <ata 1="" channel="">on atapci0
    ata1: [ITHREAD]
    uhci0: <via 83c572="" usb="" controller="">port 0xfe00-0xfe1f irq 11 at device 16.0 on pci0
    uhci0: [ITHREAD]
    usbus0: <via 83c572="" usb="" controller="">on uhci0
    uhci1: <via 83c572="" usb="" controller="">port 0xfd00-0xfd1f irq 11 at device 16.1 on pci0
    uhci1: [ITHREAD]
    usbus1: <via 83c572="" usb="" controller="">on uhci1
    uhci2: <via 83c572="" usb="" controller="">port 0xfc00-0xfc1f irq 10 at device 16.2 on pci0
    uhci2: [ITHREAD]
    usbus2: <via 83c572="" usb="" controller="">on uhci2
    uhci3: <via 83c572="" usb="" controller="">port 0xfb00-0xfb1f irq 10 at device 16.3 on pci0
    uhci3: [ITHREAD]
    usbus3: <via 83c572="" usb="" controller="">on uhci3
    ehci0: <via vt6202="" usb="" 2.0="" controller="">mem 0xfdfff000-0xfdfff0ff irq 9 at device 16.4 on pci0
    ehci0: [ITHREAD]
    usbus4: EHCI version 1.0
    usbus4: <via vt6202="" usb="" 2.0="" controller="">on ehci0
    isab0: <pci-isa bridge="">at device 17.0 on pci0
    isa0: <isa bus="">on isab0
    pci0: <multimedia, audio="">at device 17.5 (no driver attached)
    vr0: <via 10="" vt6102="" rhine="" ii="" 100basetx="">port 0xf600-0xf6ff mem 0xfdffe000-0xfdffe0ff irq 11 at device 18.0 on pci0
    vr0: Quirks: 0x0
    vr0: Revision: 0x78
    miibus4: <mii bus="">on vr0
    ukphy4: <generic ieee="" 802.3u="" media="" interface="">PHY 1 on miibus4
    ukphy4:  10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto
    vr0: [ITHREAD]
    atrtc0: <at realtime="" clock="">port 0x70-0x73 irq 8 on acpi0
    uart0: <16550 or compatible> port 0x3f8-0x3ff irq 4 flags 0x10 on acpi0
    uart0: [FILTER]
    uart1: <16550 or compatible> port 0x2f8-0x2ff irq 3 on acpi0
    uart1: [FILTER]
    ppc0: <parallel port="">port 0x378-0x37f,0x778-0x77b irq 7 drq 3 on acpi0
    ppc0: SMC-like chipset (ECP/EPP/PS2/NIBBLE) in COMPATIBLE mode
    ppc0: FIFO with 16/16/9 bytes threshold
    ppc0: [ITHREAD]
    ppbus0: <parallel port="" bus="">on ppc0
    plip0: <plip network="" interface="">on ppbus0
    plip0: [ITHREAD]
    lpt0: <printer>on ppbus0
    lpt0: [ITHREAD]
    lpt0: Interrupt-driven port
    ppi0: <parallel i="" o="">on ppbus0
    pmtimer0 on isa0
    sc0: <system console="">at flags 0x100 on isa0
    sc0: VGA <16 virtual consoles, flags=0x300>
    vga0: <generic isa="" vga="">at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0
    atkbdc0: <keyboard controller="" (i8042)="">at port 0x60,0x64 on isa0
    atkbd0: <at keyboard="">irq 1 on atkbdc0
    kbd0 at atkbd0
    atkbd0: [GIANT-LOCKED]
    atkbd0: [ITHREAD]
    est0: <enhanced speedstep="" frequency="" control="">on cpu0
    est: CPU supports Enhanced Speedstep, but is not recognized.
    est: cpu_vendor CentaurHauls, msr 8100a1308000a13
    device_attach: est0 attach returned 6
    p4tcc0: <cpu frequency="" thermal="" control="">on cpu0
    Timecounter "TSC" frequency 997505807 Hz quality 800
    Timecounters tick every 1.000 msec
    IPsec: Initialized Security Association Processing.
    usbus0: 12Mbps Full Speed USB v1.0
    usbus1: 12Mbps Full Speed USB v1.0
    usbus2: 12Mbps Full Speed USB v1.0
    usbus3: 12Mbps Full Speed USB v1.0
    usbus4: 480Mbps High Speed USB v2.0
    ad0: 999MB <pqi ide="" diskonmodule="" 060729da="">at ata0-master WDMA2
    ugen0.1: <via>at usbus0
    uhub0: <via 1="" 9="" uhci="" root="" hub,="" class="" 0,="" rev="" 1.00="" 1.00,="" addr="">on usbus0
    ugen1.1: <via>at usbus1
    uhub1: <via 1="" 9="" uhci="" root="" hub,="" class="" 0,="" rev="" 1.00="" 1.00,="" addr="">on usbus1
    ugen2.1: <via>at usbus2
    uhub2: <via 1="" 9="" uhci="" root="" hub,="" class="" 0,="" rev="" 1.00="" 1.00,="" addr="">on usbus2
    ugen3.1: <via>at usbus3
    uhub3: <via 1="" 9="" uhci="" root="" hub,="" class="" 0,="" rev="" 1.00="" 1.00,="" addr="">on usbus3
    ugen4.1: <via>at usbus4
    uhub4: <via 1="" 9="" ehci="" root="" hub,="" class="" 0,="" rev="" 2.00="" 1.00,="" addr="">on usbus4
    Root mount waiting for: usbus4 usbus3 usbus2 usbus1 usbus0
    uhub0: 2 ports with 2 removable, self powered
    uhub1: 2 ports with 2 removable, self powered
    uhub2: 2 ports with 2 removable, self powered
    uhub3: 2 ports with 2 removable, self powered
    Root mount waiting for: usbus4
    Root mount waiting for: usbus4
    Root mount waiting for: usbus4
    uhub4: 8 ports with 8 removable, self powered
    ugen4.2: <ralink>at usbus4
    Trying to mount root from ufs:/dev/ad0s1a</ralink></via></via></via></via></via></via></via></via></via></via></pqi></cpu></enhanced></at></keyboard></generic></system></parallel></printer></plip></parallel></parallel></at></generic></mii></via></multimedia,></isa></pci-isa></via></via></via></via></via></via></via></via></via></via></ata></ata></via></generic></mii></sun></bridge></generic></mii></sun></bridge></generic></mii></sun></bridge></generic></mii></sun></bridge></pci></pci-pci></vga-compatible></pci></pci-pci></via></acpi></acpi></power></acpi></cn700></aes-cbc,sha1,sha256></software></rng,aes,aes-ctr,sha1,sha256,rsa></sse3,est,tm2,xtpr></fpu,vme,de,pse,tsc,msr,pae,mce,cx8,sep,mtrr,pge,cmov,pat,clflush,acpi,mmx,fxsr,sse,sse2,tm,pbe>



  • @craigduff:

    uhub4: 8 ports with 8 removable, self powered
    ugen4.2: <ralink>at usbus4
    Trying to mount root from ufs:/dev/ad0s1a</ralink>

    ugen is a "catch all" usb device - the device you have plugged in is not recognised by a specific device driver.

    Here's an extract from startup on one of my systems showing a Ralink USB WiFi adapter claimed by the run device driver:

    uhub3: 6 ports with 6 removable, self powered
    ugen3.2: <ralink>at usbus3
    run0: <1.0> on usbus3
    run0: MAC/BBP RT3070 (rev 0x0201), RF RT3020 (MIMO 1T1R), address c8:3a:35:c4:ee:f3
    run0: firmware RT2870 loaded
    Trying to mount root from ufs:/dev/ad0s1a</ralink>

    Your system doesn't have a device driver which is prepared to claim the Ralink USB device.



  • ok so that makes perfect sense. Is there a way i can make it use a driver, by installing one? Can you assist? Thank you for the reply btw!!



  • @craigduff:

    Is there a way i can make it use a driver, by installing one?

    Yes. Do you have a suitable driver?

    @craigduff:

    Can you assist?

    If it involves more than about 5 minutes of my time, not as a volunteer.



  • I was wondering if we can take the ralink 5370 driver from ralink's site and compile it to work with pfsense?  Is that possible?



  • @flynhawaiian:

    I was wondering if we can take the ralink 5370 driver from ralink's site and compile it to work with pfsense?  Is that possible?

    If that driver is not a FreeBSD driver then it won't be of much use. If you post a link to it I can take a closer look.



  • Here is the link.  It is the 3rd one, "RT8070 /RT3070 /RT3370 /RT5370 /RT5372 USB"  I cannot post a direct link to it.  Thanks for your help!

    http://www.ralinktech.com/en/04_support/support.php?sn=501



  • @flynhawaiian:

    Here is the link.  It is the 3rd one, "RT8070 /RT3070 /RT3370 /RT5370 /RT5372 USB"  I cannot post a direct link to it.  Thanks for your help!

    http://www.ralinktech.com/en/04_support/support.php?sn=501

    That is for a Linux driver. There would be considerable work required to convert a Linux driver to FreeBSD (the operating system of pfSense).

    The RT3070 is supported by the FreeBSD run driver in pfSense 2.0.x and 2.1 Snapshot builds. The TP-Link TL-WN321G (which seems to have the RT3070 chipset) can be purchased where I live for less than the local equivalent of US$13. Why spend hours tinkering to save spending such a small amount to buy an interface that others have found to work?



  • I was looking for a wireless n capable one with an external antenna that can be changed.  I don't need the wireless n right now, but it would be nice to have it for future upgradability.  Any thoughts?



  • Or would this one do it?

    http://tinyurl.com/9pau3p3



  • @flynhawaiian:

    Or would this one do it?

    http://tinyurl.com/9pau3p3

    For the price I would consider it worth trying. It says it has a supported chipset but that doesn't mean it will work: The chipset designers generally have a default Vendor code and product code programmed in the chipset. However adapter designers are often given a mechanism to override those codes. Thus  DLink adapter using a RALINK chipset may have a DLink Vendor code and so not be recognised by the driver for the Ralink chipset. Adapter designers can often add their own "added value" tweaks to a device and require their own firmware to make use of those tweaks. Thus the "standard" chipset firmware might (at best) not be able to activate those tweaks (for example, higher power output) or (at worst) not play ball at all with the chipset driver.

    At the quoted price, I suspect there isn't much scope for "adding value" to a RALINK reference design so I would guess it would probably work OK but since I have not even seen one, yet alone plugged one into a pfSense box, a guess is the best I can offer.

    If you aren't likely to cry over "wasting" the purchase price I would encourage you to buy one, try it and report back here. I expect I would likely purchase a couple if you give a good report.



  • I just ordered 2, so hopefully I'll have some good feedback soon.  It's from china so it will take a while.  My guess on the high power output is due to the antenna.  What is nice is it does wireless n, which is coming to freebsd soon.  Fingers Crossed



  • @flynhawaiian:

    Any thoughts?

    Separate AP.



  • This rt3070 usb wireless adapter is recognized, but is having issues working.  I upgraded to the new snapshot 2.1, and it seems to fail to include the run(0) driver.  I am wondering if I would can use the freebsd ralink driver?  Apparently it even supports wireless n.  The issue is, I am unsure how to download it into the pfsense box and run makefile.  Anyhelp would be awesome!!  Attached is the GIT for the file, and the forum link that it comes from.  this is the final piece of the puzzle for me.  Even if it is just wireless g I would be happy!

    http://forums.freebsd.org/showthread.php?t=7562

    http://gitorious.org/run/run/trees/8.1_REL



  • @flynhawaiian:

    I upgraded to the new snapshot 2.1, and it seems to fail to include the run(0) driver.

    What is your evidence for that? I have used a number of different pfSense 2.1 snapshots and the run driver has been in every one of them. It is possible the run driver has been accidentally omitted from recent snapshot builds but I suspect "missing run driver" is not your problem.



  • Actually it is missing.  I went through the entire system.



  • @flynhawaiian:

    Actually it is missing.  I went through the entire system.

    What do you mean by "I went through the whole system"?

    Apparently you are doing something and interpreting the results as "missing run driver". I would like to know what you are doing and the raw (uninterpreted) results.



  • Before I send you the results I’m going to try the newest snapshot to see if that will correct the issue.  I’m still hoping I can get this working properly.  If not I may just give up and get a wireless AP and call it good until wireless N or the newest ralink 3070 drivers are supported.  If not I’m wondering if I can compile the newest freebsd 3070 drivers and try those.  Thoughts on the later?

    http://forums.freebsd.org/showthread.php?t=7562

    http://gitorious.org/run/run/trees/8.1_REL



  • Alright it's finally working again.  The driver must not have been in the prior snapshot or something.

    Now the problem is setting up the wireless to work properly.  I have it serving out dhcp numbers, but the wireless clients cannot connect up to the webconfig.  I have all of the firewall rules turned off while I’m trying to get this working properly.  It is working perfectly when connected directly to the LAN port.  I set it as an access point, assuming that this was the correct setting.

    How I have it setup is:
    LAN = 10.10.5.200
    WiFi = None
    Bridge = None (LAN + WiFi)



  • I got it working actually.  Now the only problem is the usb wireless card is dropping connections every so often.


Log in to reply