home bbs files messages ]

Forums before death by AOL, social media and spammers... "We can't have nice things"

   comp.protocols.tcp-ip      TCP and IP network protocols.      14,669 messages   

[   << oldest   |   < older   |   list   |   newer >   |   newest >>   ]

   Message 14,341 of 14,669   
   ElChino to All   
   IPv6 traceroute weirdness   
   14 Aug 18 14:22:37   
   
   From: elchino@cnn.cn   
      
   Hello group.   
      
   I now have IPv6 connection to the net. But I'm only able   
   to get a proper stable WAN/IPv6 connection via '6to4'.   
   I tried 'SLAAC/DHCPv6' and got a connect, but it got   
   a "disconnect" after approx. 20 min. And my router (a   
   Trendnet TEW-824DRU) seems to have an auto-fallback to   
   '6to4'.   
      
    From the router-status, I see it uses '2001:4600:4:1fff::'   
   as the DNSv6-server. Located in Oslo/Norway.   
      
   Here is the strange part in this '6to4' tunneling scheme.   
   A 'c:\Windows\system32\tracert.exe -6 2001:4600:4:1fff::' shows   
   these long hops:   
      
   Tracing route to 2001:4600:4:1fff:: over a maximum of 30 hops   
      
      1    <1 ms    <1 ms    <1 ms  2002:6dbd:2078:1::1   
      2    41 ms    42 ms    43 ms  2002:c058:6301::1   
      3    70 ms    43 ms    67 ms  ve210.core1.ams1.he.net [2001:470:0:24f::1]   
      4    43 ms    43 ms    43 ms  ti9000b400.ti.telenor.net [2001   
   7f8:1::a500:2119:1]   
      5    65 ms    64 ms    65 ms  ti3004c400-lo0-0.ti.telenor.net   
   [2001:4600:0:100::5]   
      6    67 ms    75 ms    64 ms  ti0001c360-lo0-0.ti.telenor.net   
   [2001:4600:0:100::23]   
      7    66 ms    65 ms    63 ms  ti0300b400-lo0-0.ti.telenor.net [2001:4600::e]   
      8    65 ms    65 ms    66 ms  sf-o-d-6.ti.telenor.net [2001:4600:10::ae]   
      9    64 ms    64 ms    73 ms  tix96c01-ec6-v100.tix.telenor.net   
   [2001:4600:4:f000::c1]   
     10    65 ms    69 ms    65 ms  tix95d02-ec4-v100.tix.telenor.net   
   [2001:4600:4:f000::a2]   
     11    65 ms    65 ms    65 ms  tix95d01-ec1-v100.tix.telenor.net   
   [2001:4600:4:f000::91]   
     12    66 ms    65 ms    65 ms  tix95a01-ec7-v100.tix.telenor.net   
   [2001:4600:4:f000::112]   
     13    66 ms    66 ms    85 ms  2001:4600:4:f000::95:a2   
     14    64 ms    65 ms    64 ms  fw-z1-95-exp1-v11.tnx.telenor.net   
   [2001:4600:4:f000::95:94]   
     15    66 ms    74 ms    65 ms  tnxe95c01-v11.tnx.telenor.net [   
   001:4600:4:f000::95:92]   
     16    65 ms    65 ms    65 ms  fw-z1-95-exp1-v11.tnx.telenor.net   
   [2001:4600:4:f000::95:94]      == hop 14   
     17    66 ms    66 ms    72 ms  tnxe95c01-v11.tnx.telenor.net [   
   001:4600:4:f000::95:92]   
     18    66 ms   123 ms    68 ms  fw-z1-95-exp1-v11.tnx.telenor.net   
   [2001:4600:4:f000::95:94]      == hop 14   
     19    66 ms    71 ms    66 ms  tnxe95c01-v11.tnx.telenor.net [   
   001:4600:4:f000::95:92]   
     20    68 ms   102 ms    66 ms  fw-z1-95-exp1-v11.tnx.telenor.net   
   [2001:4600:4:f000::95:94]      == hop 14   
     21    69 ms    66 ms    69 ms  tnxe95c01-v11.tnx.telenor.net [   
   001:4600:4:f000::95:92]   
     22    66 ms    78 ms    65 ms  fw-z1-95-exp1-v11.tnx.telenor.net   
   [2001:4600:4:f000::95:94]      == hop 14   
     23    66 ms    67 ms    70 ms  tnxe95c01-v11.tnx.telenor.net [   
   001:4600:4:f000::95:92]   
     24    67 ms    66 ms    66 ms  fw-z1-95-exp1-v11.tnx.telenor.net   
   [2001:4600:4:f000::95:94]      == hop 14   
     25    69 ms    67 ms    67 ms  tnxe95c01-v11.tnx.telenor.net [   
   001:4600:4:f000::95:92]   
     26    67 ms    82 ms    68 ms  fw-z1-95-exp1-v11.tnx.telenor.net   
   [2001:4600:4:f000::95:94]      == hop 14   
     27    77 ms    69 ms    68 ms  tnxe95c01-v11.tnx.telenor.net [   
   001:4600:4:f000::95:92]   
     28    69 ms    68 ms    68 ms  fw-z1-95-exp1-v11.tnx.telenor.net   
   [2001:4600:4:f000::95:94]      == hop 14   
     29   113 ms    69 ms    70 ms  tnxe95c01-v11.tnx.telenor.net [   
   001:4600:4:f000::95:92]   
     30    68 ms    69 ms    69 ms  fw-z1-95-exp1-v11.tnx.telenor.net   
   [2001:4600:4:f000::95:94]      == hop 14   
      
   ---------   
      
   Using data from GeoIP and IP2Location data-bases, I figured the   
   location of hop 3 is in "United States (Fremont/California)" !!   
      
   Hop 4 is 'Holland, Amsterdam'.   
   Hop 5 and higher are all 'Norway, Oslo'.   
      
   And what's up with all the nodes at hop 16, 18,..30?   
   My Windows tracert program gave up after 30 hops.   
      
   Who can I blame this strangeness on? Windows-10, my ISP or   
   my router/PC settings?   
      
   I briefly read something about 'IPv6 tunnel brokering'. Would   
   that be a fix for this case?   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)   

[   << oldest   |   < older   |   list   |   newer >   |   newest >>   ]


(c) 1994,  bbs@darkrealms.ca