squalou's questions

Running on 18.04, when trying sudo do-release-upgrade -d I get following error :

authenticate 'focal.tar.gz' against 'focal.tar.gz.gpg' 
Authentication failed
Authenticating the upgrade failed. There may be a problem with the network or with the server. 

I've seen numerous posts akgin to reinstall sudo apt-get install --reinstall ubuntu-keyring

Which I did, with no result.

I manually downloaded focal.tar.gz and focal.tar.gz.gpg from http://mirrors.linode.com/ubuntu/dists/focal-proposed/main/dist-upgrader-all/20.04.18/

I did run a gpg check

gpg --receive-keys 871920D1991BC93C
gpg --receive-keys 3B4FE6ACC0B21F32
gpg --verify focal.tar.gz.gpg focal.tar.gz

Looks succesful (with warnings, but at least it matches)

gpg: Signature made mer. 08 avril 2020 19:38:12 CEST
gpg:                using RSA key 3B4FE6ACC0B21F32
gpg: Good signature from "Ubuntu Archive Automatic Signing Key (2012) <[email protected]>" [unknown]
gpg: WARNING: This key is not certified with a trusted signature!
gpg:          There is no indication that the signature belongs to the owner.
Primary key fingerprint: 790B C727 7767 219C 42C8  6F93 3B4F E6AC C0B2 1F32
gpg: Signature made mer. 08 avril 2020 19:38:12 CEST
gpg:                using RSA key 871920D1991BC93C
gpg: Good signature from "Ubuntu Archive Automatic Signing Key (2018) <[email protected]>" [unknown]
gpg: WARNING: This key is not certified with a trusted signature!
gpg:          There is no indication that the signature belongs to the owner.
Primary key fingerprint: F6EC B376 2474 EDA9 D21B  7022 8719 20D1 991B C93C

No idea what I could try to make the upgrade accept the file, and the process to go on.

I do not wish to follow this suggestion : change manually the sources definition, https://stackoverflow.com/questions/62388015/authenticating-the-upgrade-failed-there-may-be-a-problem-with-the-network-or-wi

I'm running this ubuntu machine as a 'maintainability test for any user', so my challenge here is not to tweak around. For that, my main pc runs arch ;)

So, I'm looking for a way as easy to explain and reproduce as possible to solve this.

Thank you !

Note

I could manually tinker with apt-key

gpg --receive-keys 3B4FE6ACC0B21F32
gpg --receive-keys 871920D1991BC93C
gpg --export  790BC7277767219C42C86F933B4FE6ACC0B21F32 > 1.gpg
gpg --export  F6ECB3762474EDA9D21B7022871920D1991BC93C > 2.gpg
sudo apt-key add 1.gpg
sudo apt-key add 2.gpg

but that's not something I should do .... is it ? And even so, it fails later on with

Updating repository information
Hit http://www-ftp.lip6.fr/pub/linux/distributions/Ubuntu/archive focal InRelease                                                                                                                                 
Hit http://www-ftp.lip6.fr/pub/linux/distributions/Ubuntu/archive focal-security InRelease                                                                                                                        
Hit http://archive.canonical.com/ubuntu focal InRelease                                                                                                                                                           
Fetched 0 B in 0s (0 B/s)   

(appstreamcli:1444): GLib-CRITICAL **: 19:08:37.593: g_variant_builder_end: assertion '!GVSB(builder)->uniform_item_types || GVSB(builder)->prev_item_type != NULL || g_variant_type_is_definite (GVSB(builder)->type)' failed

(appstreamcli:1444): GLib-CRITICAL **: 19:08:37.593: g_variant_new_variant: assertion 'value != NULL' failed

(appstreamcli:1444): GLib-ERROR **: 19:08:37.594: g_variant_new_parsed: 11-13:invalid GVariant format string
Trace/breakpoint trap (core dumped)

I sure can wait for 20.04.1 release but... that's a weird behaviour.

Looks like repo info is not found see Fetched 0 B in 0s (0 B/s) but when I manually browse the repo, things are there.

I did open this question a few weeks ago already : 18.04 VPN l2tp issue - connects but no access to resources

I'm still investigating but so far here are my findings :

• used to work with 16.04
• works on Debian stretch
• works on Debian testing
• works on Arch
• fails on Mint 18.04
• fails on Fedora 28

It is exactly this issue also : https://bbs.archlinux.org/viewtopic.php?pid=1802711#p1802711

Now, does anyone has the slightest idea how to see differences between Debian on which Ubuntu are based, and Ubuntu ? This is a very tricky network issue, maybe a net guru will step by ...

I've already updated xl2tpd to circumvent the 'kernel 4.15' issues. I've updated anything I could. I've followed 'ip routing' magic trick : no better result.

What the hell can be broken in this distrib ...

regards.

My network setup is somewhat complex, so let's explain it.

But first keep in mind that everything works perfectly with ubuntu 16.04, nixOs, several flavours of Arch based distribs, and windows 10.

here it is :

[HOME NETWORK] <--l2tp-ipsec-VPN---> [OFFICE NETWORK - with a DNS] <---Site2SiteVPN----> [some other cloud resource]

Expected result example :

• establish vpn connection from home to office
• acquire an IP in the expected range (172. instead of 192..., )
• obtain a correct DNS config
• SSH or HTTPS to "some other cloud resource" => SHOULD work

On Ubuntu 18.04 :

sudo apt-get install network-manager-l2tp-gnome

then configure connexion, connect : Yeah ! the 'lock' appears near the network icon. Looks promising so far.

A new interface ppp0 appears, with an IP that seems OK

When checking 'whatsmyip.org' it now displays my office IP. Looks fine

ip addr
...
...
12: ppp0: <POINTOPOINT,MULTICAST,NOARP,UP,LOWER_UP> mtu 1400 qdisc fq_codel state UNKNOWN group default qlen 3
  link/ppp
  inet 172.x.x.x peer 172.255.255.0/32 scope global ppp0

Now here is the issue : - impossible to reach any resource on "some other cloud resource"

http connecion times out, ssh does never answer. ...

I saw this issue on 3 different PCs, from 2 different locations. All of them used to work with 16.04.

Connexion IS established, no error appear on vpn server, or on networkmanager logs, but it's as if all connexions were not using the ppp0 interface.

Made me think of some kind on 'connexion priority' but I didn't find any way to play with that.

Any suggestion would be highly welcome.

Thanks!

PS : I also checked with 'route' command : ppp0 appears with top priority