No connection after dhcpcd success

edriv · 2014-02-20 17:06:28

Hi all,
today my internet connection does not work even if the router is set up correctly.
I have my laptop connected using dhcpcd with the following commands:

# wpa_supplicant
# dhcpcd wlan0
dhcpcd: wlan0: version 5.6.8 starting
dhcpcd: wlan0: waiting for carrier
dhcpcd: wlan0: carrier acquired
dhcpcd: wlan0: sending IPv6 router solicitation
dhcpcd: wlan0: sendmsg: cannot assign requested address
dhcpcd: wlan0: broadcasting for a lease
dhcpcd: wlan0: offered 192.168.1.12 from 192.168.1.1
dhcpcd: wlan0: acknowledged 192.168.1.12 from 192.168.1.1
dhcpcd: wlan0: checking 192.168.1.12
dhcpcd: wlan0: sending IPv6 router solicitation
dhcpcd: wlan0: leased 192.168.1.12 for 16200 seconds
dhcpcd: forked to background, PID 6892

However I am not able to surf the web, and what's more surprising, even ping 192.168.1.1 does not work.
I suspect there is a DNS problem but I don't know..

ewaller · 2014-02-20 17:23:55

edriv wrote:

However I am not able to surf the web, and what's more surprising, even ping 192.168.1.1 does not work.
I suspect there is a DNS problem but I don't know..

If you cannot ping 192.168.1.1, it is not a DNS issue. As a sanity check, verify that you can ping 127.0.0.1 and 192.168.1.12. One of those, of course. is localhost. The other is the address that had been assigned to your machine.

Is this wired or wireless?
What is the output of route ?

edriv · 2014-02-20 17:45:38

I tried the two ping command and only localhost is successful.

The output of route:

$ routel
target            gateway          source    proto    scope    dev tbl
      
127.0.0.0	broadcast	127.0.0.1	kernel		link		lo local
     
127.0.0.0/ 8	local		127.0.0.1	kernel		host		lo local
      
127.0.0.1	local		127.0.0.1	kernel		host		lo local

127.255.255.255	broadcast       127.0.0.1	kernel		link		lo local
            
::1             local		kernel		lo 
        
fe80::/ 64			kernel           wlan0 
        
default		unreachable	kernel              lo unspec
            
::1		local				none              lo local

fe80::4a5d:60ff:fe60:d4f4 local			none              lo local
        
ff00::/ 8                                                     wlan0 local
        
default        unreachable      		kernel              	lo unspec

ewaller · 2014-02-20 17:56:37

And, of course, this is wireless. Stupid question

That route output is hideous.
Sane route output look like this

ewaller$@$odin ~ 1019 %route
Kernel IP routing table
Destination     Gateway         Genmask         Flags Metric Ref    Use Iface
default         ewaller         0.0.0.0         UG    303    0        0 wlan0
192.168.1.0     *               255.255.255.0   U     303    0        0 wlan0
ewaller$@$odin ~ 1020 %

It looks like all of the routing information outside your box is IPv6.
Lets try disabling IPv6

edriv · 2014-02-20 18:09:00

Now I have gathered more information; since I was running wpa_supplicant from a script, I could not see the following output: (maybe was written to stderr?)

# wpa_supplicant -iwlan0 -c/etc/wpa_supplicant.conf
Successfully initialized wpa_supplicant
wlan0: Failed to initiate AP scan
wlan0: Trying to associate with 58:98:35:5e:e7:1b (SSID='Inetlink-90105627' freq=2412 MHz)
wlan0: Associated with 58:98:35:5e:e7:1b
wlan0: WPA: Invalid EAPOL-Key MIC when using TPTK - ignoring TPTK
wlan0: WPA: Could not verify EAPOL-Key MIC - dropping packet
wlan0: WPA: Invalid EAPOL-Key MIC when using TPTK - ignoring TPTK
wlan0: WPA: Could not verify EAPOL-Key MIC - dropping packet
wlan0: WPA: Invalid EAPOL-Key MIC when using TPTK - ignoring TPTK
wlan0: WPA: Could not verify EAPOL-Key MIC - dropping packet
wlan0: WPA: Invalid EAPOL-Key MIC when using TPTK - ignoring TPTK
wlan0: WPA: Could not verify EAPOL-Key MIC - dropping packet
wlan0: CTRL-EVENT-DISCONNECTED bssid=58:98:35:5e:e7:1b reason=0
wlan0: WPA: 4-Way Handshake failed - pre-shared key may be incorrect
wlan0: CTRL-EVENT-SSID-TEMP-DISABLED id=0 ssid="Inetlink-90105627" auth_failures=1 duration=10
wlan0: Failed to initiate AP scan
wlan0: CTRL-EVENT-TERMINATING

actually the output never stops.
It seems there is something going wrong with the wireless, but is it Router-side or client-side?

ewaller · 2014-02-21 04:52:57

Brutal day, sorry.

I am puzzled as to why dhcpcd would come up with an address if there were something fundamentally wrong with the link. You say you are running wpa_supplicant from a script. You may want to share that script. Also, when you ran wpa_supplicant by hand, were there any other things "helping"? Things like netctl, or wicd?

When you thought the wifi was ready to go, what was the output of ip link and of ip addr ??
Also, I guess I should ask for the output of lspci -nn

Did you try disabling IPv6?

Arch Linux

#1 2014-02-20 17:06:28

No connection after dhcpcd success

#2 2014-02-20 17:23:55

Re: No connection after dhcpcd success

#3 2014-02-20 17:45:38

Re: No connection after dhcpcd success

#4 2014-02-20 17:56:37

Re: No connection after dhcpcd success

#5 2014-02-20 18:09:00

Re: No connection after dhcpcd success

#6 2014-02-21 04:52:57

Re: No connection after dhcpcd success

Board footer