On Monday, 13 January 2020 15:26:47 GMT Peter Humphrey wrote: > On Monday, 13 January 2020 11:00:23 GMT Dale wrote: > > Dale wrote: > > > > Well, this has to be fixed or turned off completely. When I try to > > emerge and it tries to download new packages, it is trying to use IPv6 > > > > addresses which fail. It spits out this: > > >>> Downloading > > > > 'https://mirrors.evowise.com/gentoo/distfiles/38/kjobwidgets-5.66.0.tar.xz > > ' > > --2020-01-13 04:49:25-- > > https://mirrors.evowise.com/gentoo/distfiles/38/kjobwidgets-5.66.0.tar.xz > > Resolving mirrors.evowise.com... 2606:4700:1::6813:894b, > > 2606:4700:1::6813:8b4b, 2606:4700:1::6813:8a4b, ... > > Connecting to mirrors.evowise.com|2606:4700:1::6813:894b|:443... failed: > > No route to host. > > --->8 > > > It seems that I need IPv6 to work or to disable it until I can. > > > > Any ideas? > > It seems that upstream is detecting IPv6 addresses on your network and so > prefers it to v4. I dare say someone more knowlegeable in v6 than me could > tell you how to remove v6 routes and addresses from your interface.
Why should he? Wouldn't it be preferable to configure IPv6 routing correctly so he can connect to IPv6 hosts and so get his money back from all this modem+router extravagance of the year? :-) > What are you using as name service? You need some way to tell it not to use > IPv6. And neither /etc/hosts nor /etc/conf.d/net should mention v6 either. > If you didn't mind rebooting, you could remove v6 support from the kernel > with a single N*; then the net wouldn't have any v6 support and upstream > wouldn't try to use it. > > * Networking Support > Networking Options > The IPv6 protocol. The evowise.com DNS has a valid AAAA record: $ dig @8.8.8.8 evowise.com AAAA ; <<>> DiG 9.14.8 <<>> @8.8.8.8 evowise.com AAAA ; (1 server found) ;; global options: +cmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 15906 ;; flags: qr rd ra; QUERY: 1, ANSWER: 5, AUTHORITY: 0, ADDITIONAL: 1 ;; OPT PSEUDOSECTION: ; EDNS: version: 0, flags:; udp: 512 ;; QUESTION SECTION: ;evowise.com. IN AAAA ;; ANSWER SECTION: evowise.com. 299 IN AAAA 2606:4700:1::6813:874b evowise.com. 299 IN AAAA 2606:4700:1::6813:8b4b evowise.com. 299 IN AAAA 2606:4700:1::6813:884b evowise.com. 299 IN AAAA 2606:4700:1::6813:8a4b evowise.com. 299 IN AAAA 2606:4700:1::6813:894b ;; Query time: 41 msec ;; SERVER: 8.8.8.8#53(8.8.8.8) ;; WHEN: Mon Jan 13 16:15:32 GMT 2020 ;; MSG SIZE rcvd: 180 Traceroute would show at what point Dale's setup fails to route packets. I don't have an IPv6 router to be able to look into this further, but someone who does could perhaps advise. -- Regards, Mick
signature.asc
Description: This is a digitally signed message part.
