Bug 138688 - [rum] possibly broken on 8 Beta 4 amd64: able to wpa authenticate + obtain dhclient address, no communication though.
Summary: [rum] possibly broken on 8 Beta 4 amd64: able to wpa authenticate + obtain dh...
Status: Closed Unable to Reproduce
Alias: None
Product: Base System
Classification: Unclassified
Component: kern (show other bugs)
Version: Unspecified
Hardware: Any Any
: Normal Affects Only Me
Assignee: freebsd-bugs (Nobody)
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-09-10 05:00 UTC by Micah Roark
Modified: 2018-12-18 04:03 UTC (History)
1 user (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Micah Roark 2009-09-10 05:00:09 UTC
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).
Comment 1 Gavin Atkinson freebsd_committer freebsd_triage 2009-09-11 12:02:12 UTC
Responsible Changed
From-To: freebsd-amd64->freebsd-net

Over to maintainer(s)
Comment 2 Andriy Gapon freebsd_committer freebsd_triage 2010-12-05 14:02:09 UTC
Is this still a problem?
If yes, please try discussing it on net@ mailing list.

-- 
Andriy Gapon
Comment 3 Eitan Adler freebsd_committer freebsd_triage 2017-12-31 07:59:31 UTC
For bugs matching the following criteria:

Status: In Progress Changed: (is less than) 2014-06-01

Reset to default assignee and clear in-progress tags.

Mail being skipped
Comment 4 Andriy Voskoboinyk freebsd_committer freebsd_triage 2018-12-18 04:03:57 UTC
The driver should be stable enough at least since base r305544.