Re: Problem with using wireless usb adapter

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Bill Davidsen writes:
>Brian Wood wrote:
>> I'm having some trouble getting internet/ssh working over
>> a Linksys wireless usb adapter -- model WUSB54GSC.
>>
>> I did get it working one time, but don't know why or if
>> I did something to make it work.  I see the access
>> point I want to use and connect to it.  That seems to work.
>> Then iwconfig reports
>>
>> lo        no wireless extensions.
>>
>> eth0      no wireless extensions.
>>
>> wlan2     IEEE 802.11bg  ESSID:"brian"
>>           Mode:Managed  Frequency:2.432 GHz  Access Point: 00:1C:10:3B:06:97
>>           Bit Rate=36 Mb/s   Tx-Power=14 dBm
>>           RTS thr=2347 B   Fragment thr=2346 B
>>           Link Quality=57/100  Signal level=57/100
>>           Rx invalid nwid:0  Rx invalid crypt:0  Rx invalid frag:0
>>           Tx excessive retries:0  Invalid misc:0   Missed beacon:0
>>
>> But bringing up a URL or ssh'ing to another machine doesn't work.
>> I'm using Fedora 12.  If I use an ethernet cable instead of the
>> wireless, everything works fine.  Any ideas on what to check
>> or do?
>>
> I see two things here, one is that there is no IP on that wlan2, indicating that
> it is connected but not routed. The other is that it's wlan2 insteadl of wlan0,
> indicating that something is going on, since even with the built-in (802.11g)
> and plug-in (802.11n) NICs, I have wlan0 and wlan1, so they always do start and
> zero and go consecutively.
>
> Try:
> - dhclient wlan2
> - netstat -r
> and post the results. I would expect you will get connections after that.

Hi, Bill,

Unfortunately I've not been able to get it working yet. dhclient
didn't output anything.  The netstat -r output:
Kernel IP routing table
Destination     Gateway         Genmask         Flags   MSS Window  irtt Iface
192.168.50.0    *               255.255.255.0   U         0 0          0 wlan2
default         192.168.50.1    0.0.0.0         UG        0 0          0 wlan2


> Your dmesg output should have information of why that's wlan2, please read and
> report.

Here's the result of dmesg | grep wlan:

wlan0: register 'rndis_wlan' at usb-0000:00:03.3-1, Wireless RNDIS device, BCM4320b based, 00:1e:e5:a6:98:ee
usbcore: registered new interface driver rndis_wlan
udev: renamed network interface wlan0 to wlan2
rndis_wlan 1-1:1.0: rndis media disconnect
ADDRCONF(NETDEV_UP): wlan2: link is not ready
rndis_wlan 1-1:1.0: rndis media connect
ADDRCONF(NETDEV_CHANGE): wlan2: link becomes ready
wlan2: no IPv6 routers present
rndis_wlan 1-1:1.0: rndis media disconnect
rndis_wlan 1-1:1.0: rndis media connect
rndis_wlan 1-1:1.0: rndis media disconnect
rndis_wlan 1-1:1.0: rndis media connect


Regards,
Brian Wood
http://www.webEbenezer.net




-- 
fedora-list mailing list
fedora-list@xxxxxxxxxx
To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list
Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines

[Index of Archives]     [Current Fedora Users]     [Fedora Desktop]     [Fedora SELinux]     [Yosemite News]     [Yosemite Photos]     [KDE Users]     [Fedora Tools]     [Fedora Docs]

  Powered by Linux