1 |
On Monday, 13 January 2020 11:00:23 GMT Dale wrote: |
2 |
> Dale wrote: |
3 |
|
4 |
> Well, this has to be fixed or turned off completely. When I try to |
5 |
> emerge and it tries to download new packages, it is trying to use IPv6 |
6 |
> addresses which fail. It spits out this: |
7 |
> >>> Downloading |
8 |
> |
9 |
> 'https://mirrors.evowise.com/gentoo/distfiles/38/kjobwidgets-5.66.0.tar.xz' |
10 |
> --2020-01-13 04:49:25-- |
11 |
> https://mirrors.evowise.com/gentoo/distfiles/38/kjobwidgets-5.66.0.tar.xz |
12 |
> Resolving mirrors.evowise.com... 2606:4700:1::6813:894b, |
13 |
> 2606:4700:1::6813:8b4b, 2606:4700:1::6813:8a4b, ... |
14 |
> Connecting to mirrors.evowise.com|2606:4700:1::6813:894b|:443... failed: |
15 |
> No route to host. |
16 |
|
17 |
--->8 |
18 |
|
19 |
> It seems that I need IPv6 to work or to disable it until I can. |
20 |
> |
21 |
> Any ideas? |
22 |
|
23 |
It seems that upstream is detecting IPv6 addresses on your network and so |
24 |
prefers it to v4. I dare say someone more knowlegeable in v6 than me could |
25 |
tell you how to remove v6 routes and addresses from your interface. |
26 |
|
27 |
What are you using as name service? You need some way to tell it not to use |
28 |
IPv6. And neither /etc/hosts nor /etc/conf.d/net should mention v6 either. If |
29 |
you didn't mind rebooting, you could remove v6 support from the kernel with a |
30 |
single N*; then the net wouldn't have any v6 support and upstream wouldn't try |
31 |
to use it. |
32 |
|
33 |
* Networking Support > Networking Options > The IPv6 protocol. |
34 |
|
35 |
-- |
36 |
Regards, |
37 |
Peter. |