On 04/07/18 13:09, Adam Carter wrote: > > Since you know the server IPs, and there's only a small number so > you could try connection to each of them and see which one(s) fail. > > Or tcpdump, or netstat etc. > > > FWIW i can route to all the v4 addresses; > > # for i in 18.9.60.141 18.191.65.131 37.191.226.104 92.43.111.21 > 193.164.133.100 216.66.15.2 ; do nc -zv $i 443; done > cryptonomicon.mit.edu <http://cryptonomicon.mit.edu> [18.9.60.141] 443 > (https) open > ec2-18-191-65-131.us-east-2.compute.amazonaws.com > <http://ec2-18-191-65-131.us-east-2.compute.amazonaws.com> > [18.191.65.131] 443 (https) open > host-37-191-226-104.lynet.no <http://host-37-191-226-104.lynet.no> > [37.191.226.104] 443 (https) open > Warning: forward host lookup failed for oteiza.siccegge.de > <http://oteiza.siccegge.de>: > oteiza.siccegge.de <http://oteiza.siccegge.de> [92.43.111.21] 443 > (https) open > DNS fwd/rev mismatch: mail.b4ckbone.de <http://mail.b4ckbone.de> != > beta.b4ckbone.de <http://beta.b4ckbone.de> > mail.b4ckbone.de <http://mail.b4ckbone.de> [193.164.133.100] 443 > (https) open > zimmermann.mayfirst.org <http://zimmermann.mayfirst.org> [216.66.15.2] > 443 (https) open > I tried the host hack - still fails though a different message. I suspect the keyservers are not the problem because:
"gpg --homedir /var/lib/gentoo/gkeys/keyrings/gentoo/release --refresh-keys" mostly works fine (with or without the hosts hack). But I have never had a successful run with emerge --sync Portage is sys-apps/portage-2.3.40-r1 Bug or what? BillK
