Tag Archives: wireless

wpi-monitor: simple script to keep the wireless link up

I’m using a rum device in Host AP mode, so every time I try to send a large file or open many connections, the wireless link breaks down (gets “no carrier” instead of “associated”). To get it back up, I have to pull the interface on the station computer (wpi) down and then back up.

To automate the process, I’ve written this simple script. To be run with root/operator permissions.

#!/bin/sh
# Stop wpi from falling off.

if=wpi0 # interface name

while true
do
        # see if it has "no carrier" status, by looking for "no"
        status=`ifconfig $if | grep status | cut -d ":" -f 2 | cut -d " " -f 2`

        # bourne shell string comparison... you can has it
        if [ "$status" = "no" ] ; then
                ifconfig $if down
                ifconfig $if up
#               echo down
        else
#               echo up
        fi

        sleep 1
done

DWA-110 on FreeBSD: if_rum additions

It works. I’m using the rum driver for Host AP mode, so it actually sucks being me. Fact is, device is supported. I did get WPA2 up, following the Handbook.

Add

product DLINK2 DWA110 0x3c07 DWA-110

to usbdevs and

{ USB_VENDOR_DLINK2, USB_PRODUCT_DLINK2_DWA110 },

to if_rum.c.

D-Link DWA-110 IDs

Here’s what sysctl says:

dev.ugen.1.%pnpinfo: vendor=0x07d1 product=0x3c07 devclass=0x00 devsubclass=0x00 release=0x0001 sernum=""

D-Link DWA-110 chip

I’ve opened up my DWA-110, it has a RT2571WF (Ralink) chip inside. Which gives us the RT5201USB chipset, according to this page and man rum.

By the way, I see the DWA-111 device ID having been added to the FreeBSD 7 CVS (rum driver). I’m pretty sure DWA-110 is supported, too. There’s an appropriate gap in the device ID list. (Can’t check it right now, since in Windows.)

Note on wireless networking, Windows XP SP2

Did set up an ad-hoc wireless network in Windows, using Intel PRO/Wireless 3945ABG, driver version 11.5.1.15 (released 13-03-2008), and D-Link DWA-110, driver version 1.2.1.0 (released 14-05-2007). NOTE: the latter driver not present on main D-Link site, use the Australian instead.

Using vendor-specific software to manage wireless networks, not Windows-bundled.

So far WEP only, haven’t tried WPA.

No editing of specific wireless communication parameters (B/G filtering, ad hoc channel selection, etc.) was needed. NOTE: the Intel device, even when set channel 11 (default) in “Device Properties”, still tried to use channel 6 when connecting. This wasn’t visible in default Microsoft wireless connection management software, and was only made evident when using Intel’s own.