One PC stops accessing internet and needs to re-enable eth0

Installing and Using OpenWrt
1

I'm experiencing a slight issue when i'm using Openwrt. I did not experience this when I used Opnsense ever. If I remove Openwrt and put Opnsense router the issue never appears.
Both my Openwrt and Opnsense are X86 and identical hw.
I'm not sure where to start looking into for troubleshooting.

he issue is, once a day or every couple of days my Linux Mint Pc with stop accessing internet. I looks like a DNS type issue. but if I disable the ethernet adapter on the pc and reenable it the issue goes away.
Both routers using Pihole.
While the pc is offline everything else in the house has internet access.

2

Does this PC use dhcp or static?

3

It uses dhcp.

4

When the issue happens check the settings on the PC:
ip addr; ip ro; ping -c 3 openwrt.org; ping -c 3 1.1.1.1

1 Like
5

Ok, this happened today and here is the last output of the command above.

root@mint-20: ip addr; ip ro; ping -c 3 openwrt.org; ping -c 3 1.1.1.1
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 
       valid_lft forever preferred_lft forever
2: enp1s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 1000
    link/ether 00:10:f3:89:d9:7e brd ff:ff:ff:ff:ff:ff
    inet 192.168.4.79/24 brd 192.168.4.255 scope global dynamic noprefixroute enp1s0
       valid_lft 31856sec preferred_lft 31856sec
    inet6 fd5f:2bcc:c3de:0:ecdd:6f40:a364:df0b/64 scope global temporary dynamic 
       valid_lft 587836sec preferred_lft 69116sec
    inet6 2600:1700:14b1:654f:ecdd:6f40:a364:df0b/64 scope global temporary dynamic 
       valid_lft 2403sec preferred_lft 2403sec
    inet6 2600:1700:14b1:654f:cd64:82d8:59c9:3ab4/64 scope global temporary deprecated dynamic 
       valid_lft 2403sec preferred_lft 0sec
    inet6 fd5f:2bcc:c3de:0:cd64:82d8:59c9:3ab4/64 scope global temporary deprecated dynamic 
       valid_lft 501758sec preferred_lft 0sec
    inet6 2600:1700:14b1:654f::ef9/128 scope global dynamic noprefixroute 
       valid_lft 2402sec preferred_lft 2402sec
    inet6 fd5f:2bcc:c3de::ef9/128 scope global noprefixroute 
       valid_lft forever preferred_lft forever
    inet6 fd5f:2bcc:c3de:0:29a0:a4a9:f802:c9a6/64 scope global temporary deprecated dynamic 
       valid_lft 415679sec preferred_lft 0sec
    inet6 fd5f:2bcc:c3de:0:fa0c:7a46:7cf0:a1a8/64 scope global mngtmpaddr noprefixroute 
       valid_lft forever preferred_lft forever
    inet6 2600:1700:14b1:654f:29a0:a4a9:f802:c9a6/64 scope global temporary deprecated dynamic 
       valid_lft 2403sec preferred_lft 0sec
    inet6 2600:1700:14b1:654f:51c6:493e:8fda:8468/64 scope global dynamic mngtmpaddr noprefixroute 
       valid_lft 2403sec preferred_lft 2403sec
    inet6 fe80::49cf:d5f1:cfb0:7b3c/64 scope link noprefixroute 
       valid_lft forever preferred_lft forever
3: enp0s31f6: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc fq_codel state DOWN group default qlen 1000
    link/ether 00:10:f3:89:d9:7d brd ff:ff:ff:ff:ff:ff
default via 192.168.4.1 dev enp1s0 proto dhcp metric 100 
169.254.0.0/16 dev enp1s0 scope link metric 1000 
192.168.4.0/24 dev enp1s0 proto kernel scope link src 192.168.4.79 metric 100 
ping: openwrt.org: Name or service not known
PING 1.1.1.1 (1.1.1.1) 56(84) bytes of data.
64 bytes from 1.1.1.1: icmp_seq=1 ttl=57 time=4.44 ms
64 bytes from 1.1.1.1: icmp_seq=2 ttl=57 time=4.01 ms
64 bytes from 1.1.1.1: icmp_seq=3 ttl=57 time=4.13 ms

--- 1.1.1.1 ping statistics ---
3 packets transmitted, 3 received, 0% packet loss, time 2003ms
rtt min/avg/max/mdev = 4.013/4.193/4.443/0.182 ms
6

You have some issue with DNS, internet is working fine.
Run this when the problem exists: cat /etc/resolv.conf ; resolvectl status

1 Like
7

Ok, will play will pihole and openwrt dns settings.

8

One wuick question, what does this mean?
" DNS Domain: ~."
I get this when I run the command "resolvectl status".

9
1 Like