Network Manager seems to connect to WLAN on HP Elitebook 2740p, but unable to use

English Network/Internet
1

Laptop - HP Elitebook 2740p
openSuSE 12.1

I use GNOME 3. The little indicator in the top right hand side appears to connect, but the connection cannot be used. I cannot ping to the router.
Incidentally, I can use GNOME 3 to connect to the same network on LinuxMint 12 (with two other laptops, I haven’t used LinuxMint on this laptop)

lpsci -v shows Intel Centrino, using iwlagn…

43:00.0 Network controller: Intel Corporation Centrino Advanced-N 6200 (rev 35)
	Subsystem: Intel Corporation Centrino Advanced-N 6200 2x2 AGN
	Flags: bus master, fast devsel, latency 0, IRQ 46
	Memory at d0500000 (64-bit, non-prefetchable) [size=8]
	Capabilities: [c8] Power Management version 3
	Capabilities: [d0] MSI: Enable+ Count=1/1 Maskable- 64bit+
	Capabilities: [e0] Express Endpoint, MSI 00
	Capabilities: [100] Advanced Error Reporting
	Capabilities: [140] Device Serial Number 00-23-14-ff-ff-00-d4-cc
	Kernel driver in use: iwlagn

dmesg shows …

    8.267640] Intel(R) Wireless WiFi Link AGN driver for Linux, in-tree:d
    8.267644] Copyright(c) 2003-2011 Intel Corporation
    8.267701] iwlagn 0000:43:00.0: PCI INT A -> GSI 19 (level, low) -> IRQ 19
    8.267711] iwlagn 0000:43:00.0: setting latency timer to 64
    8.267744] iwlagn 0000:43:00.0: pci_resource_len = 0x00002000
    8.267746] iwlagn 0000:43:00.0: pci_resource_base = ffffc900110fc000
    8.267748] iwlagn 0000:43:00.0: HW Revision ID = 0x35
    8.267835] iwlagn 0000:43:00.0: irq 46 for MSI/MSI-X
    8.267876] iwlagn 0000:43:00.0: Detected Intel(R) Centrino(R) Advanced-N 6200 AGN, REV=0x74
    8.267942] iwlagn 0000:43:00.0: L1 Disabled; Enabling L0S
...
    8.278751] boot.localnet[488]: Using boot-specified hostname 'linux-07o8.site'
    8.278762] boot.localnet[488]: Setting up hostname 'linux-07o8'..done
    8.278767] boot.localnet[488]: Setting up loopback interface RTNETLINK answers: File exists
    8.278786] boot.localnet[488]: ..done
...
    8.297137] iwlagn 0000:43:00.0: device EEPROM VER=0x436, CALIB=0x6
    8.297141] iwlagn 0000:43:00.0: Device SKU: 0X1f0
    8.297165] iwlagn 0000:43:00.0: Tunable channels: 13 802.11bg, 24 802.11a channels
    8.297224] iwlagn 0000:43:00.0: RF_KILL bit toggled to disable radio.
...
    8.389093] iwlagn 0000:43:00.0: loaded firmware version 9.221.4.1 build 25532

Tailing /var/log/messages during wireless network connection shows …


Jan 29 17:49:51 linux-07o8 dhclient[5382]: 
Jan 29 17:49:51 linux-07o8 dhclient[5382]: Listening on LPF/wlan0/00:23:14:00:d4:cc
Jan 29 17:49:51 linux-07o8 dhclient[5382]: Sending on   LPF/wlan0/00:23:14:00:d4:cc
Jan 29 17:49:51 linux-07o8 dhclient[5382]: Sending on   Socket/fallback
Jan 29 17:49:51 linux-07o8 dhclient[5382]: DHCPREQUEST on wlan0 to 255.255.255.255 port 67
Jan 29 17:49:51 linux-07o8 dhclient[5382]: DHCPACK from 192.168.1.128
Jan 29 17:49:51 linux-07o8 kernel:  2194.194050] martian source 255.255.255.255 from 192.168.1.128, on dev wlan0
Jan 29 17:49:51 linux-07o8 kernel:  2194.194055] ll header: ff:ff:ff:ff:ff:ff:00:50:7f:a5:69:e8:08:00
Jan 29 17:49:51 linux-07o8 dhclient[5382]: bound to 192.168.1.26 -- renewal in 123795 seconds.
Jan 29 17:49:53 linux-07o8 avahi-daemon[1130]: Registering new address record for fe80::223:14ff:fe00:d4cc on wlan0.*.
Jan 29 17:50:02 linux-07o8 kernel:  2205.024989] wlan0: no IPv6 routers present
Jan 29 17:50:11 linux-07o8 avahi-daemon[1130]: Joining mDNS multicast group on interface wlan0.IPv4 with address 192.168.1.26.
Jan 29 17:50:11 linux-07o8 avahi-daemon[1130]: New relevant interface wlan0.IPv4 for mDNS.
Jan 29 17:50:11 linux-07o8 avahi-daemon[1130]: Registering new address record for 192.168.1.26 on wlan0.IPv4.
Jan 29 17:50:12 linux-07o8 dbus[1159]: [system] Activating service name='org.freedesktop.nm_dispatcher' (using servicehelper)
Jan 29 17:50:12 linux-07o8 dbus-daemon[1159]: dbus[1159]: [system] Activating service name='org.freedesktop.nm_dispatcher' (using servicehelper)
Jan 29 17:50:12 linux-07o8 dbus-daemon[1159]: dbus[1159]: [system] Successfully activated service 'org.freedesktop.nm_dispatcher'
Jan 29 17:50:12 linux-07o8 dbus[1159]: [system] Successfully activated service 'org.freedesktop.nm_dispatcher'
Jan 29 17:50:12 linux-07o8 dbus-daemon[1159]: /etc/rc.status: line 54: /dev/stderr: No such device or address
Jan 29 17:50:12 linux-07o8 dbus-daemon[1159]: /etc/rc.status: line 54: /dev/stderr: No such device or address
Jan 29 17:50:12 linux-07o8 SuSEfirewall2: Setting up rules from /etc/sysconfig/SuSEfirewall2 ...
Jan 29 17:50:12 linux-07o8 SuSEfirewall2: Firewall rules successfully set

ifconfig and ping shows (my router is at 192.168.1.128)…

wlan0     Link encap:Ethernet  HWaddr 00:23:14:00:D4:CC  
          inet addr:192.168.1.26  Bcast:192.168.1.255  Mask:255.255.255.0
          inet6 addr: fe80::223:14ff:fe00:d4cc/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:149 errors:0 dropped:0 overruns:0 frame:0
          TX packets:299 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          RX bytes:14961 (14.6 Kb)  TX bytes:42091 (41.1 Kb)

linux-07o8:/home/eTG # ping 192.168.1.128
PING 192.168.1.128 (192.168.1.128) 56(84) bytes of data.
^C
--- 192.168.1.128 ping statistics ---
12 packets transmitted, 0 received, 100% packet loss, time 10999ms

iwconfig shows …

lo        no wireless extensions.

wlan0     IEEE 802.11abgn  ESSID:"DavidTuxnetWAP"  
          Mode:Managed  Frequency:2.442 GHz  Access Point: 00:50:7F:A5:69:E8   
          Bit Rate=108 Mb/s   Tx-Power=15 dBm   
          Retry  long limit:7   RTS thr:off   Fragment thr:off
          Encryption key:off
          Power Management:off
          Link Quality=42/70  Signal level=-68 dBm  
          Rx invalid nwid:0  Rx invalid crypt:0  Rx invalid frag:0
          Tx excessive retries:0  Invalid misc:59   Missed beacon:0

eth0      no wireless extensions.

that seems strange. No encryption key? However, connection appears to have been established! (?)

and iwlist scan shows …

wlan0     Scan completed :
          Cell 01 - Address: 00:50:7F:A5:69:E8
                    Channel:7
                    Frequency:2.442 GHz (Channel 7)
                    Quality=41/70  Signal level=-69 dBm  
                    Encryption key:on
                    ESSID:"DavidTuxnetWAP"
                    Bit Rates:1 Mb/s; 2 Mb/s; 5.5 Mb/s; 11 Mb/s; 9 Mb/s
                              18 Mb/s; 36 Mb/s; 54 Mb/s
                    Bit Rates:6 Mb/s; 12 Mb/s; 24 Mb/s; 48 Mb/s
                    Mode:Master
                    Extra:tsf=000002ac649ed170
                    Extra: Last beacon: 26848ms ago
                    IE: Unknown: 000E44617669645475786E6574574150
                    IE: Unknown: 010882848B961224486C
                    IE: Unknown: 030107
                    IE: Unknown: 2A0100
                    IE: Unknown: 32040C183060
                    IE: Unknown: 2D1A6E1017FFFF000001000000000000000000000000000000000000
                    IE: Unknown: 3D1607070700000000000000000000000000000000000000
                    IE: Unknown: 3E0100
                    IE: WPA Version 1
                        Group Cipher : TKIP
                        Pairwise Ciphers (1) : TKIP
                        Authentication Suites (1) : PSK
                    IE: Unknown: DD180050F2020101000003A4000027A4000042435E0062322F00
                    IE: Unknown: 7F0101
                    IE: Unknown: DD07000C4300000000
                    IE: Unknown: 0706545720010D10
                    IE: Unknown: DD1E00904C336E1017FFFF000001000000000000000000000000000000000000
                    IE: Unknown: DD1A00904C3407070700000000000000000000000000000000000000
                    IE: Unknown: DD9D0050F204104A0001101044000101103B00010310470010BC329E001DD811B2860100507FA569E81021001852616C696E6B20546563686E6F6C6F67792C20436F72702E1023001C52616C696E6B20576972656C6573732041636365737320506F696E74102400065254323836301042000831323334353637381054000800060050F20400011011000952616C696E6B415053100800020084103C000100

Very strange. Any help would be appreciated!

Cheerio,
David[/size]

2

Here is route -n …

Kernel IP routing table
Destination     Gateway         Genmask         Flags Metric Ref    Use Iface
0.0.0.0         192.168.1.128   0.0.0.0         UG    0      0        0 wlan0
192.168.1.0     0.0.0.0         255.255.255.0   U     2      0        0 wlan0
3

On 01/29/2012 01:46 AM, vkelim wrote:
>
> Here is route -n …
>
>
> Code:
> --------------------
> Kernel IP routing table
> Destination Gateway Genmask Flags Metric Ref Use Iface
> 0.0.0.0 192.168.1.128 0.0.0.0 UG 0 0 0 wlan0
> 192.168.1.0 0.0.0.0 255.255.255.0 U 2 0 0 wlan0
>
> --------------------

Please try the following (in order) and report which one fails:


ping -c5 192.168.1.128
ping -c5 8.8.8.8
ping -c5 www.samba.org

My prediction is that 1 and 2 will be OK, and 3 will fail. If I’m right, that
means that your /etc/resolv.conf is wrong.

4

Thanks! Unfortunately, none of the ping -c commands worked.
They all worked after I connected an Ethernet cable!

I attached the contents of /etc/nameserver (when only the wireless was connected) as well.

David.

dfong121@linux-07o8:~> ping -c5 192.168.1.128
PING 192.168.1.128 (192.168.1.128) 56(84) bytes of data.
^C
--- 192.168.1.128 ping statistics ---
5 packets transmitted, 0 received, 100% packet loss, time 3999ms

dfong121@linux-07o8:~> ping -c5 8.8.8.8
PING 8.8.8.8 (8.8.8.8) 56(84) bytes of data.
^C
--- 8.8.8.8 ping statistics ---
5 packets transmitted, 0 received, 100% packet loss, time 3999ms

dfong121@linux-07o8:~> ping www.samba.org
^C
dfong121@linux-07o8:~> cat /etc/resolv.conf
### /etc/resolv.conf file autogenerated by netconfig!
#
...
### Please remove (at least) this line when you modify the file!
search site
nameserver 192.168.1.128
5

On 01/30/2012 02:26 AM, vkelim wrote:
>
> Thanks! Unfortunately, none of the ping -c commands worked.
> They all worked after I connected an Ethernet cable!
>
> I attached the contents of /etc/nameserver (when only the wireless was
> connected) as well.
>
> David.
>
>
> Code:
> --------------------
> dfong121@linux-07o8:~> ping -c5 192.168.1.128
> PING 192.168.1.128 (192.168.1.128) 56(84) bytes of data.
> ^C
> — 192.168.1.128 ping statistics —
> 5 packets transmitted, 0 received, 100% packet loss, time 3999ms
>
> dfong121@linux-07o8:~> ping -c5 8.8.8.8
> PING 8.8.8.8 (8.8.8.8) 56(84) bytes of data.
> ^C
> — 8.8.8.8 ping statistics —
> 5 packets transmitted, 0 received, 100% packet loss, time 3999ms
>
> dfong121@linux-07o8:~> ping www.samba.org
> ^C
> dfong121@linux-07o8:~> cat /etc/resolv.conf
> ### /etc/resolv.conf file autogenerated by netconfig!
> #
> …
> ### Please remove (at least) this line when you modify the file!
> search site
> nameserver 192.168.1.128
> --------------------
>
>
>
>
>
> lwfinger;2435229 Wrote:
>> On 01/29/2012 01:46 AM, vkelim wrote:
>>>
>>> …
>>
>> Please try the following (in order) and report which one fails:
>>
>>>
> Code:
> --------------------
> > >
> > ping -c5 192.168.1.128
> > ping -c5 8.8.8.8
> > ping -c5 www.samba.org
> >
> --------------------
>>>
>>
>> My prediction is that 1 and 2 will be OK, and 3 will fail. If I’m
>> right, that
>> means that your /etc/resolv.conf is wrong.

Although your ifconfig output made it look as if the wireless was associated and
authenticated, the failure of the first ping says it is not.

Does the dmesg output show something like:


ADDRCONF(NETDEV_UP): wlan0: link is not ready
wlan0: authenticate with c0:3f:0e:be:2b:44 (try 1)
wlan0: authenticated
wlan0: associate with c0:3f:0e:be:2b:44 (try 1)
wlan0: RX AssocResp from c0:3f:0e:be:2b:44 (capab=0x411 status=0 aid=4)
wlan0: associated
6

Thansk lwfinger!

Here is the end of my dmesg report. To my inexperienced eye, it seems okay…

   11.695916] ADDRCONF(NETDEV_UP): eth0: link is not ready
   91.545582] iwlagn 0000:43:00.0: RF_KILL bit toggled to enable radio.
   91.585887] iwlagn 0000:43:00.0: L1 Disabled; Enabling L0S
   91.592763] iwlagn 0000:43:00.0: Radio type=0x1-0x3-0x1
   91.823375] iwlagn 0000:43:00.0: L1 Disabled; Enabling L0S
   91.830284] iwlagn 0000:43:00.0: Radio type=0x1-0x3-0x1
   91.923849] ADDRCONF(NETDEV_UP): wlan0: link is not ready
   92.899800] NET: Registered protocol family 17
  100.554496] wlan0: authenticate with 00:50:7f:a5:69:e8 (try 1)
  100.556884] wlan0: authenticated
  100.599504] wlan0: associate with 00:50:7f:a5:69:e8 (try 1)
  100.603333] wlan0: RX AssocResp from 00:50:7f:a5:69:e8 (capab=0x431 status=0 aid=7)
  100.603340] wlan0: associated
  100.612582] ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
  100.612683] cfg80211: Calling CRDA for country: TW
  100.617667] cfg80211: Regulatory domain changed to country: TW
  100.617669] cfg80211:     (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp)
  100.617671] cfg80211:     (2402000 KHz - 2472000 KHz @ 40000 KHz), (300 mBi, 2700 mBm)
  100.617673] cfg80211:     (5270000 KHz - 5330000 KHz @ 40000 KHz), (300 mBi, 1700 mBm)
  100.617675] cfg80211:     (5735000 KHz - 5815000 KHz @ 40000 KHz), (300 mBi, 3000 mBm)
  101.093581] martian source 255.255.255.255 from 192.168.1.128, on dev wlan0
  101.093586] ll header: ff:ff:ff:ff:ff:ff:00:50:7f:a5:69:e8:08:00
  111.429560] wlan0: no IPv6 routers present
7

On 02/01/2012 09:16 PM, vkelim wrote:
>
> Thansk lwfinger!
>
> Here is the end of my dmesg report. To my inexperienced eye, it seems
> okay…
>
>
> Code:
> --------------------
> 11.695916] ADDRCONF(NETDEV_UP): eth0: link is not ready
> 91.545582] iwlagn 0000:43:00.0: RF_KILL bit toggled to enable radio.
> 91.585887] iwlagn 0000:43:00.0: L1 Disabled; Enabling L0S
> 91.592763] iwlagn 0000:43:00.0: Radio type=0x1-0x3-0x1
> 91.823375] iwlagn 0000:43:00.0: L1 Disabled; Enabling L0S
> 91.830284] iwlagn 0000:43:00.0: Radio type=0x1-0x3-0x1
> 91.923849] ADDRCONF(NETDEV_UP): wlan0: link is not ready
> 92.899800] NET: Registered protocol family 17
> 100.554496] wlan0: authenticate with 00:50:7f:a5:69:e8 (try 1)
> 100.556884] wlan0: authenticated
> 100.599504] wlan0: associate with 00:50:7f:a5:69:e8 (try 1)
> 100.603333] wlan0: RX AssocResp from 00:50:7f:a5:69:e8 (capab=0x431 status=0 aid=7)
> 100.603340] wlan0: associated
> 100.612582] ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
> 100.612683] cfg80211: Calling CRDA for country: TW
> 100.617667] cfg80211: Regulatory domain changed to country: TW
> 100.617669] cfg80211: (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp)
> 100.617671] cfg80211: (2402000 KHz - 2472000 KHz @ 40000 KHz), (300 mBi, 2700 mBm)
> 100.617673] cfg80211: (5270000 KHz - 5330000 KHz @ 40000 KHz), (300 mBi, 1700 mBm)
> 100.617675] cfg80211: (5735000 KHz - 5815000 KHz @ 40000 KHz), (300 mBi, 3000 mBm)
> 101.093581] martian source 255.255.255.255 from 192.168.1.128, on dev wlan0
> 101.093586] ll header: ff:ff:ff:ff:ff:ff:00:50:7f:a5:69:e8:08:00
> 111.429560] wlan0: no IPv6 routers present

Except for the martian source line, it looks OK. That dropped packet came from
your router - I have no idea why you get that. It should be OK.

8

(sorry to resurrect an ‘old thread’, but I have done more diagnostics, and hope it is more helpful)

My HP 2740p is successfully able to send a ping to another computer through wireless, and that other computer sends
a ping response back. However, the 2740p doesn’t ‘receive’ the response.

In this wireshark capture, my 2740p is 192.168.1.27, the other computer is 192.168.1.28 (also on wireless).

No.     Time        Source                Destination           Protocol Length Info
      1 0.000000    192.168.1.27          192.168.1.28          ICMP     98     Echo (ping) request  id=0x0de0, seq=18/4608, ttl=64

Frame 1: 98 bytes on wire (784 bits), 98 bytes captured (784 bits)
Ethernet II, Src: IntelCor_00:d4:cc (00:23:14:00:d4:cc), Dst: HonHaiPr_54:f4:62 (00:25:56:54:f4:62)
Internet Protocol Version 4, Src: 192.168.1.27 (192.168.1.27), Dst: 192.168.1.28 (192.168.1.28)
Internet Control Message Protocol

No.     Time        Source                Destination           Protocol Length Info
      2 0.000058    192.168.1.28          192.168.1.27          ICMP     98     Echo (ping) reply    id=0x0de0, seq=18/4608, ttl=64

Frame 2: 98 bytes on wire (784 bits), 98 bytes captured (784 bits)
Ethernet II, Src: HonHaiPr_54:f4:62 (00:25:56:54:f4:62), Dst: IntelCor_00:d4:cc (00:23:14:00:d4:cc)
Internet Protocol Version 4, Src: 192.168.1.28 (192.168.1.28), Dst: 192.168.1.27 (192.168.1.27)
Internet Control Message Protocol

No.     Time        Source                Destination           Protocol Length Info
      3 0.998152    192.168.1.27          192.168.1.28          ICMP     98     Echo (ping) request  id=0x0de0, seq=19/4864, ttl=64

Frame 3: 98 bytes on wire (784 bits), 98 bytes captured (784 bits)
Ethernet II, Src: IntelCor_00:d4:cc (00:23:14:00:d4:cc), Dst: HonHaiPr_54:f4:62 (00:25:56:54:f4:62)
Internet Protocol Version 4, Src: 192.168.1.27 (192.168.1.27), Dst: 192.168.1.28 (192.168.1.28)
Internet Control Message Protocol

No.     Time        Source                Destination           Protocol Length Info
      4 0.998214    192.168.1.28          192.168.1.27          ICMP     98     Echo (ping) reply    id=0x0de0, seq=19/4864, ttl=64

Frame 4: 98 bytes on wire (784 bits), 98 bytes captured (784 bits)
Ethernet II, Src: HonHaiPr_54:f4:62 (00:25:56:54:f4:62), Dst: IntelCor_00:d4:cc (00:23:14:00:d4:cc)
Internet Protocol Version 4, Src: 192.168.1.28 (192.168.1.28), Dst: 192.168.1.27 (192.168.1.27)
Internet Control Message Protocol

My HP 2740p sends the pings, but doesn’t take them back. The wireshark capture shows that the HP (192.168.1.27)
enquiring as to who has 192.168.1.28, and vice versa. Both computers respond to that enquiry. Also the HP (192.168.1.27)
responds to a ‘who has’ enquiry from the router (192.168.1.128)

Turning off the firewall on the HP 2740p doesn’t make any difference.
Any suggestions would be welcome!

No.     Time        Source                Destination           Protocol Length Info
      7 3.999802    192.168.1.27          192.168.1.28          ICMP     98     Echo (ping) request  id=0x0e89, seq=5/1280, ttl=64

Frame 7: 98 bytes on wire (784 bits), 98 bytes captured (784 bits)
Ethernet II, Src: IntelCor_00:d4:cc (00:23:14:00:d4:cc), Dst: HonHaiPr_54:f4:62 (00:25:56:54:f4:62)
Internet Protocol Version 4, Src: 192.168.1.27 (192.168.1.27), Dst: 192.168.1.28 (192.168.1.28)
Internet Control Message Protocol

No.     Time        Source                Destination           Protocol Length Info
      8 4.999805    192.168.1.27          192.168.1.28          ICMP     98     Echo (ping) request  id=0x0e89, seq=6/1536, ttl=64

Frame 8: 98 bytes on wire (784 bits), 98 bytes captured (784 bits)
Ethernet II, Src: IntelCor_00:d4:cc (00:23:14:00:d4:cc), Dst: HonHaiPr_54:f4:62 (00:25:56:54:f4:62)
Internet Protocol Version 4, Src: 192.168.1.27 (192.168.1.27), Dst: 192.168.1.28 (192.168.1.28)
Internet Control Message Protocol

No.     Time        Source                Destination           Protocol Length Info
      9 5.014742    IntelCor_00:d4:cc     HonHaiPr_54:f4:62     ARP      42     Who has 192.168.1.28?  Tell 192.168.1.27

Frame 9: 42 bytes on wire (336 bits), 42 bytes captured (336 bits)
Ethernet II, Src: IntelCor_00:d4:cc (00:23:14:00:d4:cc), Dst: HonHaiPr_54:f4:62 (00:25:56:54:f4:62)
Address Resolution Protocol (request)

No.     Time        Source                Destination           Protocol Length Info
     10 5.017577    HonHaiPr_54:f4:62     IntelCor_00:d4:cc     ARP      42     Who has 192.168.1.27?  Tell 192.168.1.28

Frame 10: 42 bytes on wire (336 bits), 42 bytes captured (336 bits)
Ethernet II, Src: HonHaiPr_54:f4:62 (00:25:56:54:f4:62), Dst: IntelCor_00:d4:cc (00:23:14:00:d4:cc)
Address Resolution Protocol (request)

No.     Time        Source                Destination           Protocol Length Info
     11 5.017592    IntelCor_00:d4:cc     HonHaiPr_54:f4:62     ARP      42     192.168.1.27 is at 00:23:14:00:d4:cc

Frame 11: 42 bytes on wire (336 bits), 42 bytes captured (336 bits)
Ethernet II, Src: IntelCor_00:d4:cc (00:23:14:00:d4:cc), Dst: HonHaiPr_54:f4:62 (00:25:56:54:f4:62)
Address Resolution Protocol (reply)

No.     Time        Source                Destination           Protocol Length Info
     12 5.022276    HonHaiPr_54:f4:62     IntelCor_00:d4:cc     ARP      42     192.168.1.28 is at 00:25:56:54:f4:62

Frame 12: 42 bytes on wire (336 bits), 42 bytes captured (336 bits)
Ethernet II, Src: HonHaiPr_54:f4:62 (00:25:56:54:f4:62), Dst: IntelCor_00:d4:cc (00:23:14:00:d4:cc)
Address Resolution Protocol (reply)

No.     Time        Source                Destination           Protocol Length Info
     13 5.745892    Draytek_a5:69:e8      Broadcast             ARP      42     Who has 192.168.1.27?  Tell 192.168.1.128

Frame 13: 42 bytes on wire (336 bits), 42 bytes captured (336 bits)
Ethernet II, Src: Draytek_a5:69:e8 (00:50:7f:a5:69:e8), Dst: Broadcast (ff:ff:ff:ff:ff:ff)
Address Resolution Protocol (request)

No.     Time        Source                Destination           Protocol Length Info
     14 5.745920    IntelCor_00:d4:cc     Draytek_a5:69:e8      ARP      42     192.168.1.27 is at 00:23:14:00:d4:cc

Frame 14: 42 bytes on wire (336 bits), 42 bytes captured (336 bits)
Ethernet II, Src: IntelCor_00:d4:cc (00:23:14:00:d4:cc), Dst: Draytek_a5:69:e8 (00:50:7f:a5:69:e8)
Address Resolution Protocol (reply)

No.     Time        Source                Destination           Protocol Length Info
     15 5.999771    192.168.1.27          192.168.1.28          ICMP     98     Echo (ping) request  id=0x0e89, seq=7/1792, ttl=64

Frame 15: 98 bytes on wire (784 bits), 98 bytes captured (784 bits)
Ethernet II, Src: IntelCor_00:d4:cc (00:23:14:00:d4:cc), Dst: HonHaiPr_54:f4:62 (00:25:56:54:f4:62)
Internet Protocol Version 4, Src: 192.168.1.27 (192.168.1.27), Dst: 192.168.1.28 (192.168.1.28)
Internet Control Message Protocol

No.     Time        Source                Destination           Protocol Length Info
     16 6.999761    192.168.1.27          192.168.1.28          ICMP     98     Echo (ping) request  id=0x0e89, seq=8/2048, ttl=64

Frame 16: 98 bytes on wire (784 bits), 98 bytes captured (784 bits)
Ethernet II, Src: IntelCor_00:d4:cc (00:23:14:00:d4:cc), Dst: HonHaiPr_54:f4:62 (00:25:56:54:f4:62)
Internet Protocol Version 4, Src: 192.168.1.27 (192.168.1.27), Dst: 192.168.1.28 (192.168.1.28)
Internet Control Message Protocol
9

Every indication is that your hardware is functioning. If that were not true,
you would not be able to get pings on the air, and the ARP exchanges would fail.
In addition, you would never get the IP assigned.

I think the problem is higher up the network stack. Perhaps it is in mac80211.
That false “encryption key off” reading suddenly seems more important.

Please try the compat-wireless package for your kernel. You will need to enable
the http://download.opensuse.org/repositories/driver:/wireless/openSUSE_12.1
repo. That will replace the entire wireless code, including the driver. In
addition, do a reload of the kernel-firmware package just in case you have a
faulty firmware file. Such a problem could mess up encryption/decryption.

10

Thanks lwfinger.

For my Intel Corporation Centrino Advanced-N 6200 and desktop-kernel I installed compat-wireless-kmp-desktop, compat-wireless-scripts, iw (upgrade), and iwl6000-ucode (which replaced a kernel-microcode package).

Everything looked initially better, perhaps my imagination that the scan showed a lot more wireless networks being available, but unfortunately the ping to my router (or other machines in my local network) still didn’t work and the “encryption key off” message was still there. When I have a few more hours to spare, I’ll try to disable the encryption on the router, temporarily…

11

First stating that lwfinger knows the world more about networking than I do, but could ipV6 play a role here? Is it enabled in Yast? What happens if you disable ipV6, reboot en create a new connection?

12

On 03/19/2012 08:16 AM, Knurpht wrote:
>
> First stating that lwfinger knows the world more about networking than I
> do, but could ipV6 play a role here? Is it enabled in Yast? What happens
> if you disable ipV6, reboot en create a new connection?

No, IPv6 could not cause a problem with pinging. For starters, the ICMP protocol
uses UDP, not TCP, and it occurs at a much lower level that DNS. Do not bother
doing this.

13

I am having the exact same problem on a Lenovo T410 with the Intel Centrino Advanced-N 6200 right down to the Encryption showing off (and it should be WPA). I get an IP with hardwire, I get an IP with wireless. What I noticed different is when on wireless, I CAN ping a printer and also view that printers web page (at 192.168.1.55) but not the router at 192.168.1.1. I cannot get to any other web pages or ping anything else external (of course). I also checked the router and it shows an entry for the wireless at 192.168.1.104 (192.168.1.105 is the hardwire). This is very odd -

linux-jap0:~ # ifdown eth0
eth0 device: Intel Corporation 82577LM Gigabit Network Connection (rev 06)
linux-jap0:~ # ping 192.168.1.55
PING 192.168.1.55 (192.168.1.55) 56(84) bytes of data.
64 bytes from 192.168.1.55: icmp_seq=1 ttl=255 time=33.6 ms
64 bytes from 192.168.1.55: icmp_seq=3 ttl=255 time=5.33 ms
64 bytes from 192.168.1.55: icmp_seq=4 ttl=255 time=4.79 ms
64 bytes from 192.168.1.55: icmp_seq=5 ttl=255 time=2.60 ms
64 bytes from 192.168.1.55: icmp_seq=6 ttl=255 time=2.53 ms
64 bytes from 192.168.1.55: icmp_seq=7 ttl=255 time=2.49 ms
64 bytes from 192.168.1.55: icmp_seq=8 ttl=255 time=2.53 ms
^C
— 192.168.1.55 ping statistics —
8 packets transmitted, 7 received, 12% packet loss, time 7008ms
rtt min/avg/max/mdev = 2.497/7.703/33.618/10.638 ms

linux-jap0:~ # ifconfig
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:3423 errors:0 dropped:0 overruns:0 frame:0
TX packets:3423 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:340583 (332.6 Kb) TX bytes:340583 (332.6 Kb)

wlan0 Link encap:Ethernet HWaddr DELETED BY ME
inet addr:192.168.1.104 Bcast:192.168.1.255 Mask:255.255.255.0
inet6 addr:DELETED BY ME Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:1105 errors:0 dropped:0 overruns:0 frame:0
TX packets:1065 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:295694 (288.7 Kb) TX bytes:92140 (89.9 Kb)

linux-jap0:~ # ping 192.168.1.1
PING 192.168.1.1 (192.168.1.1) 56(84) bytes of data.
^C
— 192.168.1.1 ping statistics —
5 packets transmitted, 0 received, 100% packet loss, time 3999ms

It eventually says destination host unreachable.

Has their been a driver update or anything else to try?

14

I am actually posting this through the Intel Centrino Advanced-D 6200. I disabled WPA in my router. Went to Yast and took off WPA-PSK (set to no encryption). i am not real versed in Linux so Yast seemed the easy route. I stopped eth0 ifdown eth0. This stopped all the interfaces (not the loopback though), including wlan0. I restarted wlan0 ifup wlan0 and everything works. I cannot run unencrypted so I will need to set this back, but at least that narrows down the problem. If anyone comes up with a solution it would be greatly appreciated! I have to be able to use encryption to keep this OS on the laptop.

15

On 05/03/2012 12:06 PM, mikesopensuse wrote:
>
> I am having the exact same problem on a Lenovo T410 with the Intel
> Centrino Advanced-N 6200 right down to the Encryption showing off (and
> it should be WPA). I get an IP with hardwire, I get an IP with
> wireless. What I noticed different is when on wireless, I CAN ping a
> printer and also view that printers web page (at 192.168.1.55) but not
> the router at 192.168.1.1. I cannot get to any other web pages or ping
> anything else external (of course). I also checked the router and it
> shows an entry for the wireless at 192.168.1.104 (192.168.1.105 is the
> hardwire). This is very odd -
>
> linux-jap0:~ # ifdown eth0
> eth0 device: Intel Corporation 82577LM Gigabit Network
> Connection (rev 06)
> linux-jap0:~ # ping 192.168.1.55
> PING 192.168.1.55 (192.168.1.55) 56(84) bytes of data.
> 64 bytes from 192.168.1.55: icmp_seq=1 ttl=255 time=33.6 ms
> 64 bytes from 192.168.1.55: icmp_seq=3 ttl=255 time=5.33 ms
> 64 bytes from 192.168.1.55: icmp_seq=4 ttl=255 time=4.79 ms
> 64 bytes from 192.168.1.55: icmp_seq=5 ttl=255 time=2.60 ms
> 64 bytes from 192.168.1.55: icmp_seq=6 ttl=255 time=2.53 ms
> 64 bytes from 192.168.1.55: icmp_seq=7 ttl=255 time=2.49 ms
> 64 bytes from 192.168.1.55: icmp_seq=8 ttl=255 time=2.53 ms
> ^C
> — 192.168.1.55 ping statistics —
> 8 packets transmitted, 7 received, 12% packet loss, time 7008ms
> rtt min/avg/max/mdev = 2.497/7.703/33.618/10.638 ms
>
> linux-jap0:~ # ifconfig
> 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:3423 errors:0 dropped:0 overruns:0 frame:0
> TX packets:3423 errors:0 dropped:0 overruns:0 carrier:0
> collisions:0 txqueuelen:0
> RX bytes:340583 (332.6 Kb) TX bytes:340583 (332.6 Kb)
>
> wlan0 Link encap:Ethernet HWaddr DELETED BY ME
> inet addr:192.168.1.104 Bcast:192.168.1.255
> Mask:255.255.255.0
> inet6 addr:DELETED BY ME Scope:Link
> UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
> RX packets:1105 errors:0 dropped:0 overruns:0 frame:0
> TX packets:1065 errors:0 dropped:0 overruns:0 carrier:0
> collisions:0 txqueuelen:1000
> RX bytes:295694 (288.7 Kb) TX bytes:92140 (89.9 Kb)
>
> linux-jap0:~ # ping 192.168.1.1
> PING 192.168.1.1 (192.168.1.1) 56(84) bytes of data.
> ^C
> — 192.168.1.1 ping statistics —
> 5 packets transmitted, 0 received, 100% packet loss, time 3999ms
>
> It eventually says destination host unreachable.
>
> Has their been a driver update or anything else to try?

What does ‘/sbin/route -n’ show? This type of problem is generally one of
routing. AFAIK, no recent updates will change this.

16

On 05/03/2012 12:16 PM, mikesopensuse wrote:
>
> I am actually posting this through the Intel Centrino Advanced-D 6200.
> I disabled WPA in my router. Went to Yast and took off WPA-PSK (set to
> no encryption). i am not real versed in Linux so Yast seemed the easy
> route. I stopped eth0 ifdown eth0. This stopped all the interfaces
> (not the loopback though), including wlan0. I restarted wlan0 ifup
> wlan0 and everything works. I cannot run unencrypted so I will need to
> set this back, but at least that narrows down the problem. If anyone
> comes up with a solution it would be greatly appreciated! I have to be
> able to use encryption to keep this OS on the laptop.

If it runs unencrypted, then the problem is in the ifup configuration. Please
check /etc/sysconfig/network/ifcfg-wlan0 after you re-enable the encryption. The
problem is likely there.

17

Does this look right -

BOOTPROTO=‘dhcp4’
BROADCAST=’’
ETHTOOL_OPTIONS=’’
IPADDR=’’
MTU=’’
NAME=‘Intel WLAN controller’
NETMASK=’’
NETWORK=’’
REMOTE_IPADDR=’’
STARTMODE=‘auto’
USERCONTROL=‘yes’
WIRELESS_AP=’’
WIRELESS_AP_SCANMODE=‘1’
WIRELESS_AUTH_MODE=‘psk’
WIRELESS_BITRATE=‘auto’
WIRELESS_CA_CERT=’’
WIRELESS_CHANNEL=’’
WIRELESS_CLIENT_CERT=’’
WIRELESS_CLIENT_KEY=’’
WIRELESS_CLIENT_KEY_PASSWORD=’’
WIRELESS_DEFAULT_KEY=‘0’
WIRELESS_EAP_AUTH=’’
WIRELESS_EAP_MODE=’’
WIRELESS_ESSID=‘MikesLink’
WIRELESS_FREQUENCY=’’
WIRELESS_KEY=’’
WIRELESS_KEY_0=’’
WIRELESS_KEY_1=’’
WIRELESS_KEY_2=’’
WIRELESS_KEY_3=’’
WIRELESS_KEY_LENGTH=‘128’
WIRELESS_MODE=‘Managed’
WIRELESS_NICK=’’
WIRELESS_NWID=’’
WIRELESS_PEAP_VERSION=’’
WIRELESS_POWER=‘no’
“ifcfg-wlan0” 40L, 812C 10,1 Top

18

the address for the wlan0 is 192.168.1.104

Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
0.0.0.0 192.168.1.1 0.0.0.0 UG 0 0 0 wlan0
127.0.0.0 0.0.0.0 255.0.0.0 U 0 0 0 lo
169.254.0.0 0.0.0.0 255.255.0.0 U 0 0 0 wlan0
192.168.1.0 0.0.0.0 255.255.255.0 U 0 0 0 wlan0

19

On 05/04/2012 03:06 PM, mikesopensuse wrote:
>
> Does this look right -
>
> BOOTPROTO=‘dhcp4’
> BROADCAST=’’
> ETHTOOL_OPTIONS=’’
> IPADDR=’’
> MTU=’’
> NAME=‘Intel WLAN controller’
> NETMASK=’’
> NETWORK=’’
> REMOTE_IPADDR=’’
> STARTMODE=‘auto’
> USERCONTROL=‘yes’
> WIRELESS_AP=’’
> WIRELESS_AP_SCANMODE=‘1’
> WIRELESS_AUTH_MODE=‘psk’
> WIRELESS_BITRATE=‘auto’
> WIRELESS_CA_CERT=’’
> WIRELESS_CHANNEL=’’
> WIRELESS_CLIENT_CERT=’’
> WIRELESS_CLIENT_KEY=’’
> WIRELESS_CLIENT_KEY_PASSWORD=’’
> WIRELESS_DEFAULT_KEY=‘0’
> WIRELESS_EAP_AUTH=’’
> WIRELESS_EAP_MODE=’’
> WIRELESS_ESSID=‘MikesLink’
> WIRELESS_FREQUENCY=’’
> WIRELESS_KEY=’’
> WIRELESS_KEY_0=’’
> WIRELESS_KEY_1=’’
> WIRELESS_KEY_2=’’
> WIRELESS_KEY_3=’’
> WIRELESS_KEY_LENGTH=‘128’
> WIRELESS_MODE=‘Managed’
> WIRELESS_NICK=’’
> WIRELESS_NWID=’’
> WIRELESS_PEAP_VERSION=’’
> WIRELESS_POWER=‘no’
> “ifcfg-wlan0” 40L, 812C 10,1
> Top

No. You did not put in a WPA secret in a ‘WIRELESS_WPA_PSK=xjxjxjxjxjx’ line.

A minor point - WIRELESS_POWER=‘no’ should be OK, but 12.1 likes ‘none’ better.
That is a bug.

20

Do I just add that line WIRELESS_WPA_PSK=xjxjxjxjxjx to ifcfg-wlan0? If so is xjxjxjxjxjx my WPA passphrase or is that in HEX or is it something else?