Major resolve problems since upgrade to Mint 19

Questions about cabled networking
Forum rules
Before you post please read how to get help
Post Reply
bertdj
Level 1
Level 1
Posts: 6
Joined: Thu Aug 23, 2018 5:23 am

Major resolve problems since upgrade to Mint 19

Post by bertdj » Thu Aug 23, 2018 5:29 am

After upgrading to Mint 19, I'm experiencing major (domain) resolve problems.
Roughly 50% of all resolve requests fail, regardless the program/tool.

Some examples:
  • ping google.com will say "Network is unreachable",
  • loading a site in Firefox will say "Unable to connect",
  • Evolution will give error messages (about being unable to: load IMAP folders, send emails, etc).
I hope this is the correct place to report this problem.
If you need any information, such as the contents of files, let me know and I'll provide it.

Based on what it says here and here, I've already tried uncommenting "DNSSEC=no" in /etc/systemd/resolved.conf and then rebooting, but this doesn't fix the problem.

User avatar
catweazel
Level 17
Level 17
Posts: 7748
Joined: Fri Oct 12, 2012 9:44 pm
Location: Australian Antarctic Territory

Re: Major resolve problems since upgrade to Mint 19

Post by catweazel » Thu Aug 23, 2018 5:37 am

bertdj wrote:
Thu Aug 23, 2018 5:29 am
After upgrading to Mint 19, I'm experiencing major (domain) resolve problems.
Please post the output of this terminal command:

Code: Select all

inxi -Fxz
Enclose the results between [ⅽode] and [/ⅽode] code markers by selecting </> from the mini toolbar above the textbox where you type your reply.
¡uʍop ǝpısdn sı buıɥʇʎɹǝʌǝ os ɐıןɐɹʇsnɐ ɯoɹɟ ɯ,ı

bertdj
Level 1
Level 1
Posts: 6
Joined: Thu Aug 23, 2018 5:23 am

Re: Major resolve problems since upgrade to Mint 19

Post by bertdj » Thu Aug 23, 2018 5:53 am

Code: Select all

bert@bert-All-Series ~ $ inxi -Fxz
System:    Host: bert-All-Series Kernel: 4.15.0-32-generic x86_64
           bits: 64 gcc: 7.3.0
           Desktop: Xfce 4.12.3 (Gtk 2.24.31) Distro: Linux Mint 19 Tara
Machine:   Device: desktop System: ASUS product: All Series serial: N/A
           Mobo: ASUSTeK model: H81M-K v: Rev X.0x serial: N/A
           BIOS: American Megatrends v: 1103 date: 05/14/2015
CPU:       Dual core Intel Core i3-4160 (-MT-MCP-) 
           arch: Haswell rev.3 cache: 3072 KB
           flags: (lm nx sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx) bmips: 14367
           clock speeds: max: 3600 MHz 1: 1059 MHz 2: 1813 MHz 3: 1435 MHz
           4: 1829 MHz
Graphics:  Card: NVIDIA GT218 [GeForce 210] bus-ID: 01:00.0
           Display Server: x11 (X.Org 1.19.6 )
           drivers: nouveau (unloaded: modesetting,fbdev,vesa)
           Resolution: 1920x1080@60.00hz, 1920x1080@60.00hz
           OpenGL: renderer: NVA8 version: 3.3 Mesa 18.0.5 Direct Render: Yes
Audio:     Card-1 Intel 8 Series/C220 Series High Def. Audio Controller
           driver: snd_hda_intel bus-ID: 00:1b.0
           Card-2 NVIDIA High Def. Audio Controller
           driver: snd_hda_intel bus-ID: 01:00.1
           Sound: Advanced Linux Sound Architecture v: k4.15.0-32-generic
Network:   Card: Realtek RTL8111/8168/8411 PCIE Gigabit Ethernet Controller
           driver: r8169 v: 2.3LK-NAPI port: d000 bus-ID: 03:00.0
           IF: enp3s0 state: up speed: 1000 Mbps duplex: full mac: <filter>
Drives:    HDD Total Size: 1240.3GB (7.7% used)
           ID-1: /dev/sda model: KINGSTON_SHFS37A size: 240.1GB
           ID-2: USB /dev/sdb model: External_USB_3.0 size: 1000.2GB
Partition: ID-1: / size: 94G used: 85G (96%) fs: ext4 dev: /dev/sda5
           ID-2: swap-1 size: 4.23GB used: 0.03GB (1%)
           fs: swap dev: /dev/sda6
RAID:      No RAID devices: /proc/mdstat, md_mod kernel module present
Sensors:   System Temperatures: cpu: 29.8C mobo: 27.8C gpu: 53.0
           Fan Speeds (in rpm): cpu: 0
Info:      Processes: 219 Uptime: 2:54 Memory: 2066.2/3882.5MB
           Init: systemd runlevel: 5 Gcc sys: 7.3.0
           Client: Shell (bash 4.4.191) inxi: 2.3.56 
bert@bert-All-Series ~ $ 

User avatar
catweazel
Level 17
Level 17
Posts: 7748
Joined: Fri Oct 12, 2012 9:44 pm
Location: Australian Antarctic Territory

Re: Major resolve problems since upgrade to Mint 19

Post by catweazel » Thu Aug 23, 2018 6:00 am

bertdj wrote:
Thu Aug 23, 2018 5:53 am

Code: Select all

Network:   Card: Realtek RTL8111/8168/8411 PCIE Gigabit Ethernet Controller
           driver: r8169 v: 2.3LK-NAPI port: d000 bus-ID: 03:00.0
           IF: enp3s0 state: up speed: 1000 Mbps duplex: full mac: <filter>
You might try rebooting your router. Switch it off for a few minutes then switch it back on.
¡uʍop ǝpısdn sı buıɥʇʎɹǝʌǝ os ɐıןɐɹʇsnɐ ɯoɹɟ ɯ,ı

bertdj
Level 1
Level 1
Posts: 6
Joined: Thu Aug 23, 2018 5:23 am

Re: Major resolve problems since upgrade to Mint 19

Post by bertdj » Thu Aug 23, 2018 8:27 am

My PC and the router have been reset several times since the upgrade to Mint 19.
I've had the resolve problems for weeks now; slowly driving me crazy...

I've been running more tests and I've discovered three new things about the unfortunate situation my system is in:
1. If I wait 2 seconds or more before (re)running ping google.com, it consistently fails with "Network is unreachable".
2. Quickly running a new ping after the failure always results in a successful ping.
3. I almost never use Chrome. I recently started using it and, to my surprise, noticed it never has the resolve problems. So far, this is the only program I've found that doesn't have the problem. Even if I disable "Use a prediction service to load pages more quickly" it doesn't have the problem.

Both (1 and 2 combined) and (3) seem peculiar enough to me that I'm hoping someone will recognize this behavior...

sgtor
Level 3
Level 3
Posts: 163
Joined: Sat May 13, 2017 9:39 pm

Re: Major resolve problems since upgrade to Mint 19

Post by sgtor » Thu Aug 23, 2018 8:50 am

For chrome to work without error suggests the problem is not Mint itself but something else, yet pinging is sporadic, which can be normal under certain circumstances.

So try some of these things to get a bigger picture of what is happening.

If you ping your router what happens?

And also is there a way on your router to ping some sites from the router?
Go into your router settings and see if that is available as an option.

The results of a traceroute would be helpful as well.

Might need to install it

Code: Select all

sudo apt install traceroute
the run it on a few different sites

Code: Select all

traceroute google.com

Code: Select all

traceroute yahoo.com

Code: Select all

traceroute amazon.com
etc,etc

If you could run these on the router as well that would be an even bigger help but if not that's fine.

Also I wonder what your firewall settings are
just type firewall from from the main menu and look in there.
Running iptables from the command line would show more but that's a lot of text to post here.

sgtor
Level 3
Level 3
Posts: 163
Joined: Sat May 13, 2017 9:39 pm

Re: Major resolve problems since upgrade to Mint 19

Post by sgtor » Thu Aug 23, 2018 9:01 am

Oh yeah I almost forgot you need to check if your IP is static or set with DHCP. It could be possible that your IP address is conflicting with the same IP on another device. If it's set static on any device that could be the culprit. The easiest way to do that is just type "network connections" (without quotes) in the main menu and look in there. Then check other devices as well.

bertdj
Level 1
Level 1
Posts: 6
Joined: Thu Aug 23, 2018 5:23 am

Re: Major resolve problems since upgrade to Mint 19

Post by bertdj » Thu Aug 23, 2018 9:06 am

Thank you both for trying to help.
sgtor wrote:
Thu Aug 23, 2018 8:50 am
If you ping your router what happens?

Code: Select all

bert@bert-All-Series ~ $ ip r
default via 10.0.0.254 dev enp3s0 proto dhcp metric 100 
10.0.0.0/24 dev enp3s0 proto kernel scope link src 10.0.0.11 metric 100 
169.254.0.0/16 dev enp3s0 scope link metric 1000 

bert@bert-All-Series ~ $ ping 10.0.0.254
PING 10.0.0.254 (10.0.0.254) 56(84) bytes of data.
64 bytes from 10.0.0.254: icmp_seq=1 ttl=64 time=0.354 ms
64 bytes from 10.0.0.254: icmp_seq=2 ttl=64 time=0.283 ms
64 bytes from 10.0.0.254: icmp_seq=3 ttl=64 time=0.289 ms
64 bytes from 10.0.0.254: icmp_seq=4 ttl=64 time=0.319 ms
etc.
sgtor wrote:
Thu Aug 23, 2018 8:50 am

Code: Select all

traceroute google.com

Code: Select all

bert@bert-All-Series ~ $ traceroute google.com
traceroute to google.com (2a00:1450:4013:c06::65), 30 hops max, 80 byte packets
connect: Network is unreachable
(Running it again...)

Code: Select all

bert@bert-All-Series ~ $ traceroute google.com
traceroute to google.com (172.217.20.110), 30 hops max, 60 byte packets
 1  _gateway (10.0.0.254)  0.383 ms  0.418 ms  0.466 ms
 2  <...> (<ip>)  1.582 ms  1.629 ms  1.762 ms
 3  10.101.84.1 (10.101.84.1)  7.919 ms  7.823 ms  7.848 ms
 4  212.142.51.213 (212.142.51.213)  7.998 ms  8.356 ms  8.376 ms
 5  asd-tr0021-cr101-bundle-ether109-1.aorta.net (84.116.244.33)  10.611 ms  14.920 ms  14.900 ms
 6  nl-ams02a-rc2-lag-5-0.aorta.net (84.116.135.33)  14.871 ms  9.898 ms  9.676 ms
 7  nl-ams14a-ri1-ae5-0.aorta.net (84.116.135.34)  10.818 ms  10.765 ms  10.714 ms
 8  74.125.146.228 (74.125.146.228)  10.822 ms  10.886 ms  11.121 ms
 9  108.170.241.225 (108.170.241.225)  12.711 ms 108.170.241.193 (108.170.241.193)  11.474 ms 108.170.241.225 (108.170.241.225)  12.723 ms
10  209.85.240.115 (209.85.240.115)  11.363 ms  11.517 ms 209.85.240.31 (209.85.240.31)  11.461 ms
11  fra02s28-in-f14.1e100.net (172.217.20.110)  11.140 ms  11.045 ms  11.046 ms
bert@bert-All-Series ~ $ 
sgtor wrote:
Thu Aug 23, 2018 8:50 am

Code: Select all

traceroute yahoo.com

Code: Select all

bert@bert-All-Series ~ $ traceroute yahoo.com
traceroute to yahoo.com (2001:4998:44:41d::4), 30 hops max, 80 byte packets
connect: Network is unreachable
sgtor wrote:
Thu Aug 23, 2018 8:50 am

Code: Select all

traceroute amazon.com

Code: Select all

bert@bert-All-Series ~ $ traceroute amazon.com
amazon.com: No address associated with hostname
Cannot handle "host" cmdline arg `amazon.com' on position 1 (argc 1)
sgtor wrote:
Thu Aug 23, 2018 8:50 am
Also I wonder what your firewall settings are [...] Running iptables from the command line would show more but that's a lot of text to post here.

Code: Select all

bert@bert-All-Series ~ $ sudo iptables -vL -t filter
Chain INPUT (policy ACCEPT 2113 packets, 1799K bytes)
 pkts bytes target     prot opt in     out     source               destination         

Chain FORWARD (policy ACCEPT 0 packets, 0 bytes)
 pkts bytes target     prot opt in     out     source               destination         

Chain OUTPUT (policy ACCEPT 2017 packets, 225K bytes)
 pkts bytes target     prot opt in     out     source               destination         
bert@bert-All-Series ~ $ sudo iptables -vL -t nat
Chain PREROUTING (policy ACCEPT 0 packets, 0 bytes)
 pkts bytes target     prot opt in     out     source               destination         

Chain INPUT (policy ACCEPT 0 packets, 0 bytes)
 pkts bytes target     prot opt in     out     source               destination         

Chain OUTPUT (policy ACCEPT 0 packets, 0 bytes)
 pkts bytes target     prot opt in     out     source               destination         

Chain POSTROUTING (policy ACCEPT 0 packets, 0 bytes)
 pkts bytes target     prot opt in     out     source               destination         
bert@bert-All-Series ~ $ sudo iptables -vL -t mangle
Chain PREROUTING (policy ACCEPT 0 packets, 0 bytes)
 pkts bytes target     prot opt in     out     source               destination         

Chain INPUT (policy ACCEPT 0 packets, 0 bytes)
 pkts bytes target     prot opt in     out     source               destination         

Chain FORWARD (policy ACCEPT 0 packets, 0 bytes)
 pkts bytes target     prot opt in     out     source               destination         

Chain OUTPUT (policy ACCEPT 0 packets, 0 bytes)
 pkts bytes target     prot opt in     out     source               destination         

Chain POSTROUTING (policy ACCEPT 0 packets, 0 bytes)
 pkts bytes target     prot opt in     out     source               destination         
bert@bert-All-Series ~ $ sudo iptables -vL -t raw
Chain PREROUTING (policy ACCEPT 0 packets, 0 bytes)
 pkts bytes target     prot opt in     out     source               destination         

Chain OUTPUT (policy ACCEPT 0 packets, 0 bytes)
 pkts bytes target     prot opt in     out     source               destination         
bert@bert-All-Series ~ $ sudo iptables -vL -t security
Chain INPUT (policy ACCEPT 0 packets, 0 bytes)
 pkts bytes target     prot opt in     out     source               destination         

Chain FORWARD (policy ACCEPT 0 packets, 0 bytes)
 pkts bytes target     prot opt in     out     source               destination         

Chain OUTPUT (policy ACCEPT 0 packets, 0 bytes)
 pkts bytes target     prot opt in     out     source               destination         
bert@bert-All-Series ~ $ 

User avatar
Joe2Shoe
Level 4
Level 4
Posts: 351
Joined: Wed Oct 18, 2017 8:12 pm
Location: Ozone

Re: Major resolve problems since upgrade to Mint 19

Post by Joe2Shoe » Thu Aug 23, 2018 9:17 am

Did you upgrade per Clem's directions? A clean install is always best.
"Tolerance is the refuge of men without conviction."
"Common sense is not so common" - Voltaire

sgtor
Level 3
Level 3
Posts: 163
Joined: Sat May 13, 2017 9:39 pm

Re: Major resolve problems since upgrade to Mint 19

Post by sgtor » Thu Aug 23, 2018 11:58 am

If you ping your router it seems to work fine so the connection from computer to router doesn't seem to be the issue. Although that's not really enough testing to be conclusive, but it's good enough to say for now the problem is probably in the router.

Go into the router settings and renew the ip address to the DHCP server from your ISP.
If that doesn't work try turning off both the ISP modem and your router.

The turn on the modem and wait for it to finish booting up.

Then turn on the router.

sgtor
Level 3
Level 3
Posts: 163
Joined: Sat May 13, 2017 9:39 pm

Re: Major resolve problems since upgrade to Mint 19

Post by sgtor » Thu Aug 23, 2018 12:05 pm

BTW
your firewall settings look a bit odd. Your policy for both INPUT and FORWARD is accept and there are no rules in either of them. So how are you blocking incoming packets?

Norbert
Level 1
Level 1
Posts: 4
Joined: Wed Jul 09, 2014 5:23 pm

Re: Major resolve problems since upgrade to Mint 19

Post by Norbert » Sat Oct 13, 2018 4:57 pm

I have the exact same problem with a fresh install - so no upgrade - of Mint 19 Xfce edition.
Is there a solution?

Norbert
Level 1
Level 1
Posts: 4
Joined: Wed Jul 09, 2014 5:23 pm

Re: Major resolve problems since upgrade to Mint 19

Post by Norbert » Sun Oct 14, 2018 9:53 am

For some reason it seems the network connection needs constant wake-up calls.
If in the last second or so you haven't accessed the Internet, it needs a single call to get started.
For example, ping google.com will fail, but then immediately ping yahoo.com will work, even though it's a different domain/IP.
The same happens with visiting websites, to reach linuxmint.com I first need to briefly do a failed attempt to access anything else, e.g. cnn.com.
Or just access linuxmint.com twice in a row, of course, to make the second access work.

sgtor
Level 3
Level 3
Posts: 163
Joined: Sat May 13, 2017 9:39 pm

Re: Major resolve problems since upgrade to Mint 19

Post by sgtor » Tue Oct 16, 2018 12:35 am

By any chance do you have UPnP enabled on the router? If you do try turning it off then rebooting(not power cycling) the router. Also turn off any DDOS protection type settings.
And possibly try turning on IPv6.

I had the same problem recently after installing Debian 9.5 Mate as a dual boot system and Debian was doing this, then when I booted back into mint it was also doing it so I knew it was the router. I'm not sure which one is causing the problem or if it's all together because I haven't had the time to test it further and now it just works. UPnP is a security risk anyway so turning it off is fine for me. The DDOS is an interesting one since on my router it's only supposed to block WAN traffic not LAN traffic.

bertdj
Level 1
Level 1
Posts: 6
Joined: Thu Aug 23, 2018 5:23 am

Re: Major resolve problems since upgrade to Mint 19

Post by bertdj » Tue Oct 16, 2018 3:08 am

When I moved from Mint 18.3 to Mint 19, my router didn't change, Mint changed.

sgtor
Level 3
Level 3
Posts: 163
Joined: Sat May 13, 2017 9:39 pm

Re: Major resolve problems since upgrade to Mint 19

Post by sgtor » Wed Oct 17, 2018 5:02 pm

bertdj wrote:
Tue Oct 16, 2018 3:08 am
When I moved from Mint 18.3 to Mint 19, my router didn't change, Mint changed.
When I installed Debian 9.5 on another partition I didn't change my Mint 19 install yet the problems started in Mint also

Norbert
Level 1
Level 1
Posts: 4
Joined: Wed Jul 09, 2014 5:23 pm

Re: Major resolve problems since upgrade to Mint 19

Post by Norbert » Sun Oct 21, 2018 8:16 pm

I've been able to fix the problems! :)

I always use a /home/norbert/.hosts file with ln -s to /etc/hosts.
(Personal preference, related to how I (frequently) edit the file.)
Apparently Mint 19 doesn't like this set up.
As soon as moved back ~/.hosts to /etc/hosts the problems disappeared.

bertdj
Level 1
Level 1
Posts: 6
Joined: Thu Aug 23, 2018 5:23 am

Re: Major resolve problems since upgrade to Mint 19

Post by bertdj » Mon Oct 29, 2018 4:19 am

Same solution (changing symbolic link to file) worked here.

Post Reply

Return to “Ethernet”