[SOLVED] Weird networking issues after changing pc case and gpu.

Efka · 2026-04-15 10:44:28

So, i had perfectly working network with systemd-networkd and static ip.
Decided to change pc case, swap gpu and then it all started.

ip a

Nothing comes back. Router light of activity does not lighting up - so no network activity.

ip link set enp130s0 up

ipv6 network is on and can only visit ipv6 websites, but no ipv4.
I forgot how to check status of systemctl so once i got ipv6 i ran update with paru ( instead of pacman) installed dhcpcd due to need of internet for work.
Installed , ran the command to start and enable. Reboot. Internet is back and its non static ip.

ip a
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000
    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 noprefixroute
       valid_lft forever preferred_lft forever
2: enp130s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP group default qlen 1000
    link/ether 10:ff:e0:6b:c2:d0 brd ff:ff:ff:ff:ff:ff
    altname enx10ffe06bc2d0
    inet 192.168.1.92/24 brd 192.168.1.255 scope global dynamic noprefixroute enp130s0
       valid_lft 42256sec preferred_lft 36856sec
    inet6 2a00:f502:250:cada:c02a:5ddf:6b19:3001/64 scope global mngtmpaddr noprefixroute
       valid_lft forever preferred_lft forever
    inet6 fe80::e6ca:7308:14a:95db/64 scope link
       valid_lft forever preferred_lft forever

Ran few commands:

systemctl status systemd-networkd
● systemd-networkd.service - Network Management
     Loaded: loaded (/usr/lib/systemd/system/systemd-networkd.service; enabled; preset: enabled)
     Active: active (running) since Wed 2026-04-15 05:12:18 CDT; 11min ago
 Invocation: 4c04be42025c429590cc8112e16d1482
TriggeredBy: ● systemd-networkd.socket
             ● systemd-networkd-varlink.socket
             ● systemd-networkd-resolve-hook.socket
             ● systemd-networkd-varlink-metrics.socket
       Docs: man:systemd-networkd.service(8)
             man:org.freedesktop.network1(5)
   Main PID: 649 (systemd-network)
     Status: "Processing requests..."
      Tasks: 1 (limit: 38088)
   FD Store: 0 (limit: 512)
     Memory: 4.8M (peak: 7.9M)
        CPU: 32ms
     CGroup: /system.slice/systemd-networkd.service
             └─649 /usr/lib/systemd/systemd-networkd

Apr 15 05:12:18 kodasARCH systemd[1]: Starting Network Management...
Apr 15 05:12:18 kodasARCH systemd-networkd[649]: lo: Link UP
Apr 15 05:12:18 kodasARCH systemd-networkd[649]: lo: Gained carrier
Apr 15 05:12:18 kodasARCH systemd[1]: Started Network Management.
Apr 15 05:12:18 kodasARCH systemd-networkd[649]: eth0: Interface name change detected, renamed to enp130s0.
Apr 15 05:12:20 kodasARCH systemd-networkd[649]: enp130s0: Link UP
Apr 15 05:12:22 kodasARCH systemd-networkd[649]: enp130s0: Gained carrier
Apr 15 05:12:24 kodasARCH systemd-networkd[649]: enp130s0: Gained IPv6LL

systemctl status dhcpcd
● dhcpcd.service - DHCP/ IPv4LL/ IPv6RA/ DHCPv6 client on all interfaces
     Loaded: loaded (/usr/lib/systemd/system/dhcpcd.service; enabled; preset: disabled)
     Active: active (running) since Wed 2026-04-15 05:12:19 CDT; 13min ago
 Invocation: 1d93331879264457b5d741b548a1a89d
   Main PID: 787 (dhcpcd)
      Tasks: 5 (limit: 38088)
     Memory: 3.4M (peak: 8.5M)
        CPU: 88ms
     CGroup: /system.slice/dhcpcd.service
             ├─787 "dhcpcd: [manager] [ip4] [ip6]"
             ├─792 "dhcpcd: [privileged proxy]"
             ├─793 "dhcpcd: [network proxy]"
             ├─794 "dhcpcd: [control proxy]"
             └─851 "dhcpcd: [BPF ARP] enp130s0 192.168.1.92"

Apr 15 05:12:23 kodasARCH dhcpcd[792]: enp130s0: rebinding lease of 192.168.1.92
Apr 15 05:12:23 kodasARCH dhcpcd[792]: enp130s0: probing address 192.168.1.92/24
Apr 15 05:12:24 kodasARCH dhcpcd[792]: enp130s0: soliciting an IPv6 router
Apr 15 05:12:24 kodasARCH dhcpcd[792]: enp130s0: Router Advertisement from fe80::5ced:eeda:7d02:685f
Apr 15 05:12:24 kodasARCH dhcpcd[792]: enp130s0: adding address 2a00:f502:250:cada:c02a:5ddf:6b19:3001/64
Apr 15 05:12:24 kodasARCH dhcpcd[792]: enp130s0: adding route to 2a00:f502:250:cada::/64
Apr 15 05:12:24 kodasARCH dhcpcd[792]: enp130s0: adding default route via fe80::5ced:eeda:7d02:685f
Apr 15 05:12:28 kodasARCH dhcpcd[792]: enp130s0: leased 192.168.1.92 for 43200 seconds
Apr 15 05:12:28 kodasARCH dhcpcd[792]: enp130s0: adding route to 192.168.1.0/24
Apr 15 05:12:28 kodasARCH dhcpcd[792]: enp130s0: adding default route via 192.168.1.1

ip route show
default via 192.168.1.1 dev enp130s0 proto dhcp src 192.168.1.92 metric 1002 mtu 1500
192.168.1.0/24 dev enp130s0 proto dhcp scope link src 192.168.1.92 metric 1002 mtu 1500

ip -6 route show
2a00:f502:250:cada::/64 dev enp130s0 proto ra metric 1002 mtu 1500 pref medium
fe80::/64 dev enp130s0 proto kernel metric 256 pref medium
default via fe80::5ced:eeda:7d02:685f dev enp130s0 proto ra metric 1002 expires 63671sec mtu 1500 pref medium

Which interface is running ? systemd-networkd or dhcpcd ?
One command shows dhcpcd is disabled and other - ip is trough dhcpcd.

Last edited by Efka (2026-04-15 12:21:20)

-thc · 2026-04-15 12:00:32

Efka wrote:

installed dhcpcd due to need of internet for work.
Installed , ran the command to start and enable. Reboot. Internet is back and its non static ip.

That's not how you enable DHCP in systemd-networkd. See the "Note" here.

Efka wrote:

Which interface is running ? systemd-networkd or dhcpcd ?
One command shows dhcpcd is disabled and other - ip is trough dhcpcd.

Only one interface: enp130s0. Both systemd-networkd and dhcpcd are running - see above. Where do you get "dhcpcd is disabled" from?

What is the content of your *.netdev and *.network files under "/etc/systemd/network"?

Efka · 2026-04-15 12:20:52

-thc wrote:

Efka wrote:
installed dhcpcd due to need of internet for work.
Installed , ran the command to start and enable. Reboot. Internet is back and its non static ip.
That's not how you enable DHCP in systemd-networkd. See the "Note" here.
Efka wrote:
Which interface is running ? systemd-networkd or dhcpcd ?
One command shows dhcpcd is disabled and other - ip is trough dhcpcd.
Only one interface: enp130s0. Both systemd-networkd and dhcpcd are running - see above. Where do you get "dhcpcd is disabled" from?
What is the content of your *.netdev and *.network files under "/etc/systemd/network"?

ls /etc/systemd/network
20-wired.network

GOT THE CULPRIT OF THIS ISSUE.
Ive changed nvme from one slot to another one and looks like this caused my network card to go from enp132s0 to enp130s0.

cat /etc/systemd/network/20-wired.network
[Match]
Name=enp132s0

[Network]
Address=192.168.1.100/24
Gateway=192.168.1.1
DNS=1.1.1.1
DNS=8.8.8.8
DNS=2606:4700:4700::1111
DNS=2606:4700:4700::1001

Where do you get "dhcpcd is disabled"
I think i mixed up with preset: disabled

systemctl status dhcpcd
● dhcpcd.service - DHCP/ IPv4LL/ IPv6RA/ DHCPv6 client on all interfaces
     Loaded: loaded (/usr/lib/systemd/system/dhcpcd.service; enabled; preset: disabled)

About interface, correct enp130s0 , i mixed up my words with systemd-networkd and dhcpcd - this is what i meant to say.

SOLVED.
Thank You. I keep forgetting about changes when i change things in pcie and nvme slots.

Arch Linux

#1 2026-04-15 10:44:28

[SOLVED] Weird networking issues after changing pc case and gpu.

#2 2026-04-15 12:00:32

Re: [SOLVED] Weird networking issues after changing pc case and gpu.

#3 2026-04-15 12:20:52

Re: [SOLVED] Weird networking issues after changing pc case and gpu.

Board footer