Sorry, you need to enable JavaScript to visit this website.

Primary tabs

download.01.org IPv6 address unreachable

5 posts / 0 new
01 Staff's picture
Starter
01 Staff (not verified)

May 02, 2013 - 04:19am

  • 01 Staff's picture
    01 Staff (not verified)
    $ ping6 -c10 download.01.org
    PING download.01.org(2001:19d0:3:5::106) 56 data bytes
    From 2001:19d0:2:5::2 icmp_seq=1 Destination unreachable: Address unreachable
    From 2001:19d0:2:5::2 icmp_seq=5 Destination unreachable: Address unreachable
    From 2001:19d0:2:5::2 icmp_seq=9 Destination unreachable: Address unreachable
    
    --- download.01.org ping statistics ---
    10 packets transmitted, 0 received, +3 errors, 100% packet loss, time 9055ms
    
    

    So when IPv6 is preferred over IPv4 (which is the default), `apt-get update` takes much longer than when IPv4 is preferred (after modifying /etc/gai.conf).

    Not sure if this is just me. I couldn't find any online net tool that allows inputing IPv6 addresses.

    May 02, 2013 - 04:19am
  • Thanks for letting us know, ladios. Investigation is underway. Cheers!

    May 03, 2013 - 08:34am
  • ladios, should be fixed now. Does it work for you?

    May 03, 2013 - 10:34am
  • ladios's picture
    ladios (not verified)

    Yes, it works. Thanks

    May 03, 2013 - 06:57pm
  • patrickv's picture
    patrickv (not verified)

    Hello there,

    I am reviving this thread to point out I have currrently the same issue, through 3 different networks. All three stop at 10gigabitethernet12-2.core1.sea1.he.net

    traceroute to download.01.org (2001:19d0:3:5::106), 30 hops max, 80 byte packets
     1  [deleted]
     2  [deleted]
     3  [deleted]
     4  [deleted]
     5  30gigabitethernet4-3.core1.fra1.he.net (2001:7f8::1b1b:0:1)  7.455 ms  7.383 ms  6.838 ms
     6  10gigabitethernet5-3.core1.lon1.he.net (2001:470:0:1d2::1)  23.522 ms  22.383 ms  22.178 ms
     7  10gigabitethernet10-4.core1.nyc4.he.net (2001:470:0:128::1)  90.159 ms  98.816 ms  98.731 ms
     8  100gigabitethernet7-2.core1.chi1.he.net (2001:470:0:298::1)  109.414 ms  108.309 ms  108.525 ms
     9  10gigabitethernet3-2.core1.den1.he.net (2001:470:0:1af::2)  132.259 ms  132.753 ms  132.172 ms
    10  10gigabitethernet12-2.core1.sea1.he.net (2001:470:0:18f::1)  163.987 ms  163.969 ms  164.437 ms
    11  * * *
    12  [snip]
    
    Jul 09, 2013 - 01:30am
  • Hi patricky,

    Our IT folks have done a thorough investigation with our service providers, and are not able to reproduce any routing issues to our IPv6 servers at the present time.

    Cheers

    Jul 15, 2013 - 12:25pm