It might be a problem in the rum interface, because the device connects perfectly to the iwi interface in the laptop. Here are ifconfigs for the devices:

rum0: flags=108843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST,NEEDSGIANT> metric 0 mtu 1500
        ether 00:1c:f0:9d:08:b3
media: IEEE 802.11 Wireless Ethernet autoselect <adhoc> (autoselect <adhoc>)
        status: associated

        ssid bsd7adhoc
        channel 6 (2437 Mhz 11g)
        bssid c6:98:35:ef:28:ae
        authmode OPEN
        privacy OFF
        txpower 50
        scanvalid 60
        bgscan
        bgscanintvl 300
        bgscanidle 250
        roam:rssi11g 7
        roam:rate11g 5
        protmode CTS


iwi0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1500
        ether 00:0e:35:4a:2d:e8
media: IEEE 802.11 Wireless Ethernet autoselect (autoselect <adhoc>)
        status: associated

        ssid omg
        channel 10 (2457 Mhz 11g)
        bssid c6:e6:a6:49:5c:d7
        authmode OPEN
        privacy OFF
        bmiss 10
        scanvalid 60
        bgscan
        bgscanintvl 300
        bgscanidle 250
        roam:rssi11g 7
        roam:rate11g 5
        protmode CTS

I don't know if the differences are significant, but the first one doesn't work and the second one does.

One other thing: when on Windows (i.e. when it's working), the "link" LED on the rum NIC flashes constantly, as well as the "act" LED. On FreeBSD (when it's not), the "link" LED flashes occasionally (presumably when there's data traffic), and the "act" link flashes as constantly as before.

Maybe it has something to do with the missing beacons from my past messages?

The rum(4) man page has a CAVEAT about automatic control of transmit speed but forcing it to DS/1Mbps mode 11b doesn't help (the device is 11b-only).

Attachment: signature.asc
Description: OpenPGP digital signature

Reply via email to