Upgrade to 20.04.1 no internet

[Chris]

On Sat, 2020-10-03 at 20:37 +1000, Karl Auer wrote:
> On Sat, 2020-10-03 at 11:07 +0100, Colin Law wrote:
> > I think the errors are to do with IPV6.  Have you been playing with
> > IPV6?  How have you got V6 configured in the network manager
> > settings
> > for the connection.
> 
> It's quite rare that IPv6 screws with anything these days. People
> tend
> to either have it and it just works, or they don't have it. Because
> almost everything tries IPv6 first, it's common to see lots of IPv6
> "error messages" on systems with no IPv6 connectivity.
> 
> Otherwise I'm with Colin - settings rather than a defect.
> 
> This is a wild shot in the dark, but those "trust chain broken"
> messages could be evidence of a clock issue (the crypto protecting
> most
> major domains these days relies on agreed time). Make sure your
> computer time is set correctly. If you have a local resolver on your
> network, make sure its time is set correctly too. Though it would be
> a
> bit odd for the time to differ between the live CD and the real
> system.
Doing a search through my hourly syslog snippets I found that the
"trust chain broken" issues has gone away since 4am this morning.

> 
> Looking at that log, this feels like a DNS or routing issue, not a
> hardware issue (except for the time, maybe). On a different computer,
> look up www.google.com and try pinging its IPv4 address (or any of
> its
> IPv4 addresses) from the problem child. If the ping gets there, you
> have a DNS problem. If the ping doesn't get there, we can look
> further...
I pinged several of google's V4 addresses and several others, here are
the results:

Google:
ping -c5 209.85.128.0
PING 209.85.128.0 (209.85.128.0) 56(84) bytes of data.

--- 209.85.128.0 ping statistics ---
5 packets transmitted, 0 received, 100% packet loss, time 4076ms

chris at localhost:~$ ping -c5 google.com
PING google.com (142.250.68.174) 56(84) bytes of data.
64 bytes from 142.250.68.174 (142.250.68.174): icmp_seq=1 ttl=119
time=25.4 ms
64 bytes from 142.250.68.174 (142.250.68.174): icmp_seq=2 ttl=119
time=24.6 ms
64 bytes from 142.250.68.174 (142.250.68.174): icmp_seq=3 ttl=119
time=47.0 ms
64 bytes from 142.250.68.174 (142.250.68.174): icmp_seq=4 ttl=119
time=55.7 ms
64 bytes from 142.250.68.174 (142.250.68.174): icmp_seq=5 ttl=119
time=24.7 ms

Another Google V4 IP
chris at localhost:~$ ping -c5 216.239.32.0
PING 216.239.32.0 (216.239.32.0) 56(84) bytes of data.

--- 216.239.32.0 ping statistics ---
5 packets transmitted, 0 received, 100% packet loss, time 4101ms

chris at localhost:~$ ping -c5 amazon.com
ping: amazon.com: Name or service not known

chris at localhost:~$ ping -c5 amazon.com
PING amazon.com (176.32.103.205) 56(84) bytes of data.
64 bytes from 176.32.103.205 (176.32.103.205): icmp_seq=1 ttl=239
time=58.3 ms
64 bytes from 176.32.103.205 (176.32.103.205): icmp_seq=2 ttl=239
time=58.3 ms
64 bytes from 176.32.103.205 (176.32.103.205): icmp_seq=3 ttl=239
time=58.5 ms
64 bytes from 176.32.103.205 (176.32.103.205): icmp_seq=4 ttl=239
time=58.2 ms
64 bytes from 176.32.103.205 (176.32.103.205): icmp_seq=5 ttl=239
time=58.0 ms

--- amazon.com ping statistics ---
5 packets transmitted, 5 received, 0% packet loss, time 4004ms
rtt min/avg/max/mdev = 58.004/58.269/58.477/0.154 ms

Why Amazon is not found one minute and a successful ping the next I
have no idea.

> 
> Regards, K.
> 
> -- 
> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
> ~~
> Karl Auer (kauer at biplane.com.au)
> http://www.biplane.com.au/kauer
> 
> GPG fingerprint: 2561 E9EC D868 E73C 8AF1 49CF EE50 4B1D CCA1 5170
> Old fingerprint: 8D08 9CAA 649A AFEF E862 062A 2E97 42D4 A2A0 616D
> 
> 
> 
> 

-- 
Chris
31.11972; -97.90167 (Elev. 1092 ft)
09:22:55 up 9:38, 1 user, load average: 1.13, 1.12, 1.13
Description:	Ubuntu 20.04.1 LTS, kernel 5.4.0-48-generic