Date: Thu, 10 Sep 2009 03:59:40 GMT From: Micah Roark <micahroark@gmail.com> To: freebsd-gnats-submit@FreeBSD.org Subject: amd64/138688: rum possibly broken on 8 Beta 4 amd64: Linksys WUSB54GC v1 device appears as rum, clonable to wlan0, able to wpa authenticate + obtain dhclient address, no communication though. Message-ID: <200909100359.n8A3xeoc078363@www.freebsd.org> Resent-Message-ID: <200909100400.n8A40AKB031538@freefall.freebsd.org>
next in thread | raw e-mail | index | archive | help
>Number: 138688 >Category: amd64 >Synopsis: rum possibly broken on 8 Beta 4 amd64: Linksys WUSB54GC v1 device appears as rum, clonable to wlan0, able to wpa authenticate + obtain dhclient address, no communication though. >Confidential: no >Severity: non-critical >Priority: low >Responsible: freebsd-amd64 >State: open >Quarter: >Keywords: >Date-Required: >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Thu Sep 10 04:00:09 UTC 2009 >Closed-Date: >Last-Modified: >Originator: Micah Roark >Release: 8 Beta 4 >Organization: >Environment: FreeBSD fbsdtest4.gateway.2wire.net 8.0-BETA4 FreeBSD 8.0-BETA4 #0: Sun Sep 6 05:51:03 UTC 2009 root@almeida.cse.buffalo.edu:/usr/obj/usr/src/sys/GENERIC amd64 >Description: Machine: Dell Studio 14z Built-in wifi is reported (pciconf -lv) as Atheros AR5B91 (class=0x028000 card=0x0200168c chip=0x002a168c rev=0x01 hdr=0x00), after much testing with B3 and B4 amd64 and i386, unable to communicate with device, although it does appear as ath, is clonable, and configurable. Reverted to using Linksys WUSB54GC v1 USB wireless adapter reporting (usbconfig) as ugen1.2: <Compact Wireless-G USB Adapter Cisco-Linksys> at usbus1, cfg=0 md=HOST, spd=HIGH (480Mbps) pwr=ON On 8 Beta 4 amd64, am able to see the device (ifconfig) as rum0, able to clone as wlan0 (ifconfig wlan0 create wlandev rum0 up), able to authenticate with wpa (wpa_supplicant -i wlan0 -c /etc/wpa_supplicant.conf), and able to obtain IP with dhclient (dhclient wlan0). Unable to communicate. For example, pinging the gateway shows no activity on the terminal from the ping command, however the led on the device is lighting as if pinging is taking place. Further, pinging the machine from a remote computer on the LAN causes the led to also light in time with the ping attempts on the remote computer, though no reply is returned. Same results with WEP auth. Unable to return scan results on ifconfig wlan0 up scan. On 8 Beta 4 i386, appears to be working well after 30 minutes of steady activity (downloads resulting from building ports). >How-To-Repeat: >Fix: >Release-Note: >Audit-Trail: >Unformatted:
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200909100359.n8A3xeoc078363>