Issues Connecting via ethernet

agryphos · 2021-06-17 13:21:40

I recently installed arch a few days ago, and everything has been going well after the installation until today. Suddenly after I booted into Windows and back to arch again my wired connection isn't working.

It lists as wired connected, but I'm not able to make any connection.

Below are some commands I ran trying to find the issue

[# systemctl status NetorkManager
NetworkManager.service - Network Manager
     Loaded: loaded (/usr/lib/systemd/system/NetworkManager.service; enabled; vendor preset: disabled)
    Drop-In: /usr/lib/systemd/system/NetworkManager.service.d
             └──NetworkManager-ovs.conf
     Active: active (running) since Thu 2021-06-17 16:54:39 CEST; 8min ago
       Docs: man:NetworkManager(8)
   Main PID: 2530 (NetworkManager)
      Tasks: 3 (limit: 38378)
     Memory: 4.3M
        CPU: 206ms
     CGroup: /system.slice/NetworkManager.service
             └── /usr/bin/NetworkManager --no-daemon

Jun 17 16:56:32 archyphos NetworkManager[2530]: <info>  [1623941792.6835] device (enp5s0): state change: config -> ip-config (reason 'none', sys-iface-state: 'managed')
Jun 17 16:56:32 archyphos NetworkManager[2530]: <info>  [1623941792.6837] dhcp4 (enp5s0): activation: beginning transaction (timeout in 45 seconds)
Jun 17 16:56:32 archyphos NetworkManager[2530]: <info>  [1623941792.6984] dhcp4 (enp5s0): state changed unknown -> bound, address=192.168.1.104
Jun 17 16:56:32 archyphos NetworkManager[2530]: <info>  [1623941792.6992] device (enp5s0): state change: ip-config -> ip-check (reason 'none', sys-iface-state: 'managed')
Jun 17 16:56:32 archyphos NetworkManager[2530]: <info>  [1623941792.7049] device (enp5s0): state change: ip-check -> secondaries (reason 'none', sys-iface-state: 'managed')
Jun 17 16:56:32 archyphos NetworkManager[2530]: <info>  [1623941792.7050] device (enp5s0): state change: secondaries -> activated (reason 'none', sys-iface-state: 'managed')
Jun 17 16:56:32 archyphos NetworkManager[2530]: <info>  [1623941792.7052] manager: NetworkManager state is now CONNECTED_LOCAL
Jun 17 16:56:32 archyphos NetworkManager[2530]: <info>  [1623941792.7057] manager: NetworkManager state is now CONNECTED_SITE
Jun 17 16:56:32 archyphos NetworkManager[2530]: <info>  [1623941792.7058] policy: set 'Wired connection 1' (enp5s0) as default for IPv4 routing and DNS
Jun 17 16:56:32 archyphos NetworkManager[2530]: <info>  [1623941792.7079] device (enp5s0): Activation: successful, device activated.

$ ip link
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN mode DEFAULT group default qlen 1000
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
2: enp5s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP mode DEFAULT group default qlen 1000
    link/ether 04:d9:f5:f6:06:fe brd ff:ff:ff:ff:ff:ff

$ ip route
default via 192.168.1.1 dev enp5s0 proto dhcp metric 20100
192.168.1.0/24 dev enp5s0 proto kernel scope link src 192.168.1.104 metric 100

I have tried searching but I can't figure out the issue.
I booted with the installation medium to try with dhcpcd, but dhcpcd did not connect either.

I would love some clues on what to do because I'm feeling rather stumped right now.

Last edited by agryphos (2021-06-17 13:46:37)

agryphos · 2021-06-17 19:45:39

The problem seems to have resolved itself, although I am not 100% sure what I did to do so. It could have been a firewall issue as I tried turning my firewall off. But it still worked when I started the firewall daemon again? Again, not really sure of the cause but I'll try to do more research tomorrow and this can probably be tagged as resolved.

Slithery · 2021-06-17 19:48:27

What's the output of...

find /etc/systemd -type l -exec test -f {} \; -print | awk -F'/' '{ printf ("%-40s | %s\n", $(NF-0), $(NF-1)) }' | sort -f

euromatlox · 2021-06-17 19:52:01

You might need to study Arch Wiki Network configuration carefully. I personally use systemd-networkd, so cannot help you with that choice of yours (NetworkManager). If you're a beginner (fresh install) you can think which network manager is best for your usage. It's a feature that you not switch easily like a web browser.

agryphos · 2021-06-17 19:59:37

It seems that the issue lies in ufw. Could be because I was running 2 firewall programs like an absolute fool (thinking about that now, it's just like why would I even....). I'll try to read through this in more detail tomorrow because I want to learn from this. Posting this up top so it is known before someone spends a bunch of time reading through this.

Slithery wrote:

What's the output of...

find /etc/systemd -type l -exec test -f {} \; -print | awk -F'/' '{ printf ("%-40s | %s\n", $(NF-0), $(NF-1)) }' | sort -f

Output below:

$ find /etc/systemd -type l -exec test -f {} \; -print | awk -F'/' '{ printf ("%-40s | %s\n", $(NF-0), $(NF-1)) }' | sort -f
acpid.service                            | multi-user.target.wants
avahi-daemon.service                     | multi-user.target.wants
avahi-daemon.socket                      | sockets.target.wants
cups.path                                | multi-user.target.wants
cups.service                             | printer.target.wants
cups.socket                              | sockets.target.wants
dbus-org.fedoraproject.FirewallD1.service | system
dbus-org.freedesktop.Avahi.service       | system
dbus-org.freedesktop.nm-dispatcher.service | system
dbus-org.freedesktop.timesync1.service   | system
dirmngr.socket                           | sockets.target.wants
display-manager.service                  | system
firewalld.service                        | multi-user.target.wants
fstrim.timer                             | timers.target.wants
getty@tty1.service                       | getty.target.wants
gpg-agent-browser.socket                 | sockets.target.wants
gpg-agent-extra.socket                   | sockets.target.wants
gpg-agent.socket                         | sockets.target.wants
gpg-agent-ssh.socket                     | sockets.target.wants
libvirtd-ro.socket                       | sockets.target.wants
libvirtd.service                         | multi-user.target.wants
libvirtd.socket                          | sockets.target.wants
NetworkManager.service                   | multi-user.target.wants
NetworkManager-wait-online.service       | network-online.target.wants
p11-kit-server.socket                    | sockets.target.wants
pipewire-media-session.service           | pipewire.service.wants
pipewire.socket                          | sockets.target.wants
pulseaudio.socket                        | sockets.target.wants
reflector.timer                          | timers.target.wants
remote-fs.target                         | multi-user.target.wants
sshd.service                             | multi-user.target.wants
systemd-timesyncd.service                | sysinit.target.wants
ufw.service                              | multi-user.target.wants
virtlockd.socket                         | sockets.target.wants
virtlogd.socket                          | sockets.target.wants
xdg-user-dirs-update.service             | default.target.wants

When I tried to re-enable it I got this error print:

$ sudo ufw enable
ERROR: problem running ufw-init
modprobe: FATAL: Module nf_conntrack_ftp not found in directory /lib/modules/5.12.10-arch1-1
modprobe: FATAL: Module nf_nat_ftp not found in directory /lib/modules/5.12.10-arch1-1
modprobe: FATAL: Module nf_conntrack_netbios_ns not found in directory /lib/modules/5.12.10-arch1-1
iptables-restore v1.8.7 (nf_tables):
line 42: RULE_APPEND failed (No such file or directory): rule in chain INPUT
line 42: RULE_APPEND failed (No such file or directory): rule in chain INPUT
line 42: RULE_APPEND failed (No such file or directory): rule in chain INPUT
line 42: RULE_APPEND failed (No such file or directory): rule in chain INPUT
line 42: RULE_APPEND failed (No such file or directory): rule in chain INPUT
line 42: RULE_APPEND failed (No such file or directory): rule in chain INPUT
line 42: RULE_APPEND failed (No such file or directory): rule in chain OUTPUT
line 42: RULE_APPEND failed (No such file or directory): rule in chain OUTPUT
line 42: RULE_APPEND failed (No such file or directory): rule in chain OUTPUT
line 42: RULE_APPEND failed (No such file or directory): rule in chain OUTPUT
line 42: RULE_APPEND failed (No such file or directory): rule in chain OUTPUT
line 42: RULE_APPEND failed (No such file or directory): rule in chain OUTPUT
line 42: RULE_APPEND failed (No such file or directory): rule in chain FORWARD
line 42: RULE
iptables-restore v1.8.7 (nf_tables): Couldn't load match `conntrack':No such file or directory

Error occurred at line: 2
Try `iptables-restore -h' or 'iptables-restore --help' for more information.
iptables-restore v1.8.7 (nf_tables):
line 8: RULE_APPEND failed (No such file or directory): rule in chain ufw-skip-to-policy-input
line 8: RULE_APPEND failed (No such file or directory): rule in chain ufw-skip-to-policy-output
line 8: RULE_APPEND failed (No such file or directory): rule in chain ufw-skip-to-policy-forward
iptables-restore v1.8.7 (nf_tables): Couldn't load match `conntrack':No such file or directory

Error occurred at line: 25
Try `iptables-restore -h' or 'iptables-restore --help' for more information.
iptables-restore v1.8.7 (nf_tables): unknown option "--dport"
Error occurred at line: 19
Try `iptables-restore -h' or 'iptables-restore --help' for more information.
iptables-restore v1.8.7 (nf_tables): unknown option "--log-prefix"
Error occurred at line: 23
Try `iptables-restore -h' or 'iptables-restore --help' for more information.
iptables-restore: line 5 failed
ip6tables-restore v1.8.7 (nf_tables):
line 42: RULE_APPEND failed (No such file or directory): rule in chain INPUT
line 42: RULE_APPEND failed (No such file or directory): rule in chain INPUT
line 42: RULE_APPEND failed (No such file or directory): rule in chain INPUT
line 42: RULE_APPEND failed (No such file or directory): rule in chain INPUT
line 42: RULE_APPEND failed (No such file or directory): rule in chain INPUT
line 42: RULE_APPEND failed (No such file or directory): rule in chain INPUT
line 42: RULE_APPEND failed (No such file or directory): rule in chain OUTPUT
line 42: RULE_APPEND failed (No such file or directory): rule in chain OUTPUT
line 42: RULE_APPEND failed (No such file or directory): rule in chain OUTPUT
line 42: RULE_APPEND failed (No such file or directory): rule in chain OUTPUT
line 42: RULE_APPEND failed (No such file or directory): rule in chain OUTPUT
line 42: RULE_APPEND failed (No such file or directory): rule in chain OUTPUT
line 42: RULE_APPEND failed (No such file or directory): rule in chain FORWARD
line 42: RULE
ip6tables-restore v1.8.7 (nf_tables): Couldn't load match `conntrack':No such file or directory

Error occurred at line: 2
Try `ip6tables-restore -h' or 'ip6tables-restore --help' for more information.
ip6tables-restore v1.8.7 (nf_tables):
line 8: RULE_APPEND failed (No such file or directory): rule in chain ufw6-skip-to-policy-input
line 8: RULE_APPEND failed (No such file or directory): rule in chain ufw6-skip-to-policy-output
line 8: RULE_APPEND failed (No such file or directory): rule in chain ufw6-skip-to-policy-forward
ip6tables-restore v1.8.7 (nf_tables): Couldn't load match `rt':No such file or directory

Error occurred at line: 24
Try `ip6tables-restore -h' or 'ip6tables-restore --help' for more information.
ip6tables-restore v1.8.7 (nf_tables): unknown option "--dport"
Error occurred at line: 19
Try `ip6tables-restore -h' or 'ip6tables-restore --help' for more information.
ip6tables-restore v1.8.7 (nf_tables): unknown option "--log-prefix"
Error occurred at line: 23
Try `ip6tables-restore -h' or 'ip6tables-restore --help' for more information.
ip6tables-restore: line 5 failed

Problem running '/etc/ufw/before.rules'
Problem running '/etc/ufw/after.rules'
Problem running '/etc/ufw/user.rules'
Problem running '/etc/ufw/before6.rules'
Problem running '/etc/ufw/after6.rules'
Problem running '/etc/ufw/user6.rules'

Last edited by agryphos (2021-06-17 20:02:29)

seth · 2021-06-18 06:10:28

modprobe: FATAL: Module nf_conntrack_ftp not found in directory /lib/modules/5.12.10-arch1-1
modprobe: FATAL: Module nf_nat_ftp not found in directory /lib/modules/5.12.10-arch1-1
modprobe: FATAL: Module nf_conntrack_netbios_ns not found in directory /lib/modules/5.12.10-arch1-1

pacman -Qikk linux

Also see the 3rd link below.

Arch Linux

#1 2021-06-17 13:21:40

Issues Connecting via ethernet

#2 2021-06-17 19:45:39

Re: Issues Connecting via ethernet

#3 2021-06-17 19:48:27

Re: Issues Connecting via ethernet

#4 2021-06-17 19:52:01

Re: Issues Connecting via ethernet

#5 2021-06-17 19:59:37

Re: Issues Connecting via ethernet

#6 2021-06-18 06:10:28

Re: Issues Connecting via ethernet

Board footer