[SOLVED] Wired conn. failing at install despite working via ArchBang

Michael Gruenstaeudl · 2015-07-09 21:01:16

I am trying set up a fresh ArchLinux system in a university network. Available to me is a new(ish) PC with two network cards, but no wireless device. To obtain all pertinent network addresses (the IP address, the broadcast address, the default gateway, and the DNS addresses), I had booted via an ArchBang LiveCD and recorded the settings from NetworkManager. I then booted via a fresh ArchLinux installation disk.

Pinging does not work out of the box, so I am following the ArchWiki for setting up a wired connection via a static IP address. Upon manually assigning the static IP address and the broadcast address, and adding the gateway IP address, the interface does display said addresses via command ip a . Pinging remains unsuccessful, however.

Adding the addresses via configuring /etc/dhcpcd.conf and restarting the dhcpcd.service does not get me wired internet access either. Nor does writing a netctl configuration file and starting the connection via netctl .

What are your suggestions to troubleshoot this connection?

Last edited by Michael Gruenstaeudl (2015-08-31 12:58:41)

Head_on_a_Stick · 2015-07-09 21:06:33

Michael Gruenstaeudl wrote:

Adding the addresses via configuring /etc/dhcpcd.conf and restarting the dhcpcd.service does not get me wired internet access either.

Have you tried removing the addresses from dhcpcd.conf and just running:

# systemctl start dhcpcd.service

Also, if you assign IPs statically without a dhcp client you will have to edit /etc/resolv.conf and add some nameservers.

# /etc/resolv.conf
nameserver 8.8.8.8
nameserver 8.8.4.4

EDIT: Be sure to post exact comands, exact terminal output, exact configuration files and exact error messages rather than just paraphrasing everything.

Last edited by Head_on_a_Stick (2015-07-09 21:10:22)

Michael Gruenstaeudl · 2015-07-09 21:46:33

Thank you for your reply.

Neither suggestion produced a successful wired connection. I am listing the log output for both of the points you brought up.

Head_on_a_Stick wrote:

Have you tried removing the addresses from dhcpcd.conf and just running:
# systemctl start dhcpcd.service

Jul 09 23:27:43 archiso systemd[1]: Stopping dhcpcd on all interfaces...
-- Subject: Unit dhcpcd.service has begun shutting down
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- 
-- Unit dhcpcd.service has begun shutting down.
Jul 09 23:27:43 archiso dhcpcd[1056]: sending signal TERM to pid 904
Jul 09 23:27:43 archiso dhcpcd[1056]: waiting for pid 904 to exit
Jul 09 23:27:43 archiso dhcpcd[904]: received SIGTERM, stopping
Jul 09 23:27:43 archiso dhcpcd[904]: enp3s0: removing interface
Jul 09 23:27:43 archiso dhcpcd[904]: enp2s0: removing interface
Jul 09 23:27:43 archiso dhcpcd[904]: enp2s0: deleting default route via xxx.xxx.68.1
Jul 09 23:27:43 archiso dhcpcd[904]: dhcpcd exited
Jul 09 23:27:43 archiso dhcpcd[1056]: sending signal TERM to pid 904
Jul 09 23:27:43 archiso dhcpcd[1056]: waiting for pid 904 to exit
Jul 09 23:27:43 archiso systemd[1]: Starting dhcpcd on all interfaces...
-- Subject: Unit dhcpcd.service has begun start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- 
-- Unit dhcpcd.service has begun starting up.
Jul 09 23:27:43 archiso dhcpcd[1065]: enp2s0: IPv6 kernel autoconf disabled
Jul 09 23:27:43 archiso dhcpcd[1065]: enp3s0: IPv6 kernel autoconf disabled
Jul 09 23:27:43 archiso dhcpcd[1065]: forked to background, child pid 1067
Jul 09 23:27:43 archiso systemd[1]: Started dhcpcd on all interfaces.
-- Subject: Unit dhcpcd.service has finished start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- 
-- Unit dhcpcd.service has finished starting up.
-- 
-- The start-up result is done.
Jul 09 23:27:43 archiso dhcpcd[1067]: DUID 00:01:00:01:1d:31:bb:7c:8c:89:a5:18:ed:17
Jul 09 23:27:43 archiso dhcpcd[1067]: enp2s0: IAID a5:18:ed:17
Jul 09 23:27:43 archiso dhcpcd[1067]: enp3s0: waiting for carrier
Jul 09 23:27:43 archiso dhcpcd[1067]: enp2s0: rebinding lease of xxx.xxx.68.244
Jul 09 23:27:43 archiso dhcpcd[1067]: enp2s0: leased xxx.xxx.68.244 for 691200 seconds
Jul 09 23:27:43 archiso dhcpcd[1067]: enp2s0: adding route to xxx.xxx.68.0/23
Jul 09 23:27:43 archiso dhcpcd[1067]: enp2s0: adding default route via xxx.xxx.68.1
Jul 09 23:27:43 archiso dhcpcd[1067]: enp2s0: removing route to xxx.xxx.68.0/23
Jul 09 23:27:43 archiso dhcpcd[1067]: enp2s0: soliciting an IPv6 router

Head_on_a_Stick wrote:

Also, if you assign IPs statically without a dhcp client you will have to edit /etc/resolv.conf and add some nameservers.
# /etc/resolv.conf
nameserver 8.8.8.8
nameserver 8.8.4.4

# echo 'nameserver 8.8.8.8' >> /etc/resolv.conf
# echo 'nameserver 8.8.4.4' >> /etc/resolv.conf
# netctl stop-all
# netctl start test

Jul 09 23:29:52 archiso systemd[1]: Stopped Networking for netctl profile test.
-- Subject: Unit netctl@test.service has finished shutting down
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- 
-- Unit netctl@test.service has finished shutting down.
Jul 09 23:29:57 archiso systemd[1]: Starting Networking for netctl profile test...
-- Subject: Unit netctl@test.service has begun start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- 
-- Unit netctl@test.service has begun starting up.
Jul 09 23:29:58 archiso network[1192]: Starting network profile 'test'...
Jul 09 23:29:58 archiso network[1192]: The interface of network profile 'test' is already up
Jul 09 23:29:58 archiso systemd[1]: netctl@test.service: Main process exited, code=exited, status=1/FAILURE
Jul 09 23:29:58 archiso systemd[1]: Failed to start Networking for netctl profile test.
-- Subject: Unit netctl@test.service has failed
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- 
-- Unit netctl@test.service has failed.
-- 
-- The result is failed.
Jul 09 23:29:58 archiso systemd[1]: netctl@test.service: Unit entered failed state.
Jul 09 23:29:58 archiso systemd[1]: netctl@test.service: Failed with result 'exit-code'.

In both cases I receive:

root@archiso ~ # ping -c3 www.google.com
PING www.google.com (173.194.113.147) 56(84) bytes of data.

--- www.google.com ping statistics ---
3 packets transmitted, 0 received, 100% packet loss, time 1999ms

EDIT: I redacted the precise IP for security reasons.

Last edited by Michael Gruenstaeudl (2015-07-12 12:19:39)

Head_on_a_Stick · 2015-07-09 22:04:22

Can you ping your router?

Michael Gruenstaeudl · 2015-07-09 22:11:17

Yes, I can ping the router.

root@archiso ~ # ping -c 3 xxx.xxx.68.1
PING xxx.xxx.68.1 (xxx.xxx.68.1) 56(84) bytes of data.
64 bytes from xxx.xxx.68.1: icmp_seq=1 ttl=64 time=0.605 ms
64 bytes from xxx.xxx.68.1: icmp_seq=2 ttl=64 time=0.488 ms
64 bytes from xxx.xxx.68.1: icmp_seq=3 ttl=64 time=0.436 ms

--- xxx.xxx.68.1 ping statistics ---
3 packets transmitted, 3 received, 0% packet loss, time 2000ms
rtt min/avg/max/mdev = 0.436/0.509/0.605/0.075 ms

EDIT 1: I can also ping the name server IP addresses and the broadcast address.

EDIT 2: I redacted the precise IP for security reasons.

Last edited by Michael Gruenstaeudl (2015-07-12 17:22:03)

Head_on_a_Stick · 2015-07-10 07:17:57

What is the content of /etc/resolv.conf?

EDIT: Do you have a firewall in place?

Last edited by Head_on_a_Stick (2015-07-10 07:18:23)

tomk · 2015-07-10 07:53:34

Are you using dhcpcd.service or netctl? You can't use both,

Michael Gruenstaeudl · 2015-07-10 09:36:49

@ Head_on_a_Stick

Head_on_a_Stick wrote:

What is the content of /etc/resolv.conf?
EDIT: Do you have a firewall in place?

root@archiso ~ # cat /etc/resolv.conf
# /etc/resolv.conf
nameserver 8.8.8.8
nameserver 8.8.4.4

Currently, there is no firewall in place.

@ tomk

tomk wrote:

Are you using dhcpcd.service or netctl? You can't use both,

Before trying out netctl, I stopped the dhcpcd.service.

Michael Gruenstaeudl · 2015-07-10 09:40:32

The issue seems to be connected to /etc/dhcpcd.conf. When I remove said file and (re-)start the dhcpcd.service, the correct IP address is automatically assigned. I can also ping the router, but I still cannot ping outside of the internal network.

root@archiso ~ # mv /etc/dhcpcd.conf /etc/dhcpcd.conf.bak
root@archiso ~ # dhcpcd enp2s0
enp2s0: IPv6 kernel autoconf disabled
DUID 00:01:00:01:1d:32:62:89:8c:89:a5:18:ed:17
enp2s0: IAID a5:18:ed:17
enp2s0: soliciting an IPv6 router
enp2s0: soliciting a DHCP lease
enp2s0: offered xxx.xxx.69.235 from xxx.xxx.71.2
enp2s0: leased xxx.xxx.69.235 for 691200 seconds
enp2s0: adding route to xxx.xxx.68.0/23
enp2s0: adding default route via xxx.xxx.68.1
forked to background, child pid 676

EDIT 1: I am told that IPv6 is no longer supported in our network. Maybe this causes an issue?

EDIT 2: I would like to point out again that, when I booted via the ArchBang LiveCD, the internet connection worked fine, as NetworkManager connected without difficulty. Yet, I was not able to ping either.

EDIT 3: I redacted the precise IP for security reasons.

Last edited by Michael Gruenstaeudl (2015-07-12 12:16:34)

Michael Gruenstaeudl · 2015-07-10 10:22:59

Starting the wired connection via netctl does not work either.

root@archiso ~ # systemctl stop dhcpcd.service

root@archiso ~ # cat /etc/netctl/test
Connection='ethernet'
Interface='enp2s0'
IP='static'
Address='xxx.xxx.69.235/23'

root@archiso ~ # netctl restart test
root@archiso ~ # journalctl -xe
Jul 10 12:19:49 archiso systemd[1]: Stopping Networking for netctl profile test...
-- Subject: Unit netctl@test.service has begun shutting down
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- 
-- Unit netctl@test.service has begun shutting down.
Jul 10 12:19:49 archiso network[1882]: Stopping network profile 'test'...
Jul 10 12:19:49 archiso network[1882]: Stopped network profile 'test'
Jul 10 12:19:49 archiso systemd[1]: Starting Networking for netctl profile test...
-- Subject: Unit netctl@test.service has begun start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- 
-- Unit netctl@test.service has begun starting up.
Jul 10 12:19:49 archiso network[1896]: Starting network profile 'test'...
Jul 10 12:19:49 archiso kernel: r8169 0000:02:00.0 enp2s0: link down
Jul 10 12:19:49 archiso kernel: r8169 0000:02:00.0 enp2s0: link down
Jul 10 12:19:49 archiso kernel: IPv6: ADDRCONF(NETDEV_UP): enp2s0: link is not ready
Jul 10 12:19:51 archiso ntpd[1122]: Deleting interface #11 enp2s0, xxx.xxx.69.235#123, interface stats: received=0, sent=0, dropped=0, active_time=479 secs
Jul 10 12:19:51 archiso kernel: r8169 0000:02:00.0 enp2s0: link up
Jul 10 12:19:51 archiso kernel: IPv6: ADDRCONF(NETDEV_CHANGE): enp2s0: link becomes ready
Jul 10 12:19:51 archiso network[1896]: Started network profile 'test'
Jul 10 12:19:51 archiso systemd[1]: Started Networking for netctl profile test.
-- Subject: Unit netctl@test.service has finished start-up
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- 
-- Unit netctl@test.service has finished starting up.
-- 
-- The start-up result is done.
Jul 10 12:19:53 archiso ntpd[1122]: Listen normally on 12 enp2s0 xxx.xxx.69.235:123
Jul 10 12:19:53 archiso ntpd[1122]: new interface(s) found: waking up resolver
Jul 10 12:20:08 archiso kernel: usb 1-1.2: USB disconnect, device number 75
Jul 10 12:20:10 archiso kernel: usb 1-1.2: new low-speed USB device number 76 using ehci-pci
Jul 10 12:20:10 archiso kernel: input: Logitech USB Optical Mouse as /devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.2/1-1.2:1.0/0003:046D:C077.004A/input/input88
Jul 10 12:20:10 archiso kernel: hid-generic 0003:046D:C077.004A: input,hidraw1: USB HID v1.11 Mouse [Logitech USB Optical Mouse] on usb-0000:00:1a.0-1.2/input0

root@archiso ~ # ping -c 3 www.google.com
ping: unknown host www.google.com

EDIT: I redacted the precise IP for security reasons.

Last edited by Michael Gruenstaeudl (2015-07-12 12:14:44)

ewaller · 2015-07-10 16:50:06

You say you cannot ping outside your network. Does that mean you can ping machines on the local network besides the router?
When you said you could ping the name server, does that mean you can ping 8.8.8.8?
Can you ping 66.211.214.131 (An archlinux.org machine) ?

Michael Gruenstaeudl · 2015-07-12 12:12:45

ewaller wrote:

You say you cannot ping outside your network. Does that mean you can ping machines on the local network besides the router?

Affirmative.

root@archiso ~ # ping -c 3 xxx.xxx.69.11
PING xxx.xxx.69.11 (xxx.xxx.69.11) 56(84) bytes of data.
64 bytes from xxx.xxx.69.11: icmp_seq=1 ttl=60 time=6.18 ms
64 bytes from xxx.xxx.69.11: icmp_seq=2 ttl=60 time=5.13 ms
64 bytes from xxx.xxx.69.11: icmp_seq=3 ttl=60 time=4.52 ms

--- xxx.xxx.69.11 ping statistics ---
3 packets transmitted, 3 received, 0% packet loss, time 2002ms
rtt min/avg/max/mdev = 4.528/5.283/6.188/0.690 ms
2003ms
rtt min/avg/max/mdev = 2.100/5.815/10.836/3.684 ms

ewaller wrote:

When you said you could ping the name server, does that mean you can ping 8.8.8.8?

No, I cannot ping 8.8.8.8. But I can ping the local DNS.

root@archiso ~ # ping -c 3 8.8.8.8
PING 8.8.8.8 (8.8.8.8) 56(84) bytes of data.

--- 8.8.8.8 ping statistics ---
3 packets transmitted, 0 received, 100% packet loss, time 2007ms

root@archiso ~ # ping -c 3 xxx.xxx.70.3
PING xxx.xxx.70.3 (xxx.xxx.70.3) 56(84) bytes of data.
64 bytes from xxx.xxx.70.3: icmp_seq=1 ttl=126 time=0.374 ms
64 bytes from xxx.xxx.70.3: icmp_seq=2 ttl=126 time=0.363 ms
64 bytes from xxx.xxx.70.3: icmp_seq=3 ttl=126 time=0.373 ms

--- xxx.xxx.70.3 ping statistics ---
3 packets transmitted, 3 received, 0% packet loss, time 1998ms
rtt min/avg/max/mdev = 0.363/0.370/0.374/0.005 ms

ewaller wrote:

Can you ping 66.211.214.131 (An archlinux.org machine) ?

No, I cannot.

root@archiso ~ # ping -c 3 66.211.214.131
PING 66.211.214.131 (66.211.214.131) 56(84) bytes of data.

--- 66.211.214.131 ping statistics ---
3 packets transmitted, 0 received, 100% packet loss, time 2007ms

EDIT: I redacted the precise IP for security reasons.

Last edited by Michael Gruenstaeudl (2015-07-12 12:15:09)

ewaller · 2015-07-12 15:05:33

I am afraid I am losing the bubble here, so forgive me if I go back over something we have covered.

What is the output of ip route ?
and have you tried disabling IPv6? https://wiki.archlinux.org/index.php/IPv6#Disable_IPv6

Michael Gruenstaeudl · 2015-07-12 15:15:35

ewaller wrote:

What is the output of ip route ?

root@archiso ~ # ip route
default via xxx.xxx.68.1 dev enp2s0  proto static  metric 100 
 xxx.xxx.68.0/23 dev enp2s0  proto kernel  scope link  src xxx.xxx.69.235 
 xxx.xxx.68.0/23 dev enp2s0  proto kernel  scope link  src xxx.xxx.69.235  metric 100 
 xxx.xxx.71.2 via xxx.xxx.68.1 dev enp2s0  proto dhcp  metric 100

Comment: I redacted the precise IP for security reasons. xxx.xxx is always the same six digit number, though.

ewaller wrote:

and have you tried disabling IPv6?

Yes, I had added noipv6rs and noipv6 and had commented out #noipv4ll in /etc/dhcpcd.conf, but to no avail.

EDIT: Again, my internet connection works just fine under NetworkManager when I boot via the ArchBang LiveCD. What settings does NetworkManager enforce that dhcpcd or netctl do not?

Last edited by Michael Gruenstaeudl (2015-07-12 15:20:15)

ewaller · 2015-07-12 15:24:57

What happens if you delete that last route. the ...71.2 route. It strikes me as odd.

Michael Gruenstaeudl · 2015-07-12 15:37:13

ewaller wrote:

What happens if you delete that last route. the ...71.2 route. It strikes me as odd.

Sorry, my bad. I had played around with defining additional nameservers in /etc/resolv.conf. Said nameserver has been removed, yet still no pinging (see below).

root@archiso ~ # ip route
default via xxx.xxx.68.1 dev enp2s0  proto static  metric 100 
 xxx.xxx.68.0/23 dev enp2s0  proto kernel  scope link  src xxx.xxx.69.235 
 xxx.xxx.68.0/23 dev enp2s0  proto kernel  scope link  src xxx.xxx.69.235  metric 100

root@archiso ~ # ping -c3 www.google.com
PING www.google.com (173.194.113.148) 56(84) bytes of data.

--- www.google.com ping statistics ---
3 packets transmitted, 0 received, 100% packet loss, time 2007ms

Last edited by Michael Gruenstaeudl (2015-07-12 15:37:38)

ewaller · 2015-07-12 15:52:04

I am at a loss. Clearly, the network hardware is working. You can use local services.
Pinging might be blocked at the gateway, but it works for Archbang. Even if it is blocked at the firewall, you should be able to use TCP and UDP services. You said you cannot.

The host name indicates that you are doing this from an Arch install media, and have not installed Arch yet (I think you stated that in your first post too).

Unfortunately, I am running out of airspeed, altitude and ideas all at once. It really appears that the gateway/router is blocking you.
Are you still using a static address? and did the Archbang use a dynamic address? If so, it could be that the router cannot figure out that you are there, but, it should only matter for things trying to reach you. This does not seem to be a problem for non-upstream ports.

If you are using static, perhaps the approach should be to figure out why dynamic addressing did not work out of the box.

I am going to be away for the rest of the morning and most of the afternoon (UTC-9h)

Awebb · 2015-07-12 16:52:27

This looks a bit weird. Could you please describe your setup? Please everything from whatever plug "the internet comes out" to your "modem", and whatever hardware is between that and your computer.

By the way, you forgot to censor one of the IP addresses. Beyond that, the IP range of your uni is public knowledge. You have provided enough information, that I could even call you in the office tomorrow morning and walk you through the process.

There is a slight chance, that the admins responsible for the (I assume) BCP have blacklisted the hostname "archiso" for some reason or somebody else has already used it and it has landed on a filter list/allocation list. You might want to read this one: http://www.mi.fu-berlin.de/w/IT/ItServi … S_und_DHCP and you might want to try one of the public DNS servers (I don't know if you usually use an internal server):

160.45.8.8
160.45.10.12
130.133.1.57

There are two differences between an ArchBang iso and the Arch installer: ArchBang lags behind regarding updates and the live system uses a different hostname. Try changing the hostname.

Head_on_a_Stick · 2015-07-12 17:54:10

Compare the `ip r` output from Arch & ArchBang.

Michael Gruenstaeudl · 2015-08-31 12:56:57

The network problems I described turned out to be a blacklisting issue indeed. Thanks to Awebb for pointing out this possibility.

Last edited by Michael Gruenstaeudl (2015-08-31 12:57:11)

Arch Linux

#1 2015-07-09 21:01:16

[SOLVED] Wired conn. failing at install despite working via ArchBang

#2 2015-07-09 21:06:33

Re: [SOLVED] Wired conn. failing at install despite working via ArchBang

#3 2015-07-09 21:46:33

Re: [SOLVED] Wired conn. failing at install despite working via ArchBang

#4 2015-07-09 22:04:22

Re: [SOLVED] Wired conn. failing at install despite working via ArchBang

#5 2015-07-09 22:11:17

Re: [SOLVED] Wired conn. failing at install despite working via ArchBang

#6 2015-07-10 07:17:57

Re: [SOLVED] Wired conn. failing at install despite working via ArchBang

#7 2015-07-10 07:53:34

Re: [SOLVED] Wired conn. failing at install despite working via ArchBang

#8 2015-07-10 09:36:49

Re: [SOLVED] Wired conn. failing at install despite working via ArchBang

#9 2015-07-10 09:40:32

Re: [SOLVED] Wired conn. failing at install despite working via ArchBang

#10 2015-07-10 10:22:59

Re: [SOLVED] Wired conn. failing at install despite working via ArchBang

#11 2015-07-10 16:50:06

Re: [SOLVED] Wired conn. failing at install despite working via ArchBang

#12 2015-07-12 12:12:45

Re: [SOLVED] Wired conn. failing at install despite working via ArchBang

#13 2015-07-12 15:05:33

Re: [SOLVED] Wired conn. failing at install despite working via ArchBang

#14 2015-07-12 15:15:35

Re: [SOLVED] Wired conn. failing at install despite working via ArchBang

#15 2015-07-12 15:24:57

Re: [SOLVED] Wired conn. failing at install despite working via ArchBang

#16 2015-07-12 15:37:13

Re: [SOLVED] Wired conn. failing at install despite working via ArchBang

#17 2015-07-12 15:52:04

Re: [SOLVED] Wired conn. failing at install despite working via ArchBang

#18 2015-07-12 16:52:27

Re: [SOLVED] Wired conn. failing at install despite working via ArchBang

#19 2015-07-12 17:54:10

Re: [SOLVED] Wired conn. failing at install despite working via ArchBang

#20 2015-08-31 12:56:57

Re: [SOLVED] Wired conn. failing at install despite working via ArchBang

Board footer