Welcome! Log In Create A New Profile

Advanced

[Solved] Realtek Wireless Dongle AWLL6075 - Stops working if ethernet cable is removed

Posted by varkey 
I have this USB wireless dongle - Airlink101 AWLL6075 and lsusb shows this

Quote

Bus 001 Device 005: ID 0bda:8172 Realtek Semiconductor Corp. RTL8191S WLAN Adapter

I have compiled a kernel with the drivers for the device and dmesg shows this when I attach the device, so it seems the driver is loaded fine.

Quote

[ 230.522346] usb 1-1: new high speed USB device using orion-ehci and address 2
[ 230.784280] r8712u: module is from the staging directory, the quality is unknown, you have been warned.
[ 230.812417] r8712u: DriverVersion: v7_0.20100831
[ 230.817107] r8712u: register rtl8712_netdev_ops to netdev_ops
[ 230.823546] r8712u: USB_SPEED_HIGH with 4 endpoints
[ 230.829131] r8712u: Boot from EFUSE: Autoload OK
[ 231.570761] r8712u: CustomerID = 0x0000
[ 231.574972] r8712u: MAC Address from efuse = 00:xx:xx:xx:xx:x5
[ 231.584432] usbcore: registered new interface driver r8712u
[ 299.122888] r8712u: 1 RCR=0x153f00e
[ 299.127127] r8712u: 2 RCR=0x553f00e

I installed wpasupplicant & wireless-tools packages and my /etc/network/interfaces file corresponding the wlan0 is this

Quote

auto wlan0
iface wlan0 inet static
address 192.168.2.150
netmask 255.255.255.0
network 192.168.2.0
wpa-ssid "myssid"
wpa-psk "mywpapass"

Output of 'iwconfig wlan0'

Quote

wlan0 IEEE 802.11bg ESSID:"myssid" Nickname:"rtl_wifi"
Mode:Managed Frequency:2.437 GHz Access Point: 00:cc:cc:cc:cc:60
Bit Rate:54 Mb/s Sensitivity:0/0
Retry:off RTS thr:off Fragment thr:off
Encryption key:****-****-****-****-****-****-****-**** Security mode:open
Power Management:off
Link Quality=100/100 Signal level=100/100 Noise level=0/100
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:0 Invalid misc:0 Missed beacon:0

Now the issue is that, if I remove the ethernet cable or bring down the eth0 interface the dockstar stops responding to ping. But if I check my wireless router I can see the dongle as an active wireless client the whole time. If I attach the cable again it starts responding to ping immediately.

Any idea what might be the issue here?



Edited 1 time(s). Last edit at 06/17/2011 03:55PM by varkey.
Please post your 'ifconfig' output and the resolv.conf & network/interfaces (under /etc). Did you configure a gateway? Are both interfaces in the same subnet?

Maybe a static route makes 'ping' try to connect with eth0 interface and it doesn't work.
Re: Realtek Wireless Dongle AWLL6075 - Stops working if ethernet cable is removed
June 17, 2011 02:05PM
Here are the details you asked for

ifconfig

Quote

eth0 Link encap:Ethernet HWaddr 00:cc:cc:cc:cc:b0
inet addr:192.168.2.75 Bcast:192.168.2.255 Mask:255.255.255.0
inet6 addr: fe80::210:75ff:fe26:45b0/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:3333 errors:0 dropped:2 overruns:0 frame:0
TX packets:4575 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:5000
RX bytes:1325501 (1.2 MiB) TX bytes:997030 (973.6 KiB)
Interrupt:11

lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:58 errors:0 dropped:0 overruns:0 frame:0
TX packets:58 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:6938 (6.7 KiB) TX bytes:6938 (6.7 KiB)

wlan0 Link encap:Ethernet HWaddr 00:cc:cc:cc:cc:55
inet addr:192.168.2.150 Bcast:192.168.2.255 Mask:255.255.255.0
inet6 addr: fe80::221:2fff:fe39:4a55/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:3418 errors:0 dropped:156 overruns:0 frame:0
TX packets:63 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:816215 (797.0 KiB) TX bytes:4719 (4.6 KiB)

/etc/network/interfaces

Quote

auto lo eth0
iface lo inet loopback

iface eth0 inet static
address 192.168.2.75
netmask 255.255.255.0
network 192.168.2.0
gateway 192.168.2.1

auto wlan0
iface wlan0 inet static
address 192.168.2.150
netmask 255.255.255.0
network 192.168.2.0
wpa-ssid "myssd"
wpa-psk "mywpapass"

resolve.conf
Quote

nameserver 208.67.222.222
nameserver 8.8.8.8
nameserver 202.88.231.2

Yes I have configured the gateway as 192.168.2.1 and yes both are in the same subnet as you can see.

Quote

root@goflex:/home/varkey# ip route show
192.168.2.0/24 dev eth0 proto kernel scope link src 192.168.2.75
192.168.2.0/24 dev wlan0 proto kernel scope link src 192.168.2.150
default via 192.168.2.1 dev eth0

So any configuration error here?



Edited 1 time(s). Last edit at 06/17/2011 02:08PM by varkey.
Re: Realtek Wireless Dongle AWLL6075 - Stops working if ethernet cable is removed
June 17, 2011 03:13PM
Quote
pazos
Maybe a static route makes 'ping' try to connect with eth0 interface and it doesn't work.

Thank you. That was the problem.

There was a default route defined for eth0 which had higher preference than the wlan0 route.

Kernel IP routing table
Destination     Gateway         Genmask         Flags Metric Ref    Use Iface
192.168.2.0     0.0.0.0         255.255.255.0   U     0      0        0 eth0
192.168.2.0     0.0.0.0         255.255.255.0   U     0      0        0 wlan0
0.0.0.0         192.168.2.1     0.0.0.0         UG    0      0        0 wlan0
0.0.0.0         192.168.2.1     0.0.0.0         UG    0      0        0 eth0

The first route was causing the problem, so I edited my /etc/network/interfaces like given below to delete that route when the wlan0 interface comes up and add it again when wlan0 goes down.

auto wlan0
iface wlan0 inet static
        address 192.168.2.150
        netmask 255.255.255.0
        network 192.168.2.0
        gateway 192.168.2.1
        wpa-ssid "myssid"
        wpa-psk "mywpapass"
        post-up route del -net 192.168.2.0 netmask 255.255.255.0 dev eth0
        pre-down route add -net 192.168.2.0 netmask 255.255.255.0 dev eth0

Now everything is working perfectly and it boots fine with just the wireless adapter as well. :)



Edited 2 time(s). Last edit at 03/02/2012 12:37AM by varkey.
Re: Realtek Wireless Dongle AWLL6075 - Stops working if ethernet cable is removed
October 03, 2011 04:50PM
I'm currently experiencing the same issue, but your fix doesn't work for me. Right now, /etc/network/interfaces looks like:

auto lo
iface lo inet loopback
auto eth0
iface eth0 inet static
        address 192.168.1.101
        network 192.168.1.0
        netmask 255.255.255.0
        broadcast 192.168.1.255
        gateway 192.168.1.1
        dns-nameservers 192.168.1.1
auto wlan0
iface wlan0 inet static
        #wpa-driver ????
        wpa-ssid calvin
        wpa-bssid [mymac]
        wpa-psk "[mypass]"
        wpa-key-mgmt WPA-PSK
        #wpa-pairwise TKIP CCMP
        #wpa-group TKIP CCMP
        #wpa-proto WPA RSN
        #wireless-essid calvin
        #wireless-mode master
        address 192.168.1.109
        network 192.168.1.0
        netmask 255.255.255.0
        broadcast 192.168.1.255
        gateway 192.168.1.1
        dns-nameservers 192.168.1.1
        post-up route del -net 192.168.1.0 netmask 255.255.255.0 dev eth0
        pre-down route add -net 192.168.1.0 netmask 255.255.255.0 dev eth0

And `route` shows:

Kernel IP routing table
Destination     Gateway         Genmask         Flags Metric Ref    Use Iface
192.168.1.0     *               255.255.255.0   U     0      0        0 wlan0
default         WNDR3700v2      0.0.0.0         UG    0      0        0 wlan0
default         WNDR3700v2      0.0.0.0         UG    0      0        0 eth0

Any insights appreciated.
hi rawsted...

please post the output of 'route -n'

Your interfaces file has redundant information...

I would try to change it to:

auto lo
iface lo inet loopback
auto eth0
iface eth0 inet static
address 192.168.1.101
netmask 255.255.255.0
gateway 192.168.1.1
auto wlan0
iface wlan0 inet static
wpa-driver wext
wpa-ssid calvin
wpa-bssid [mymac]
wpa-psk "[mypass]"
wpa-key-mgmt WPA-PSK
address 192.168.1.109
netmask 255.255.255.0
gateway 192.168.1.1


you don't need to specify a dns-server if it is the same as your gateway!

Please change your /etc/network/interfaces (keep a backup first of your config) and then post your 'route -n' output..
pazos,

My /etc/network/interfaces file now looks like:

auto lo
iface lo inet loopback
auto eth0
iface eth0 inet static
        address 192.168.1.101
        netmask 255.255.255.0
        gateway 192.168.1.1
auto wlan0
iface wlan0 inet static
        wpa-driver wext
        wpa-ssid calvin
        wpa-bssid [mymac]
        wpa-psk "[mypass]"
        wpa-key-mgmt WPA-PSK
        #wpa-pairwise TKIP CCMP
        #wpa-group TKIP CCMP
        #wpa-proto WPA RSN
        #wireless-essid calvin
        #wireless-mode master
        address 192.168.1.109
        netmask 255.255.255.0
        gateway 192.168.1.1
        #post-up route del -net 192.168.1.0 netmask 255.255.255.0 dev eth0
        #pre-down route add -net 192.168.1.0 netmask 255.255.255.0 dev eth0

Note that varkey`s fix has been commented out.

`route -n` shows:

Kernel IP routing table
Destination     Gateway         Genmask         Flags Metric Ref    Use Iface
192.168.1.0     0.0.0.0         255.255.255.0   U     0      0        0 wlan0
192.168.1.0     0.0.0.0         255.255.255.0   U     0      0        0 eth0
0.0.0.0         192.168.1.1     0.0.0.0         UG    0      0        0 eth0
0.0.0.0         192.168.1.1     0.0.0.0         UG    0      0        0 wlan0

And the issue persists. As soon as I unplug the wired interface, I can no longer ping the wireless IP



Edited 1 time(s). Last edit at 10/06/2011 06:27AM by rawsted.
>And the issue persists. As soon as I unplug the wired interface, I can no longer ping the wireless IP

But, can you associate with the AP?. Cause maybe your wireless iface doesn't connect and the only way to see it and to ping it is via wired connection.

Anyways,if you use Dinamic IP on your wireless connection & Static IP on your wired connection, both dhcpcd & dhclient managed to gets things work with routing table

just simply

wpa_passphrase calvin mypass > /etc/yourwpaconf (save configuration to a file)
wpa_supplicant -B -D wext -i wlan0 -c /etc/yourwpaconf (associate with the AP)
dhcpcd wlan0 # or # dhclient wlan0
pazos Wrote:
-------------------------------------------------------
> But, can you associate with the AP?. Cause maybe
> your wireless iface doesn't connect and the only
> way to see it and to ping it is via wired
> connection.

Yes. I was actually wrong about the behavior in my prior post. Last night, I SSH'd to the wireless IP and brought down the wired interface - the session stayed alive. After a few minutes, I unplugged the wired interface from the router - the session stayed alive. It was only after some time (say 10 minutes) that it died and I could no longer ping the wireless IP

> Anyways,if you use Dinamic IP on your wireless
> connection & Static IP on your wired connection,
> both dhcpcd & dhclient managed to gets things work
> with routing table
>
> just simply
>
> wpa_passphrase calvin mypass > /etc/yourwpaconf
> (save configuration to a file)
> wpa_supplicant -B -D wext -i wlan0 -c
> /etc/yourwpaconf (associate with the AP)
> dhcpcd wlan0 # or # dhclient wlan0

The nature of my application makes a static IP more desirable...

I found this topic:
http://forum.doozan.com/read.php?2,563

Do you suppose a different kernel would solve the issue?
If you want to set static ip for wireless you can try DHCP Static leases for your device (attaching your wireless interface MAC to an IP). I really think that is a configuration problem, not a kernel or device problem.

When I started to play with embedded devices like pogo I found that worked better if I declare only wired interfaces in /etc/network/interfaces and then make a script at the end of boot process that setup wireless connection. I'm actually using Armedslack but I've tried Angstrom, Debian & Arch with same results.

When your computer starts to boot it makes a routing table. Sometimes is better to leave this table the little you can and do it some changes "on the fly", that is my point for use DHCP (both static or dinamic leases)
Pazos,

Thanks for your help - I'll try static leasing as my last avenue. If I get the same results, I'm going to pick up a different adapter.
hello,
I have probably the same problem, but not always, except both wlan0 and eth0 get an ip from dhcp.
And I configured both interface with auto and auto plug.
Author:

Your Email:


Subject:


Spam prevention:
Please, enter the code that you see below in the input field. This is for blocking bots that try to post this form automatically. If the code is hard to read, then just try to guess it right. If you enter the wrong code, a new image is created and you get another chance to enter it right.
Message: