[Solved] TP-Link Archer C7 V5 Wi-Fi and Ethernet Disconnection after a few seconds

graves501 · June 18, 2020, 9:09am

TP-Link Archer C7 V5 Wi-Fi and Ethernet Disconnect

I recently installed openWRT 19.07.3 on my Archer C7 V5. It worked flawlessly on all my devices (various laptops, desktop pc, mobile phones) except on one device, my Dell XPS 15 9570.
I can connect to the network for a few seconds, but I get instantly disconnected.
Same scenario applies to connection via ethernet!

I thought the WIFI card is the culprit so I replaced it with a Intel AC9260, but it didn't change anything. Both WIFI and ethernet connection do not work.

I did not change anything in the openWRT settings besides adding an adblocker and DDNS.

I'm using Manjaro Linux with the 5.6 kernel, tried other kernels as well. Never had issues like that before switching to openWRT.

Here are some logs:

Thu Jun 18 09:40:02 2020 daemon.notice hostapd: wlan0: AP-STA-CONNECTED f8:ac:65:f9:9f:25
Thu Jun 18 09:40:02 2020 daemon.info hostapd: wlan0: STA f8:ac:65:f9:9f:25 RADIUS: starting accounting session 663578D2E8958FE3
Thu Jun 18 09:40:02 2020 daemon.info hostapd: wlan0: STA f8:ac:65:f9:9f:25 WPA: pairwise key handshake completed (RSN)
Thu Jun 18 09:40:02 2020 daemon.info dnsmasq-dhcp[18833]: DHCPREQUEST(br-lan) 192.168.1.108 f8:ac:65:f9:9f:25
Thu Jun 18 09:40:02 2020 daemon.info dnsmasq-dhcp[18833]: DHCPACK(br-lan) 192.168.1.108 f8:ac:65:f9:9f:25 xps15
Thu Jun 18 09:40:03 2020 daemon.info dnsmasq-dhcp[18833]: DHCPDISCOVER(br-lan) f8:ac:65:f9:9f:25
Thu Jun 18 09:40:03 2020 daemon.info dnsmasq-dhcp[18833]: DHCPOFFER(br-lan) 192.168.1.110 f8:ac:65:f9:9f:25
Thu Jun 18 09:40:03 2020 daemon.info dnsmasq-dhcp[18833]: DHCPREQUEST(br-lan) 192.168.1.110 f8:ac:65:f9:9f:25
Thu Jun 18 09:40:03 2020 daemon.info dnsmasq-dhcp[18833]: DHCPACK(br-lan) 192.168.1.110 f8:ac:65:f9:9f:25
Thu Jun 18 09:40:03 2020 daemon.notice hostapd: wlan0: AP-STA-DISCONNECTED f8:ac:65:f9:9f:25
Thu Jun 18 09:40:09 2020 daemon.info hostapd: wlan0: STA f8:ac:65:f9:9f:25 IEEE 802.11: authenticated
Thu Jun 18 09:40:09 2020 daemon.info hostapd: wlan0: STA f8:ac:65:f9:9f:25 IEEE 802.11: associated (aid 4)
Thu Jun 18 09:40:09 2020 daemon.notice hostapd: wlan0: AP-STA-CONNECTED f8:ac:65:f9:9f:25
Thu Jun 18 09:40:09 2020 daemon.info hostapd: wlan0: STA f8:ac:65:f9:9f:25 RADIUS: starting accounting session A2027606693333C9
Thu Jun 18 09:40:09 2020 daemon.info hostapd: wlan0: STA f8:ac:65:f9:9f:25 WPA: pairwise key handshake completed (RSN)
Thu Jun 18 09:40:09 2020 daemon.info dnsmasq-dhcp[18833]: DHCPREQUEST(br-lan) 192.168.1.108 f8:ac:65:f9:9f:25
Thu Jun 18 09:40:09 2020 daemon.info dnsmasq-dhcp[18833]: DHCPACK(br-lan) 192.168.1.108 f8:ac:65:f9:9f:25 xps15
Thu Jun 18 09:40:10 2020 daemon.notice hostapd: wlan0: AP-STA-DISCONNECTED f8:ac:65:f9:9f:25

trendy · June 18, 2020, 10:11am

Are you connected both by cable and wifi?
I can see the same mac asking for dhcp leases although it already has one.
Post also here the output of uci export network; uci export dhcp; uci export wireless

graves501 · June 18, 2020, 10:21am

Hi, thanks for your reply.

No, only one at a time. Currently using USB tethering via my phone to use internet. I disconnected the USB tethering and tried to connect to WIFI once again, hopefully this is more helpful:

Thu Jun 18 12:13:10 2020 daemon.notice hostapd: wlan0: AP-STA-CONNECTED f8:ac:65:f9:9f:25
Thu Jun 18 12:13:10 2020 daemon.info hostapd: wlan0: STA f8:ac:65:f9:9f:25 RADIUS: starting accounting session A7EEE9A19AE10401
Thu Jun 18 12:13:10 2020 daemon.info hostapd: wlan0: STA f8:ac:65:f9:9f:25 WPA: pairwise key handshake completed (RSN)
Thu Jun 18 12:13:10 2020 daemon.info dnsmasq-dhcp[18833]: DHCPREQUEST(br-lan) 192.168.1.108 f8:ac:65:f9:9f:25
Thu Jun 18 12:13:10 2020 daemon.info dnsmasq-dhcp[18833]: DHCPACK(br-lan) 192.168.1.108 f8:ac:65:f9:9f:25 xps15
Thu Jun 18 12:13:11 2020 daemon.info dnsmasq-dhcp[18833]: DHCPDISCOVER(br-lan) f8:ac:65:f9:9f:25
Thu Jun 18 12:13:11 2020 daemon.info dnsmasq-dhcp[18833]: DHCPOFFER(br-lan) 192.168.1.110 f8:ac:65:f9:9f:25
Thu Jun 18 12:13:12 2020 daemon.info dnsmasq-dhcp[18833]: DHCPREQUEST(br-lan) 192.168.1.110 f8:ac:65:f9:9f:25
Thu Jun 18 12:13:12 2020 daemon.info dnsmasq-dhcp[18833]: DHCPACK(br-lan) 192.168.1.110 f8:ac:65:f9:9f:25
Thu Jun 18 12:13:12 2020 daemon.notice hostapd: wlan0: AP-STA-DISCONNECTED f8:ac:65:f9:9f:25
Thu Jun 18 12:13:17 2020 daemon.info hostapd: wlan0: STA f8:ac:65:f9:9f:25 IEEE 802.11: authenticated
Thu Jun 18 12:13:17 2020 daemon.info hostapd: wlan0: STA f8:ac:65:f9:9f:25 IEEE 802.11: associated (aid 4)
Thu Jun 18 12:13:17 2020 daemon.notice hostapd: wlan0: AP-STA-CONNECTED f8:ac:65:f9:9f:25
Thu Jun 18 12:13:17 2020 daemon.info hostapd: wlan0: STA f8:ac:65:f9:9f:25 RADIUS: starting accounting session D0115BE44E469F17
Thu Jun 18 12:13:17 2020 daemon.info hostapd: wlan0: STA f8:ac:65:f9:9f:25 WPA: pairwise key handshake completed (RSN)
Thu Jun 18 12:13:17 2020 daemon.info dnsmasq-dhcp[18833]: DHCPREQUEST(br-lan) 192.168.1.108 f8:ac:65:f9:9f:25
Thu Jun 18 12:13:17 2020 daemon.info dnsmasq-dhcp[18833]: DHCPACK(br-lan) 192.168.1.108 f8:ac:65:f9:9f:25 xps15
Thu Jun 18 12:13:18 2020 daemon.notice hostapd: wlan0: AP-STA-DISCONNECTED f8:ac:65:f9:9f:25
Thu Jun 18 12:13:22 2020 daemon.info hostapd: wlan0: STA f8:ac:65:f9:9f:25 IEEE 802.11: authenticated
Thu Jun 18 12:13:22 2020 daemon.info hostapd: wlan0: STA f8:ac:65:f9:9f:25 IEEE 802.11: associated (aid 4)
Thu Jun 18 12:13:22 2020 daemon.notice hostapd: wlan0: AP-STA-CONNECTED f8:ac:65:f9:9f:25
Thu Jun 18 12:13:22 2020 daemon.info hostapd: wlan0: STA f8:ac:65:f9:9f:25 RADIUS: starting accounting session C4A47373C28E37BD
Thu Jun 18 12:13:22 2020 daemon.info hostapd: wlan0: STA f8:ac:65:f9:9f:25 WPA: pairwise key handshake completed (RSN)
Thu Jun 18 12:13:22 2020 daemon.info dnsmasq-dhcp[18833]: DHCPREQUEST(br-lan) 192.168.1.108 f8:ac:65:f9:9f:25
Thu Jun 18 12:13:22 2020 daemon.info dnsmasq-dhcp[18833]: DHCPACK(br-lan) 192.168.1.108 f8:ac:65:f9:9f:25 xps15
Thu Jun 18 12:13:23 2020 daemon.info dnsmasq-dhcp[18833]: DHCPDISCOVER(br-lan) f8:ac:65:f9:9f:25
Thu Jun 18 12:13:23 2020 daemon.info dnsmasq-dhcp[18833]: DHCPOFFER(br-lan) 192.168.1.110 f8:ac:65:f9:9f:25
Thu Jun 18 12:13:23 2020 daemon.info dnsmasq-dhcp[18833]: DHCPREQUEST(br-lan) 192.168.1.110 f8:ac:65:f9:9f:25
Thu Jun 18 12:13:23 2020 daemon.info dnsmasq-dhcp[18833]: DHCPACK(br-lan) 192.168.1.110 f8:ac:65:f9:9f:25
Thu Jun 18 12:13:24 2020 daemon.notice hostapd: wlan0: AP-STA-DISCONNECTED f8:ac:65:f9:9f:25

Here is the output of uci export network; uci export dhcp; uci export wireless I obviously changed SSID and keys:

config interface 'loopback'
        option ifname 'lo'
        option proto 'static'
        option ipaddr '127.0.0.1'
        option netmask '255.0.0.0'

config globals 'globals'
        option ula_prefix 'fd1d:6b51:d6d0::/48'

config interface 'lan'
        option type 'bridge'
        option ifname 'eth0.1'
        option proto 'static'
        option ipaddr '192.168.1.1'
        option netmask '255.255.255.0'
        option ip6assign '60'

config interface 'wan'
        option ifname 'eth0.2'
        option proto 'dhcp'
        option peerdns '0'
        list dns '1.1.1.1'
        list dns '1.0.0.1'

config device 'wan_eth0_2_dev'
        option name 'eth0.2'
        option macaddr '50:d4:f7:82:8b:ee'

config interface 'wan6'
        option ifname 'eth0.2'
        option proto 'dhcpv6'
        option reqprefix 'auto'
        option reqaddress 'try'
        option peerdns '0'
        list dns '1.1.1.1'
        list dns '1.0.0.1'

config switch
        option name 'switch0'
        option reset '1'
        option enable_vlan '1'

config switch_vlan
        option device 'switch0'
        option vlan '1'
        option ports '2 3 4 5 0t'

config switch_vlan
        option device 'switch0'
        option vlan '2'
        option ports '1 0t'

package dhcp

config dnsmasq
        option domainneeded '1'
        option boguspriv '1'
        option filterwin2k '0'
        option localise_queries '1'
        option rebind_protection '1'
        option rebind_localhost '1'
        option local '/lan/'
        option domain 'lan'
        option expandhosts '1'
        option nonegcache '0'
        option authoritative '1'
        option readethers '1'
        option leasefile '/tmp/dhcp.leases'
        option resolvfile '/tmp/resolv.conf.auto'
        option nonwildcard '1'
        option localservice '1'
        option confdir '/tmp/dnsmasq.d'

config dhcp 'lan'
        option interface 'lan'
        option start '100'
        option limit '150'
        option leasetime '12h'
        option dhcpv6 'server'
        option ra 'server'

config dhcp 'wan'
        option interface 'wan'
        option ignore '1'

config odhcpd 'odhcpd'
        option maindhcp '0'
        option leasefile '/tmp/hosts/odhcpd'
        option leasetrigger '/usr/sbin/odhcpd-update'
        option loglevel '4'

package wireless

config wifi-device 'radio0'
        option type 'mac80211'
        option channel '36'
        option hwmode '11a'
        option path 'pci0000:00/0000:00:00.0'
        option htmode 'VHT80'
        option country 'AT'

config wifi-iface 'default_radio0'
        option device 'radio0'
        option network 'lan'
        option mode 'ap'
        option encryption 'psk2'
        option key 'foo2'
        option ssid 'bar2'

config wifi-device 'radio1'
        option type 'mac80211'
        option channel '11'
        option hwmode '11g'
        option path 'platform/ahb/18100000.wmac'
        option htmode 'HT20'
        option country 'AT'

config wifi-iface 'default_radio1'
        option device 'radio1'
        option network 'lan'
        option mode 'ap'
        option key 'foo'
        option ssid 'bar'
        option encryption 'psk2'

trendy · June 18, 2020, 10:27am

graves501:

Thu Jun 18 12:13:10 2020 daemon.info dnsmasq-dhcp[18833]: DHCPACK(br-lan) 192.168.1.108 f8:ac:65:f9:9f:25 xps15
Thu Jun 18 12:13:11 2020 daemon.info dnsmasq-dhcp[18833]: DHCPDISCOVER(br-lan) f8:ac:65:f9:9f:25

Still the same. The client got the ack from dhcp server and immediately started a new discovery.
Are you using the Network Manager or something like that?

graves501 · June 18, 2020, 10:28am

Yes, I'm using the GUI of nm-applet.

trendy · June 18, 2020, 10:37am

Can you disable that and connect manually to rule out a misbehaving NetMan?

graves501 · June 18, 2020, 10:44am

Thanks again for your help!

I killed nm-applet and tried to connect to my 5GHz Wifi via nmcli. Same behaviour, it disconnects just 2-3 seconds later.

The weird thing is that my connection works flawlessly if I use my phone as a hotspot or via USB tethering.

trendy · June 18, 2020, 10:54am

Let's try the ethernet connection only without the NetMan.
Just plug in the cable and run dhcpcd

graves501 · June 18, 2020, 10:58am

Hi,

the output of dhcpcd is sending commands to dhcpcd process nothing else... I try to live boot from a USB drive later on, to see if my network configuration is faulty. I'll keep you updated. Thanks for your help once again.

trendy · June 18, 2020, 11:03am

You did run it as root, right?
Force it to use the ethernet interface only:
sudo dhcpcd eth0
or whatever the ethernet interface is.

graves501 · June 18, 2020, 11:21am

Yes, I ran the command as sudo dhcpcd eth0. I replaced eth0 according to the ethernet device label. Same output, sadly.

Interestingly if I boot with a Manjaro Live USB drive, the connection works flawlessly. Somehow some configuration is wrong, but I never had any issues in the past!

graves501 · June 18, 2020, 11:45am

With sudo journalctl -u dhcpcd.service I could get this log for wi-fi:

Jun 18 13:42:47 xps15 dhcpcd[966]: wlp59s0: carrier lost
Jun 18 13:42:47 xps15 dhcpcd[966]: wlp59s0: deleting address fd1d:6b51:d6d0:0:263c:af2a:3665:3f3f/64
Jun 18 13:42:47 xps15 dhcpcd[966]: wlp59s0: deleting route to fd1d:6b51:d6d0::/64
Jun 18 13:42:47 xps15 dhcpcd[966]: wlp59s0: deleting address fe80::ccec:6d96:802d:4dd1
Jun 18 13:42:47 xps15 dhcpcd[966]: wlp59s0: new hardware address: e2:f1:89:62:87:c8
Jun 18 13:42:48 xps15 dhcpcd[966]: wlp59s0: new hardware address: f8:ac:65:f9:9f:25
Jun 18 13:42:49 xps15 dhcpcd[966]: wlp59s0: carrier acquired
Jun 18 13:42:49 xps15 dhcpcd[966]: wlp59s0: IAID 65:f9:9f:25
Jun 18 13:42:49 xps15 dhcpcd[966]: wlp59s0: adding address fe80::ccec:6d96:802d:4dd1
Jun 18 13:42:50 xps15 dhcpcd[966]: wlp59s0: soliciting an IPv6 router
Jun 18 13:42:50 xps15 dhcpcd[966]: wlp59s0: Router Advertisement from fe80::52d4:f7ff:fe82:8bed
Jun 18 13:42:50 xps15 dhcpcd[966]: wlp59s0: adding address fd1d:6b51:d6d0:0:263c:af2a:3665:3f3f/64
Jun 18 13:42:50 xps15 dhcpcd[966]: wlp59s0: adding route to fd1d:6b51:d6d0::/64
Jun 18 13:42:50 xps15 dhcpcd[966]: wlp59s0: soliciting a DHCPv6 lease
Jun 18 13:42:50 xps15 dhcpcd[966]: wlp59s0: carrier lost
Jun 18 13:42:50 xps15 dhcpcd[966]: wlp59s0: deleting address fd1d:6b51:d6d0:0:263c:af2a:3665:3f3f/64
Jun 18 13:42:50 xps15 dhcpcd[966]: wlp59s0: deleting route to fd1d:6b51:d6d0::/64
Jun 18 13:42:50 xps15 dhcpcd[966]: wlp59s0: deleting address fe80::ccec:6d96:802d:4dd1
Jun 18 13:42:50 xps15 dhcpcd[966]: wlp59s0: new hardware address: 7a:9e:dc:62:5c:a7
Jun 18 13:42:52 xps15 dhcpcd[966]: wlp59s0: new hardware address: f8:ac:65:f9:9f:25
Jun 18 13:42:54 xps15 dhcpcd[966]: wlp59s0: carrier acquired
Jun 18 13:42:54 xps15 dhcpcd[966]: wlp59s0: IAID 65:f9:9f:25
Jun 18 13:42:54 xps15 dhcpcd[966]: wlp59s0: adding address fe80::ccec:6d96:802d:4dd1
Jun 18 13:42:54 xps15 dhcpcd[966]: wlp59s0: soliciting a DHCP lease
Jun 18 13:42:54 xps15 dhcpcd[966]: wlp59s0: offered 192.168.1.110 from 192.168.1.1
Jun 18 13:42:54 xps15 dhcpcd[966]: wlp59s0: probing address 192.168.1.110/24
Jun 18 13:42:55 xps15 dhcpcd[966]: wlp59s0: soliciting an IPv6 router
Jun 18 13:42:55 xps15 dhcpcd[966]: wlp59s0: Router Advertisement from fe80::52d4:f7ff:fe82:8bed
Jun 18 13:42:55 xps15 dhcpcd[966]: wlp59s0: adding address fd1d:6b51:d6d0:0:263c:af2a:3665:3f3f/64
Jun 18 13:42:55 xps15 dhcpcd[966]: wlp59s0: adding route to fd1d:6b51:d6d0::/64
Jun 18 13:42:55 xps15 dhcpcd[966]: wlp59s0: soliciting a DHCPv6 lease
Jun 18 13:42:55 xps15 dhcpcd[966]: wlp59s0: carrier lost
Jun 18 13:42:55 xps15 dhcpcd[7244]: ps_bpf_recvbpf: Network is down
Jun 18 13:42:55 xps15 dhcpcd[7243]: ps_bpf_recvbpf: Network is down

graves501 · June 18, 2020, 11:49am

And this is the output for my ethernet connection:

Jun 18 13:47:00 xps15 dhcpcd[966]: ens20u1: adding default route via 192.168.1.1
Jun 18 13:47:02 xps15 dhcpcd[966]: ens20u1: pid 961 deleted IP address 192.168.1.220/24
Jun 18 13:47:02 xps15 dhcpcd[966]: ens20u1: deleting route to 192.168.1.0/24
Jun 18 13:47:02 xps15 dhcpcd[966]: ens20u1: deleting default route via 192.168.1.1
Jun 18 13:47:02 xps15 dhcpcd[966]: ens20u1: rebinding lease of 192.168.1.220
Jun 18 13:47:02 xps15 dhcpcd[966]: ens20u1: leased 192.168.1.220 for 43200 seconds
Jun 18 13:47:02 xps15 dhcpcd[966]: ens20u1: adding route to 192.168.1.0/24
Jun 18 13:47:02 xps15 dhcpcd[966]: ens20u1: adding default route via 192.168.1.1
Jun 18 13:47:03 xps15 dhcpcd[966]: ens20u1: pid 961 deleted default route via 192.168.1.1
Jun 18 13:47:04 xps15 dhcpcd[966]: ens20u1: adding route to fd1d:6b51:d6d0::/64
Jun 18 13:47:04 xps15 dhcpcd[966]: ens20u1: pid 0 deleted route to fd1d:6b51:d6d0::/64
Jun 18 13:47:04 xps15 dhcpcd[966]: ens20u1: pid 0 deleted address fd1d:6b51:d6d0:0:5c9:4d24:dff1:d8c4/64
Jun 18 13:47:04 xps15 dhcpcd[966]: ens20u1: adding route to fd1d:6b51:d6d0::/64
Jun 18 13:47:04 xps15 dhcpcd[966]: ens20u1: pid 961 deleted route to 192.168.1.0/24
Jun 18 13:47:04 xps15 dhcpcd[966]: ens20u1: pid 961 deleted route to fd1d:6b51:d6d0::/64
Jun 18 13:47:04 xps15 dhcpcd[966]: ens20u1: pid 961 deleted IP address 192.168.1.220/24
Jun 18 13:47:04 xps15 dhcpcd[966]: ens20u1: rebinding lease of 192.168.1.220
Jun 18 13:47:04 xps15 dhcpcd[966]: ens20u1: probing address 192.168.1.220/24
Jun 18 13:47:06 xps15 dhcpcd[966]: control command: dhcpcd ens20u1
Jun 18 13:47:06 xps15 dhcpcd[966]: ens20u1: adding route to fd1d:6b51:d6d0::/64
Jun 18 13:47:06 xps15 dhcpcd[966]: ens20u1: pid 0 deleted route to fd1d:6b51:d6d0::/64
Jun 18 13:47:06 xps15 dhcpcd[966]: ens20u1: pid 0 deleted address fd1d:6b51:d6d0:0:5c9:4d24:dff1:d8c4/64
Jun 18 13:47:06 xps15 dhcpcd[966]: ens20u1: adding route to fd1d:6b51:d6d0::/64
Jun 18 13:47:06 xps15 dhcpcd[966]: ens20u1: pid 961 deleted route to fd1d:6b51:d6d0::/64
Jun 18 13:47:08 xps15 dhcpcd[966]: ens20u1: adding route to fd1d:6b51:d6d0::/64
Jun 18 13:47:08 xps15 dhcpcd[966]: ens20u1: pid 0 deleted route to fd1d:6b51:d6d0::/64
Jun 18 13:47:08 xps15 dhcpcd[966]: ens20u1: pid 0 deleted address fd1d:6b51:d6d0:0:5c9:4d24:dff1:d8c4/64
Jun 18 13:47:08 xps15 dhcpcd[966]: ens20u1: adding route to fd1d:6b51:d6d0::/64
Jun 18 13:47:08 xps15 dhcpcd[966]: ens20u1: pid 961 deleted route to fd1d:6b51:d6d0::/64
Jun 18 13:47:09 xps15 dhcpcd[966]: ens20u1: leased 192.168.1.220 for 43200 seconds
Jun 18 13:47:09 xps15 dhcpcd[966]: ens20u1: adding route to 192.168.1.0/24
Jun 18 13:47:09 xps15 dhcpcd[966]: ens20u1: adding default route via 192.168.1.1
Jun 18 13:47:10 xps15 dhcpcd[966]: ens20u1: adding route to fd1d:6b51:d6d0::/64
Jun 18 13:47:10 xps15 dhcpcd[966]: ens20u1: pid 0 deleted route to fd1d:6b51:d6d0::/64
Jun 18 13:47:10 xps15 dhcpcd[966]: ens20u1: pid 0 deleted address fd1d:6b51:d6d0:0:5c9:4d24:dff1:d8c4/64
Jun 18 13:47:10 xps15 dhcpcd[966]: ens20u1: adding route to fd1d:6b51:d6d0::/64
Jun 18 13:47:10 xps15 dhcpcd[966]: ens20u1: pid 961 deleted route to 192.168.1.0/24
Jun 18 13:47:10 xps15 dhcpcd[966]: ens20u1: pid 961 deleted default route via 192.168.1.1
Jun 18 13:47:10 xps15 dhcpcd[966]: ens20u1: pid 961 deleted route to fd1d:6b51:d6d0::/64
Jun 18 13:47:10 xps15 dhcpcd[966]: ens20u1: pid 961 deleted IP address 192.168.1.220/24
Jun 18 13:47:10 xps15 dhcpcd[966]: ens20u1: rebinding lease of 192.168.1.220
Jun 18 13:47:10 xps15 dhcpcd[966]: ens20u1: probing address 192.168.1.220/24
Jun 18 13:47:12 xps15 dhcpcd[966]: ens20u1: adding route to fd1d:6b51:d6d0::/64
Jun 18 13:47:12 xps15 dhcpcd[966]: ens20u1: pid 0 deleted route to fd1d:6b51:d6d0::/64
Jun 18 13:47:12 xps15 dhcpcd[966]: ens20u1: pid 0 deleted address fd1d:6b51:d6d0:0:5c9:4d24:dff1:d8c4/64
Jun 18 13:47:12 xps15 dhcpcd[966]: ens20u1: adding route to fd1d:6b51:d6d0::/64
Jun 18 13:47:12 xps15 dhcpcd[966]: ens20u1: pid 961 deleted route to fd1d:6b51:d6d0::/64
Jun 18 13:47:14 xps15 dhcpcd[966]: ens20u1: adding route to fd1d:6b51:d6d0::/64
Jun 18 13:47:14 xps15 dhcpcd[966]: ens20u1: pid 0 deleted route to fd1d:6b51:d6d0::/64
Jun 18 13:47:14 xps15 dhcpcd[966]: ens20u1: pid 0 deleted address fd1d:6b51:d6d0:0:5c9:4d24:dff1:d8c4/64
Jun 18 13:47:14 xps15 dhcpcd[966]: ens20u1: adding route to fd1d:6b51:d6d0::/64

trendy · June 18, 2020, 12:29pm

There seem to be 2 instances of dhcpcd running at the same time.

ps -ef | grep -i dhcp

graves501 · June 18, 2020, 12:39pm

Hi trendy, thanks once again for your help. I think the problem is resolved... I killed the dhcpcd processes, restarted the dhcpcd service. It seems to work now. I'll keep testing for a bit. The whole thing might be docker related as well...

trendy · June 18, 2020, 12:42pm

Alright, do your testing and when your problem is solved, please consider marking this topic as [Solved]. See How to mark a topic as [Solved] for a short how-to.

graves501 · June 18, 2020, 12:46pm

Alright, I'm gonna test today and tomorrow. If all is fine and I can definitely pinpoint what the problem was I will mark the topic as solved. Once again, thank you very much trendy. Truly appreciated. Can I buy you a beer/coffee or something?

trendy · June 18, 2020, 12:49pm

You may donate to the project instead!

graves501 · June 18, 2020, 12:53pm

You may donate to the project instead!

Done!

graves501 · June 19, 2020, 9:49am

So, the problem after all was that I had multiple dhcpcd instances running. So it was not openWRT's fault at all. Once I kill the dhcpcd instances, the ethernet and Wi-Fi connections work. Now I need to research why these instances are spawn. Might be docker related.

Thanks to @trendy once again. This thread can now be closed, already marked as solved as well.