[SOLVED] Internet via Ethernet doesn't work during install

yohgen · 2020-07-17 12:48:24

After booting into Archiso, typing

ping www.archlinux.org / google.com / 8.8.8.8

yields no result. I tried most of the stuff in arch wiki and forums, for example:

Restarting network services
Running
```
dhcpcd
```
Changing default config files (for both static and dynamic IP, although I'm pretty sure that my IP is dynamic)

For the record, my Internet seems to work on other devices, and what's the most curious is that my previous installation on the same system but on a different hard drive didn't had this issue, and if I swap drives and boot into the Arch that already had been installed the internet still works as expected.

Ip link output:

1: lo: <LOOPBAKC,UP,LOWER_UP> mtu 65536 qdisk noqueue state UNKOWN mode DEFAULT group default qlen 1000
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
2: enp4s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisk mq state UP mode DEFAULT group default qlen 1000
    link/ether d0:50:99:00:18:eb brd ff:ff:ff:ff:ff:ff

(PS: had to type manually, might be mistakes)

If there is any additional info you need, please ask

Last edited by yohgen (2020-07-20 07:22:12)

loqs · 2020-07-17 12:57:34

ping www.archlinux.org

The command exits with no output produced?

yohgen · 2020-07-17 12:59:44

Update:
Checking dhcpcd service status has the following output:

Loaded: loaded
Active: failed
~~~
archiso systemd[1]: Starting dhcpcd on all interfaces...
archiso dhcdpcd[3233]: sending commands to dhcpcd process
archiso systemd[1]: dhcpcd.service: Refusing to accept PID outside of service control group, aquired through unsafe symlink chain: /run/dhcpcd/pid
*same*
archiso systemd[1]: dhcpcd.service: Failed with result 'protocol'.
archisosystemd[1]: Failed to start dhcpcd on all interfaces.

(PS: typed by hand)

yohgen · 2020-07-17 13:01:08

loqs wrote:

ping www.archlinux.org
The command exits with no output produced?

Sorry for vague wording, it has:

ping: anysite.com: Name or service not known

loqs · 2020-07-17 13:13:00

What release of the arch ISO is this with? What is the NIC? What driver does the NIC use?

yohgen · 2020-07-17 13:22:45

loqs wrote:

What release of the arch ISO is this with? What is the NIC? What driver does the NIC use?

ISO release: archlinux-2020.07.01-x86_64 (latest one, as of now)
NIC: Broadcom Inc. and subsidiaries NetLink BCM57781 Gigabit Ethernet PCIe (rev 10) (I used "lspci", although I'm not sure if this is what you need. Correct me if it's wrong)
NIC driver in use: tg3 (same command as above)

yohgen · 2020-07-17 13:39:26

I've found this this thread that discusses the issues with my hardware, specifically referring to my chip as 'wacko' .
I'll try to follow the instructions there for the time being

seth · 2020-07-17 13:54:40

That was about "SD card reader doesn't work when I use my ethernet" (hence "wacko" - I'm not a very prudent god ;-) and you also have a 57781, not a 57785

I assume you might rather face "broken by systemd-networkd" (which for whatever reason seems the default on newer ISOs)

Ensure to stop that service (as well as systemd-resolved) before trying dhcpcd, but according to your OP the NIC is up and has a carrier - what's the output of "ip a"?
(You can post links to images, if you prefer)

yohgen · 2020-07-17 14:18:10

seth wrote:

That was about "SD card reader doesn't work when I use my ethernet" (hence "wacko" - I'm not a very prudent god ;-) and you also have a 57781, not a 57785
I assume you might rather face "broken by systemd-networkd" (which for whatever reason seems the default on newer ISOs)
Ensure to stop that service (as well as systemd-resolved) before trying dhcpcd, but according to your OP the NIC is up and has a carrier - what's the output of "ip a"?
(You can post links to images, if you prefer)

Here you go

seth · 2020-07-17 14:30:15

Up, but no lease.
So: stop systemd-network, ensure the NIC is down, start dhcpcd by hand (directly, not the service) and watch out for errors.
If it still fails to get a lease, edit /etc/dhcpcd.conf and change duid to clientid.

yohgen · 2020-07-17 14:30:21

I tried to stop 'systemd-network' and 'systemd-resolved' before running 'dhcpcd' as you suggested, but dhcpcd timed out as it did before:

dhcpcd-9.1.2 starting
dev: loaded udev
DUID 00:04:03:00:02:00:04:00:05:00:00:06:00:07:00:08:00:09
eno4s0: IAID 99:00:18:eb
enp4s0: soliciting an IPv6 router
enp4s0: soliciting a DHCP lease
enp4s0: no IPv6 Routers available
timed out
forked to background, child pid 1533

and 'ping' still can't do anything

yohgen · 2020-07-17 14:31:25

One second, your reply arrived as I was writing previous message

yohgen · 2020-07-17 14:49:28

seth wrote:

Up, but no lease.
So: stop systemd-network, ensure the NIC is down, start dhcpcd by hand (directly, not the service) and watch out for errors.
If it still fails to get a lease, edit /etc/dhcpcd.conf and change duid to clientid.

Sorry for the noob question, but what do you mean by "directly"? Just typing 'dhcpcd' into the terminal?

seth · 2020-07-17 14:51:47

Yup, but also ensure you kill the process you started before (and that forked into background)

nl6720 · 2020-07-17 15:00:09

What exactly is the rationale for dismissing systemd-networkd without even looking at networkctl output and logs?

# networkctl status enp4s0

yohgen · 2020-07-17 15:13:01

seth wrote:

Yup, but also ensure you kill the process you started before (and that forked into background)

I did the following:

# Stopped the services
systemctl stop systemd-networkd / systemd-resolved / dhcpcd / dhcpcd@enp3s0
# Killed that one in the background
kill -9 *process-pid*
# Checked each status. all seemed to be dead

# Downed the Ethernet
ip link set enp4s0 down
# Checked that it's down

# Finally, ran dhcpcd, with the following output:
main: control_open: Connection Refused
dhcpcd-9.1.2 starting
dhcp6_openudp: Address already in use
ps_inet_startcb: dhcp6_open: Address already in use
dev: loaded udev
DUID 00:04:03:00:02:00:04:00:05:00:00:06:00:07:00:08:00:09
no intefaces have a carrier
forked to background, child pid 3214

yohgen · 2020-07-17 15:21:35

nl6720 wrote:

What exactly is the rationale for dismissing systemd-networkd without even looking at networkctl output and logs?
# networkctl status enp4s0

networkctl output:

2: enp4s0
Link File: /usr/lib/systemd/network/99-default.link
Network File: /etc/systemd/network/20-ethernet.network
Type: ether
State: degraded (configuring)
Path: pci-0000:04:00.0
Driver: tg3
Vendor: Broadcom Inc. and subsidiaries
Model: NetLink BCM57781 Gigabit Ethernet PCIe (Z77 Extreme4 motherboard)
HW Adress: d0:50:99:00:18:eb (ASRock Incorporation)
MTU: 1500 (min: 60, max: 9000)
Queue Length (Tx/Rx): 5/5
Auto negotiation: yes
Speed: 100Mbps
Duplex: full
Port: tp
Address: fe80::d250:99ff:fe00:18eb
fe80::e55e:40a6:91b0:1643

enp4s0: Lost carrier
enp4s0: IPV6 successfully enabled
enp4s0: Link UP
enp4s0: gained carrier
enp4s0: gained IPv6LL
enp4s0: Link DOWN
enp4s0: Lost carrier
enp4s0: IPV6 successfully enabled
enp4s0: gained carrier
enp4s0: gained IPv6LL

Last edited by yohgen (2020-07-17 15:27:40)

seth · 2020-07-17 15:43:23

Don't "kill -9" by default.

The rationale for trying a different dhcp implementation was that the NIC was up, had a carrier but didn't get a lease.
Dhcp servers can be petty and clients broken (see the NM dhcp4 rebase…) and at least I'm not aware of options to impact the systemd dhcp implementation (aside the anon profile)

I don't like the carrier issues that showed up in the last few posts (updated "ip a"?), but they were not a symptom before.
(Aside a loose or broken cable, the SIGKILL could have induced this state)

Ensure there's a carrier ("ip a", in doubt: reboot) and try the behavior on clientid requests (if it's the dhcp server, this is - by anecdotal evidence - a popular cause of failure)

yohgen · 2020-07-17 15:45:26

I just booted into the other drive which I installed Arch on a week ago with the same system specs, and internet still works there.
For reference, it uses NetworkManager. I don't know whether this is helpful, but one the parameters that is different is that enp4s0 has a different address and also has a gateway. Driver is the same ('tg3')

I will try what seth has suggested now

yohgen · 2020-07-17 16:04:56

seth wrote:

Don't "kill -9" by default.
The rationale for trying a different dhcp implementation was that the NIC was up, had a carrier but didn't get a lease.
Dhcp servers can be petty and clients broken (see the NM dhcp4 rebase…) and at least I'm not aware of options to impact the systemd dhcp implementation (aside the anon profile)
I don't like the carrier issues that showed up in the last few posts (updated "ip a"?), but they were not a symptom before.
(Aside a loose or broken cable, the SIGKILL could have induced this state)
Ensure there's a carrier ("ip a", in doubt: reboot) and try the behavior on clientid requests (if it's the dhcp server, this is - by anecdotal evidence - a popular cause of failure)

You have my gratitude, kind sir!
Changing from 'duid' to 'clientid' in /etc/dhcpcd.conf, then running 'dhcpcd' indeed fixed the issue for me.

Again, thank you very much

seth · 2020-07-17 20:22:33

Awesome.
Please always remember to mark resolved threads by editing your initial posts subject - so others will know that there's no task left, but maybe a solution to find.
Thanks.

Arch Linux

#1 2020-07-17 12:48:24

[SOLVED] Internet via Ethernet doesn't work during install

#2 2020-07-17 12:57:34

Re: [SOLVED] Internet via Ethernet doesn't work during install

#3 2020-07-17 12:59:44

Re: [SOLVED] Internet via Ethernet doesn't work during install

#4 2020-07-17 13:01:08

Re: [SOLVED] Internet via Ethernet doesn't work during install

#5 2020-07-17 13:13:00

Re: [SOLVED] Internet via Ethernet doesn't work during install

#6 2020-07-17 13:22:45

Re: [SOLVED] Internet via Ethernet doesn't work during install

#7 2020-07-17 13:39:26

Re: [SOLVED] Internet via Ethernet doesn't work during install

#8 2020-07-17 13:54:40

Re: [SOLVED] Internet via Ethernet doesn't work during install

#9 2020-07-17 14:18:10

Re: [SOLVED] Internet via Ethernet doesn't work during install

#10 2020-07-17 14:30:15

Re: [SOLVED] Internet via Ethernet doesn't work during install

#11 2020-07-17 14:30:21

Re: [SOLVED] Internet via Ethernet doesn't work during install

#12 2020-07-17 14:31:25

Re: [SOLVED] Internet via Ethernet doesn't work during install

#13 2020-07-17 14:49:28

Re: [SOLVED] Internet via Ethernet doesn't work during install

#14 2020-07-17 14:51:47

Re: [SOLVED] Internet via Ethernet doesn't work during install

#15 2020-07-17 15:00:09

Re: [SOLVED] Internet via Ethernet doesn't work during install

#16 2020-07-17 15:13:01

Re: [SOLVED] Internet via Ethernet doesn't work during install

#17 2020-07-17 15:21:35

Re: [SOLVED] Internet via Ethernet doesn't work during install

#18 2020-07-17 15:43:23

Re: [SOLVED] Internet via Ethernet doesn't work during install

#19 2020-07-17 15:45:26

Re: [SOLVED] Internet via Ethernet doesn't work during install

#20 2020-07-17 16:04:56

Re: [SOLVED] Internet via Ethernet doesn't work during install

#21 2020-07-17 20:22:33

Re: [SOLVED] Internet via Ethernet doesn't work during install

Board footer