Wireless up but no Internet

English Network/Internet
1

I have the following device:
Device: D-Link AirPremier DWL-G550 Wireless PCI Adapter
Device Name: wlan0
Driver: ath5k

Operating System: OpenSUSE 12.1 x86_64

At the moment, my router gave my wired connection (eth1) IP 192.168.0.57 and my wireless connection (wlan0) 192.168.0.58. When I pull the ethernet cable out, I lose my Internet connection, when it should fall over to the wireless connection. I have ran several commands to troubleshoot the issue, but from what I can see, it looks like it is connected. And I can see from the router webpage it showing the machine and IP as connected as a wireless client. Below are the commands I ran to provide as much information as possible.

ifstatus wlan0
wlan0 device: Atheros Communications Inc. AR5212/AR5213 Multiprotocol MAC/baseband processor (rev 01)
DHCP4 client (dhcpcd) is running
IP address: 192.168.0.58/16
DHCP6 client (dhclient6) is running
. . . but is still waiting for data
2: wlan0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP qlen 1000
link/ether 00:1b:11:be:fc:84 brd ff:ff:ff:ff:ff:ff
inet 192.168.0.58/16 brd 192.168.255.255 scope global wlan0
inet6 fe80::21b:11ff:febe:fc84/64 scope link
valid_lft forever preferred_lft forever
wlan0 is up
bssid=1c:af:f7:d7:27:21
ssid=Wes Router
id=0
mode=station
pairwise_cipher=CCMP
group_cipher=TKIP
key_mgmt=WPA2-PSK
wpa_state=COMPLETED
ip_address=192.168.0.58

iwconfig
wlan0 IEEE 802.11bg ESSID:“Wes Router”
Mode:Managed Frequency:2.462 GHz Access Point: 1C:AF:F7:D7:27:21
Bit Rate=11 Mb/s Tx-Power=27 dBm
Retry long limit:7 RTS thr:off Fragment thr:off
Encryption key:off
Power Management:off
Link Quality=70/70 Signal level=-36 dBm
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:4 Invalid misc:23 Missed beacon:0

ifconfig
eth1 Link encap:Ethernet HWaddr 00:11:D8:9A:71:FE
inet addr:192.168.0.57 Bcast:192.168.255.255 Mask:255.255.0.0
inet6 addr: fe80::211:d8ff:fe9a:71fe/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:46410 errors:0 dropped:0 overruns:0 frame:0
TX packets:24900 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:43878655 (41.8 Mb) TX bytes:2441526 (2.3 Mb)
Interrupt:22 Base address:0xc000

wlan0 Link encap:Ethernet HWaddr 00:1B:11:BE:FC:84
inet addr:192.168.0.58 Bcast:192.168.255.255 Mask:255.255.0.0
inet6 addr: fe80::21b:11ff:febe:fc84/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:4212 errors:0 dropped:0 overruns:0 frame:0
TX packets:137 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:401813 (392.3 Kb) TX bytes:24087 (23.5 Kb)

ping -c 5 192.168.0.1
PING 192.168.0.1 (192.168.0.1) 56(84) bytes of data.
From 192.168.0.57 icmp_seq=2 Destination Host Unreachable
From 192.168.0.57 icmp_seq=3 Destination Host Unreachable
From 192.168.0.57 icmp_seq=4 Destination Host Unreachable
From 192.168.0.57 icmp_seq=5 Destination Host Unreachable

— 192.168.0.1 ping statistics —
5 packets transmitted, 0 received, +4 errors, 100% packet loss, time 4000ms
pipe 3

When I did the above ping I noticed it was trying from the eth1 connection rather than the wlan0 connection, and as the wired connection is unplugged, no wonder it says Destination Host Unreachable. However, I do not understand why it is trying to ping from the eth1 and not from wlan0!

iwlist scan
wlan0 Scan completed :
Cell 01 - Address: 1C:AF:F7:D7:27:21
Channel:11
Frequency:2.462 GHz (Channel 11)
Quality=70/70 Signal level=-37 dBm
Encryption key:on
ESSID:“Wes Router”
Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 11 Mb/s; 6 Mb/s
9 Mb/s; 12 Mb/s; 18 Mb/s
Bit Rates:24 Mb/s; 36 Mb/s; 48 Mb/s; 54 Mb/s
Mode:Master
Extra:tsf=000000000c91d579
Extra: Last beacon: 26ms ago
IE: Unknown: 000A57657320526F75746572
IE: Unknown: 010882848B960C121824
IE: Unknown: 03010B
IE: IEEE 802.11i/WPA2 Version 1
Group Cipher : TKIP
Pairwise Ciphers (2) : CCMP TKIP
Authentication Suites (1) : PSK
IE: Unknown: 2A0102
IE: Unknown: 32043048606C
IE: Unknown: DD180050F2020101830003A4000027A4000042435E0062322F00
IE: Unknown: DD1E00904C33CC111BFFFF000000000000000000000000000000000000000000
IE: Unknown: 2D1ACC111BFFFF000000000000000000000000000000000000000000
IE: Unknown: DD1A00904C340B001B00000000000000000000000000000000000000
IE: Unknown: 3D160B001B00000000000000000000000000000000000000
IE: Unknown: 4A0E14000A002C01C800140005001900
IE: Unknown: 7F0101
IE: Unknown: DD0900037F01010000FF7F
IE: Unknown: DD0A00037F04010000004000
IE: Unknown: DD770050F204104A0001101044000102103B00010310470010000000000000100000001CAFF7D7272110210006442D4C696E6B1023000D442D4C696E6B20526F75746572102400074449522D363535104200046E6F6E651054000800060050F2040001101100074449522D363535100800020084103C000103

If someone could help me shed some light on what is going on, I would highly appreciate it.

2

On 02/11/2012 07:26 PM, wslyhbb wrote:
>
> I have the following device:
> Device: D-Link AirPremier DWL-G550 Wireless PCI Adapter
> Device Name: wlan0
> Driver: ath5k
>
> Operating System: OpenSUSE 12.1 x86_64
>
> At the moment, my router gave my wired connection (eth1) IP
> 192.168.0.57 and my wireless connection (wlan0) 192.168.0.58. When I
> pull the ethernet cable out, I lose my Internet connection, when it
> should fall over to the wireless connection. I have ran several
> commands to troubleshoot the issue, but from what I can see, it looks
> like it is connected. And I can see from the router webpage it showing
> the machine and IP as connected as a wireless client. Below are the
> commands I ran to provide as much information as possible.
>
> ifstatus wlan0
> wlan0 device: Atheros Communications Inc. AR5212/AR5213
> Multiprotocol MAC/baseband processor (rev 01)
> DHCP4 client (dhcpcd) is running
> IP address: 192.168.0.58/16
> DHCP6 client (dhclient6) is running
> . . . but is still waiting for data
> 2: wlan0:<BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP
> qlen 1000
> link/ether 00:1b:11:be:fc:84 brd ff:ff:ff:ff:ff:ff
> inet 192.168.0.58/16 brd 192.168.255.255 scope global wlan0
> inet6 fe80::21b:11ff:febe:fc84/64 scope link
> valid_lft forever preferred_lft forever
> wlan0 is up
> bssid=1c:af:f7:d7:27:21
> ssid=Wes Router
> id=0
> mode=station
> pairwise_cipher=CCMP
> group_cipher=TKIP
> key_mgmt=WPA2-PSK
> wpa_state=COMPLETED
> ip_address=192.168.0.58
>
> iwconfig
> wlan0 IEEE 802.11bg ESSID:“Wes Router”
> Mode:Managed Frequency:2.462 GHz Access Point:
> 1C:AF:F7:D7:27:21
> Bit Rate=11 Mb/s Tx-Power=27 dBm
> Retry long limit:7 RTS thr:off Fragment thr:off
> Encryption key:off
> Power Management:off
> Link Quality=70/70 Signal level=-36 dBm
> Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
> Tx excessive retries:4 Invalid misc:23 Missed beacon:0

I really am getting tired of repeating this same information over and over. Why
cannot anyone do any searching.

The iwconfig results say that your wireless has authenticated and associated.
The ifconfig output says that it has gotten an IP number.

Your first problem is that an active eth1 will NEVER allow a wireless
connection. If you are using ifup, you need to have that be active when the
cable is connected, and NOT “on boot”, or “auto”.

What I cannot tell is if your routing is OK. You will need to have one line in
the output of ‘/sbin/route -n’ that mentions wlan0, and has the UG flags set.

3

Thanks for your reply, although a bit rude. I did read the sticky, hence all of the information I provided, plus I looked through the first page of threads. I guess this forum is not that friendly, I will not bother asking any more questions.

4

Just my personal opinion (especially as I am only moderator in the German part of the forum):

I think the main problems are:

  • While a helper or teacher will read the same problem or fault very often it is mostly the first problem/fault of the one how has it (caused). When I was teaching law and especially while correcting the students’ tests I saw often the same fault in many tests and got a bit angry after looking at the same fault e. g. for the 200th time - but it was probably the first time for each student that she or he has made the same fault.
  • As more a helper or teacher knows as more likely it will be that a problems (and its solution) is for him/her evident. If I would have answered the original question my replay may have been more empathetic than the one of the kernel developer - but probably much less helpful…
  • The user is able change or set up most settings in openSUSE with YaST. And in Yast you will find the wireless setup with ifup - but the easiest way for setting up a wireless LAN with openSUSE is with networkmanager and its (GNOME or KDE) helper programs in the panels. This is also the solution for wireless LAN that is recommended in the openSUSE manual(s). But maybe a hint should be added to the text in YaST > Network Settings or/and to the stickies in this forums?
  • In paid support the helper can tell himself that she/he will also be paid for not so clever questions (not only in technic but also in law and so on). So maybe the not payed helper has more expectations in view of the users’ efforts on their own?

And i would not think that

I really am getting tired of repeating this same information over and over. Why
cannot anyone do any searching.
is really rude - especially if combined with a probably helpful hint.

Regards
Martin

5

wslyhbb.

I have had exactly the same experience. Here’s the scenario.

Both the wired and the wifi are configured to come up “on boot”. They both do and both get their respective addresses. However, the wired on always gets the default route. Pull that out and the default route is not reset to the wifi one. As root, do “route add default gw x.x.x.x wlan0” and your network will come back.

x.x.x.x is the IPV4 address of your wlan router and wlan0 is the interface name of your wireless.

If both interfaces are on the same network, why have them both up at the same time?

Configure them both as “on cable connect” and give the highest priority (ifplugd priority) to the one you prefer. In my case, this was the wired one so it got priority 2 and the wireless on priority 1. When connected, the wired one comes up but the wireless one is disabled since it has a lower priority to the wired one.

My guess is that if you give the wired one priority 1 and the wireless priority 2, it should disable the wired and give you the wireless one with it as default route.

Setting them at the same priority will always give you the behaviour you have witnessed regardless of the method you use to bring them up.

Cheers - AK

6

wslyhbb. One more thing. If you configure to bring both interfaces up at the same time and on the same priority, you will find that if your wireless interface cannot find its SSID, it will continually try in the background.

Why carry this extra work?

Cheers - AK

7

Did you notice you reopened a thread from early last year?

8

oops knurpht. No, I didn’t. Sorry.