[Bug 1412943] Re: security.ubuntu.com (2001:67c:1562::XXX) not reachable

2016-12-26 Thread Robie Basak
> and then you want me to send you mails while you are having working bugtracker where problems never get resolved. This is an infrastructure operational issue, not a bug in the update- manager package in Ubuntu. This bug tracker is used to track bugs in Ubuntu itself, not infrastructure issues.

[Bug 1412943] Re: security.ubuntu.com (2001:67c:1562::XXX) not reachable

2016-12-26 Thread Ivan Denkov
I will add comment. I just spin up a server on Linode, and stuck on security server - 0% [Connecting to security.ubuntu.com (2001:67c:1562::19)] This is a joke, and then you want me to send you mails while you are having working bugtracker where problems never get resolved. I should just use

[Bug 1412943] Re: security.ubuntu.com (2001:67c:1562::XXX) not reachable

2016-04-14 Thread Paul Gear
To any future readers of this bug: please do not add further comments here; instead, paste the output of the following commands into http://pastebin.ubuntu.com/: - ip -6 address - ip -6 route - host security.ubuntu.com # [or nslookup/dig if you don't have bind9-host installed] - mtr -r -c 10 [a

[Bug 1412943] Re: security.ubuntu.com (2001:67c:1562::XXX) not reachable via HE

2016-03-23 Thread Jared Fernandez
I'm using native dual-stack and not Hurricane Electric and I'm also not able to download from any of the IPv6 repos. I can ping them, but apt is not able to use them. ** Summary changed: - security.ubuntu.com (2001:67c:1562::XXX) not reachable via HE + security.ubuntu.com (2001:67c:1562::XXX)

[Bug 1412943] Re: security.ubuntu.com (2001:67c:1562::XXX) not reachable via HE

2016-02-17 Thread hgre
Ffrom Germany (Telekom) for i in $(dig +short security.ubuntu.com ); do ping6 -w5 $i; done PING 2001:67c:1562::13(2001:67c:1562::13) 56 data bytes 64 bytes from 2001:67c:1562::13: icmp_seq=1 ttl=56 time=113 ms 64 bytes from 2001:67c:1562::13: icmp_seq=2 ttl=56 time=114 ms 64 bytes from

[Bug 1412943] Re: security.ubuntu.com (2001:67c:1562::XXX) not reachable via HE

2016-01-17 Thread Haw Loeung
Is this still a problem? Using Hurricane Electric's looking glass (http://lg.he.net), it all seems to look fine. >From HE looking glass to 2001:67c:1562::/47 (US): | core1.fmt1.he.net> traceroute ipv6 2001:67c:1562::15 numeric | Hop Packet 1Packet 2Packet 3Hostname | 1

[Bug 1412943] Re: security.ubuntu.com (2001:67c:1562::XXX) not reachable via HE

2016-01-17 Thread Haw Loeung
>From HE Berlin, Frankfurt, and Prague: | core1.ber1.he.net> traceroute 2001:67c:1562::15 | Hop Packet 1Packet 2Packet 3Hostname | 1 10.403 ms 0.176 ms0.25 ms ge2-20.core1.ber1.he.net (2001:470:0:220::1) | 2 14.487 ms 54.885 ms 16.052

[Bug 1412943] Re: security.ubuntu.com (2001:67c:1562::XXX) not reachable via HE

2016-01-17 Thread Haw Loeung
> I'm not using HE. I tested it using Telekom + M-Net (Germany) and O2 + > UPC (Czech Republic), so we can basically say that it's not reachable > in at least large parts of Germany and Czech Republic. Marc Kolly (makuser), can you please provide output from mtr/traceroutes from both Telekom +

[Bug 1412943] Re: security.ubuntu.com (2001:67c:1562::XXX) not reachable via HE

2016-01-15 Thread Robie Basak
> Why won't Canonical do something about their routing and peerings Because nobody told Canonical, apparently. I have now filed an issue with Canonical IS (reference 87918). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu.

[Bug 1412943] Re: security.ubuntu.com (2001:67c:1562::XXX) not reachable via HE

2015-12-19 Thread Marc Kolly
This problem has been around since 2012 when they enabled IPv6 for their "core services". This: #241305 shows the development of the problem we face now. I'm not using HE. I tested it using Telekom + M-Net (Germany) and O2 + UPC (Czech Republic), so we can basically say that it's not reachable in

[Bug 1412943] Re: security.ubuntu.com (2001:67c:1562::XXX) not reachable via HE

2015-11-17 Thread bp-art
And still an issue as of Nov 17, 2015 Connecting to security.ubuntu.com (2001:67c:1562::17) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1412943 Title: security.ubuntu.com (2001:67c:1562::XXX)

[Bug 1412943] Re: security.ubuntu.com (2001:67c:1562::XXX) not reachable via HE

2015-09-08 Thread Zwylicht
for i in $(dig +short security.ubuntu.com ); do ping6 -w52 $i; done PING 2001:67c:1562::14(2001:67c:1562::14) 56 data bytes --- 2001:67c:1562::14 ping statistics --- 53 packets transmitted, 0 received, 100% packet loss, time 51999ms PING 2001:67c:1562::13(2001:67c:1562::13) 56 data bytes

[Bug 1412943] Re: security.ubuntu.com (2001:67c:1562::XXX) not reachable via HE

2015-09-07 Thread Zwylicht
Unfortunately 2001:67c:1360:8c01::18 is not working either.. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1412943 Title: security.ubuntu.com (2001:67c:1562::XXX) not reachable via HE To manage

[Bug 1412943] Re: security.ubuntu.com (2001:67c:1562::XXX) not reachable via HE

2015-01-25 Thread Andrew Skalski
I found a decent workaround: use the main server archive.ubuntu.com instead of the mirror. Notice how it includes only the known-good addresses; security.ubuntu.com includes a mix of good and bad hosts, and us.archive.ubuntu.com includes only the bad ones. $ dig +short archive.ubuntu.com

[Bug 1412943] Re: security.ubuntu.com (2001:67c:1562::XXX) not reachable via HE

2015-01-24 Thread Robert Penz
Yeah, a timeout with automatic fall back would be good. The web browsers do that. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1412943 Title: security.ubuntu.com (2001:67c:1562::XXX) not reachable

[Bug 1412943] Re: security.ubuntu.com (2001:67c:1562::XXX) not reachable via HE

2015-01-22 Thread Andrew Skalski
This affects all of the IPv6 addresses for us.archive.ubuntu.com as well (the addresses are mostly the same as security.ubuntu.com, excluding the two that actually work.) It would be less of a concern if apt automatically fell back on the IPv4 stack, but right now the only way for my machines to

[Bug 1412943] Re: security.ubuntu.com (2001:67c:1562::XXX) not reachable via HE

2015-01-22 Thread Colin Dearborn
Just to note that my native IPv6 connection does work, but my HE tunnel does not, so this does appear to be an issue with routing somewhere. Further, I seem to follow the same forward path on both services (from bost-b1-v6.telia.net on), so it appears to be on the return route: HE.net:

[Bug 1412943] Re: security.ubuntu.com (2001:67c:1562::XXX) not reachable via HE

2015-01-21 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: update-manager (Ubuntu) Status: New = Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1412943

[Bug 1412943] Re: security.ubuntu.com (2001:67c:1562::XXX) not reachable via HE

2015-01-20 Thread Robert Penz
Other people seem to have the same problem e.g. this blog post describes how to prefer IPv4 over IPv6 as security.ubuntu.com does not work http://zach-adams.com/2015/01/apt-get-cant-connect-to-security-ubuntu- fix/ -- You received this bug notification because you are a member of Ubuntu