Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 356799 - gentoo.mirror.dkm.cz is unreachable with IPv6
Summary: gentoo.mirror.dkm.cz is unreachable with IPv6
Status: RESOLVED DUPLICATE of bug 356791
Alias: None
Product: Mirrors
Classification: Unclassified
Component: Server Problem (show other bugs)
Hardware: All Linux
: High normal
Assignee: Mirror Admins
URL: http://gentoo.mirror.dkm.cz
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-02-28 05:54 UTC by Michael Asthon
Modified: 2011-02-28 06:34 UTC (History)
0 users

See Also:
Package list:
Runtime testing required: ---

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Michael Asthon 2011-02-28 05:54:29 UTC 
Mirror gentoo.mirror.dkm.cz seems to be unreachable with IPv6, on any of these protocols:
icmp, http, ftp, rsync

The mirror is however marked as being IPv6 accessible: http://www.gentoo.org/main/en/mirrors2.xml

IPv6 address resolves OK:

$ host gentoo.mirror.dkm.cz
gentoo.mirror.dkm.cz is an alias for krtecek.dkm.cz.
krtecek.dkm.cz has address 86.49.49.49
krtecek.dkm.cz has IPv6 address 2001:470:1f0b:13d2::49

IPv4 accessibility is also ok.

Also, muni.cz is now IPv6 accessible (which is what emerge generally defaults to when other Czech mirrors fail) despite not being marked as such.

Reproducible: Always

Steps to Reproduce:
1. Add http://gentoo.mirror.dkm.cz/pub/gentoo/ as your first mirror in /etc/make.conf
2. Ensure you have functional IPv6 connectivity.
3. Try to emerge something (or run emerge --sync) - it will take a very long time before timeouting.



Expected Results:  
Ran emerge operation, instead it timeouts.
Comment 1 Matthew Thode ( prometheanfire ) archtester Gentoo Infrastructure gentoo-dev Security 2011-02-28 06:00:11 UTC 
another dupe of bug 356791
Comment 2 Myckel Habets 2011-02-28 06:34:54 UTC 
(In reply to comment #1)
> another dupe of bug 356791
> 

Thank you for your comment.

*** This bug has been marked as a duplicate of bug 356791 ***