[netctl] dhcp running but no connection [solved]

orschiro · 2014-05-09 11:40:24

I encounter the issue that I cannot establish any connection to the internet although my netctl service is successfully running and dhcp was successfully forked to background. I tested Thunderbird, Chromium, Firefox, all of them cannot establish any connection.

I already tried switching between dhcpcd and dhclient but the issue occurs with both of them. I never encountered this issue before. Does anyone have an idea what could cause it?

Thanks!

~ systemctl status netctl-auto@wls1.service -l
● netctl-auto@wls1.service - Automatic wireless network connection using netctl profiles
   Loaded: loaded (/usr/lib/systemd/system/netctl-auto@.service; enabled)
   Active: active (running) since Fr 2014-05-09 11:19:31 CEST; 1min 58s ago
     Docs: man:netctl.special(7)
  Process: 439 ExecStart=/usr/bin/netctl-auto start %I (code=exited, status=0/SUCCESS)
   CGroup: /system.slice/system-netctl\x2dauto.slice/netctl-auto@wls1.service
           ├─ 596 wpa_supplicant -B -P /run/wpa_supplicant_wls1.pid -i wls1 -D nl80211,wext -c/run/network/wpa_supplicant_wls1.conf -W
           ├─ 599 wpa_actiond -p /run/wpa_supplicant -i wls1 -P /run/network/wpa_actiond_wls1.pid -a /usr/lib/network/auto.action
           └─1274 dhcpcd -4qL -t 30 -K wls1

Mai 09 11:19:31 thinkpad wpa_actiond[599]: Starting wpa_actiond session for interface 'wls1'
Mai 09 11:19:36 thinkpad wpa_actiond[599]: Interface 'wls1' connected to network 'ThomsonE6490C'
Mai 09 11:19:36 thinkpad dhcpcd[1148]: version 6.3.2 starting
Mai 09 11:19:38 thinkpad dhcpcd[1148]: DUID 00:01:00:01:1a:93:69:fe:00:16:ea:ef:90:62
Mai 09 11:19:38 thinkpad dhcpcd[1148]: wls1: IAID ea:ef:90:62
Mai 09 11:19:38 thinkpad dhcpcd[1148]: wls1: rebinding lease of 192.168.2.40
Mai 09 11:19:43 thinkpad dhcpcd[1148]: wls1: leased 192.168.2.40 for 86400 seconds
Mai 09 11:19:43 thinkpad dhcpcd[1148]: wls1: adding route to 192.168.2.0/24
Mai 09 11:19:43 thinkpad dhcpcd[1148]: wls1: adding default route via 192.168.2.254
Mai 09 11:19:43 thinkpad dhcpcd[1148]: forked to background, child pid 1274

Last edited by orschiro (2014-05-11 11:38:34)

ayekat · 2014-05-09 13:57:01

I assume you have got a valid IP address from the router/access point (check with ifconfig or ip addr).

Have you tested whether the DNS you are using is working correctly? Try pinging 8.8.8.8 or something else by IP address. If you get a response, you can try to change the nameserver in /etc/resolv.conf and see if this solves your problem:

# /etc/resolv.conf
nameserver 8.8.8.8

Otherwise you can try to traceroute to a destination (preferably by IP address, to make sure the above won't interfere), and see at which point your packets stop/are getting dropped.

Haven't used netctl much, can't tell you what else could be the problem.

Last edited by ayekat (2014-05-09 13:59:56)

HiImTye · 2014-05-09 15:45:00

dig google.com

to see if it's a dns problem

orschiro · 2014-05-09 16:37:23

I very much appreciate your replies! This is a weird issue. I am using the Google nameservers but also dig leads to a connection timeout.

~ dig google.com
; <<>> DiG 9.9.2-P2 <<>> google.com
;; global options: +cmd
;; connection timed out; no servers could be reached

~ ip addr
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default 
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 scope host lo
       valid_lft forever preferred_lft forever
    inet6 ::1/128 scope host 
       valid_lft forever preferred_lft forever
2: wls1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 1000
    link/ether 00:16:ea:ef:90:62 brd ff:ff:ff:ff:ff:ff
    inet 145.107.100.32/23 brd 145.107.101.255 scope global wls1
       valid_lft forever preferred_lft forever
    inet6 fe80::216:eaff:feef:9062/64 scope link 
       valid_lft forever preferred_lft forever

~ cat /etc/resolv.conf   
# Google nameservers
nameserver 8.8.8.8
nameserver 8.8.4.4

However, for some reasons pinging the Google nameserver works:

~ ping 8.8.8.8
PING 8.8.8.8 (8.8.8.8) 56(84) bytes of data.
64 bytes from 8.8.8.8: icmp_seq=1 ttl=50 time=9.91 ms
64 bytes from 8.8.8.8: icmp_seq=2 ttl=51 time=9.77 ms
64 bytes from 8.8.8.8: icmp_seq=3 ttl=51 time=10.0 ms

EDIT:

Even more strange, running pacman -Syu from the command line works but no other program can establish a connection.

Last edited by orschiro (2014-05-09 17:05:20)

orschiro · 2014-05-10 05:01:51

Why can I run a pacman update, but get a dig, Firefox, Thunderbird, Chromium connection timeout?

What does pacman do differently in that respect?

I just booted from a live disk because I suspected my wifi hardware to be damaged. But I am writing in Chromium now, meaning that on a live disk everything is working.

Furthermore, I downgraded linux, dhclient, netctl, linux-headers but no success.

Thus not a package issue?

orschiro · 2014-05-11 11:40:36

What the hell? For some reasons access rights to /etc/resolv.conf were suddenly set to 600 instead of 644.

I changed them back to 644 and now I can establish a connection as normal user.

That also explains why pacman -Syu did still perform because it is running as root.

Arch Linux

#1 2014-05-09 11:40:24

[netctl] dhcp running but no connection [solved]

#2 2014-05-09 13:57:01

Re: [netctl] dhcp running but no connection [solved]

#3 2014-05-09 15:45:00

Re: [netctl] dhcp running but no connection [solved]

#4 2014-05-09 16:37:23

Re: [netctl] dhcp running but no connection [solved]

#5 2014-05-10 05:01:51

Re: [netctl] dhcp running but no connection [solved]

#6 2014-05-11 11:40:36

Re: [netctl] dhcp running but no connection [solved]

Board footer