Hurricane Electric's IPv6 Tunnel Broker Forums

Advanced search  

News:

Welcome to Hurricane Electric's Tunnelbroker.net forums!

Author Topic: ipv6 daily traceroute bug ?  (Read 3641 times)

anackin

  • Newbie
  • *
  • Posts: 12
ipv6 daily traceroute bug ?
« on: August 27, 2010, 02:55:03 PM »

In daily ipv6 traceroute test, submitting this trace returns always the following error:

"Sorry, you must submit the line before the first hop!"

# traceroute6  nitcipv6.jo
traceroute to nitcipv6.jo (2a02:9c0:0:300::2), 30 hops max, 80 byte packets
 1  londoner-1.tunnel.tserv5.lon1.ipv6.he.net (2001:470:1f08:9ef::1)  104.142 ms  106.992 ms  109.995 ms
 2  gige-g4-6.core1.lon5.ipv6.he.net (2001:470:0:67::1)  118.080 ms  118.010 ms  117.936 ms
 3  2001:7f8:4::cb9:1 (2001:7f8:4::cb9:1)  120.304 ms  124.228 ms  127.168 ms
 4  xe-4-1-0.lon11.ip6.tinet.net (2001:668:0:2::1:1621)  130.065 ms  134.966 ms  138.887 ms
 5  xe-7-2-0.lon20.ip6.tinet.net (2001:668:0:2::1:312)  141.420 ms  144.088 ms  148.644 ms
 6  xe-1-1-0.lon24.ip6.tinet.net (2001:668:0:2::1:1ad2)  151.541 ms  95.310 ms  98.862 ms
 7  bezeq-gw.ip6.tinet.net (2001:668:0:3::4000:3e2)  180.889 ms  183.197 ms  189.396 ms
 8  ::82.212.65.6 (::82.212.65.6)  189.359 ms  197.291 ms *
 9  ::82.212.65.22 (::82.212.65.22)  197.216 ms  200.524 ms  202.500 ms
10  2a02:9c0:0:1::1 (2a02:9c0:0:1::1)  212.501 ms  215.413 ms  219.381 ms
11  2a02:9c0:0:303::1 (2a02:9c0:0:303::1)  224.307 ms  226.269 ms  231.261 ms
12  2a02:9c0:0:300::2 (2a02:9c0:0:300::2)  175.801 ms  174.752 ms  175.944 ms

I must say it is really singular, see hops 8 and 9 !!

« Last Edit: August 27, 2010, 03:16:38 PM by anackin »
Logged

lukec

  • Jr. Member
  • **
  • Posts: 65
    • Home
Re: ipv6 daily traceroute bug ?
« Reply #1 on: August 29, 2010, 03:01:30 AM »

Here is the whois for the IPv4 portions of your traceroute

 8  ::82.212.65.6 (::82.212.65.6)  189.359 ms  197.291 ms *
 9  ::82.212.65.22 (::82.212.65.22)  197.216 ms  200.524 ms  202.500 ms

IPv4 address...in IPv6
Note the description...
Regards
lukec



NetRange:       82.0.0.0 - 82.255.255.255
CIDR:           82.0.0.0/8
OriginAS:
NetName:        82-RIPE
NetHandle:      NET-82-0-0-0-1
Parent:
NetType:        Allocated to RIPE NCC
NameServer:     TINNIE.ARIN.NET
NameServer:     NS-PRI.RIPE.NET
NameServer:     SUNIC.SUNET.SE
NameServer:     SEC3.APNIC.NET
NameServer:     NS3.NIC.FR
NameServer:     SEC1.APNIC.NET
Comment:        These addresses have been further assigned to users in
Comment:        the RIPE NCC region. Contact information can be found in
Comment:        the RIPE database at http://www.ripe.net/whois
RegDate:        2002-11-23
Updated:        2004-03-16
Ref:            http://whois.arin.net/rest/net/NET-82-0-0-0-1

OrgName:        RIPE Network Coordination Centre
OrgId:          RIPE
Address:        P.O. Box 10096
City:           Amsterdam
StateProv:
PostalCode:     1001EB
Country:        NL
RegDate:
Updated:        2004-12-13
Ref:            http://whois.arin.net/rest/org/RIPE

ReferralServer: whois://whois.ripe.net:43

#
# ARIN WHOIS data and services are subject to the Terms of Use
# available at: https://www.arin.net/whois_tou.html
#

% This is the RIPE Database query service.
% The objects are in RPSL format.
%
% The RIPE Database is subject to Terms and Conditions.
% See http://www.ripe.net/db/support/db-terms-conditions.pdf

% Note: This output has been filtered.
%       To receive output for a database update, use the "-B" flag.

% Information related to '82.212.65.0 - 82.212.65.255'

inetnum:        82.212.65.0 - 82.212.65.255
netname:        NEU-TELECOM
descr:          DamaMax Jordan Point-to-Point Odd routers Connections
descr:          This space is statically assigned.
remarks:        INFRA-AW
country:        JO
remarks:        Tel +962-6-5777733
remarks:        *****************************************************
remarks:        * Please send all abuse-complaints to               *
remarks:        * abuse@damamax.jo                                  *
remarks:        *****************************************************
admin-c:        NRA19-RIPE
tech-c:         NRA19-RIPE
status:         ASSIGNED PA
mnt-by:         MNT-NEU
mnt-lower:      MNT-NEU
mnt-routes:     MNT-NEU
source:         RIPE # Filtered

person:         NEU RIPE admin
address:        Al Madina Al Munawwara Str.
                Amman
                Jordan
phone:          +962 6 5777733
phone:          +962 7 8810 1170
fax-no:         +962 6 5777744
nic-hdl:        NRa19-RIPE
e-mail:         ripeadmin@neutelecom.com
mnt-by:         MNT-NEU
source:         RIPE # Filtered

% Information related to '82.212.64.0/18AS47887'

route:          82.212.64.0/18
descr:          NTT Prefix
origin:         AS47887
mnt-by:         MNT-NEU
source:         RIPE # Filtered

% Information related to '82.212.65.0/24AS47887'

route:          82.212.65.0/24
descr:          NTT Routers Point-to-Point Odd Connection
origin:         AS47887
mnt-by:         MNT-NEU
source:         RIPE # Filtered

Logged

cholzhauer

  • Hero Member
  • *****
  • Posts: 2714
Re: ipv6 daily traceroute bug ?
« Reply #2 on: August 29, 2010, 06:59:34 PM »

Quote
# traceroute6  nitcipv6.jo
traceroute to nitcipv6.jo (2a02:9c0:0:300::2), 30 hops max, 80 byte packets
 1  londoner-1.tunnel.tserv5.lon1.ipv6.he.net (2001:470:1f08:9ef::1)  104.142 ms  106.992 ms  109.995 ms
 2  gige-g4-6.core1.lon5.ipv6.he.net (2001:470:0:67::1)  118.080 ms  118.010 ms  117.936 ms
 3  2001:7f8:4::cb9:1 (2001:7f8:4::cb9:1)  120.304 ms  124.228 ms  127.168 ms
 4  xe-4-1-0.lon11.ip6.tinet.net (2001:668:0:2::1:1621)  130.065 ms  134.966 ms  138.887 ms
 5  xe-7-2-0.lon20.ip6.tinet.net (2001:668:0:2::1:312)  141.420 ms  144.088 ms  148.644 ms
 6  xe-1-1-0.lon24.ip6.tinet.net (2001:668:0:2::1:1ad2)  151.541 ms  95.310 ms  98.862 ms
 7  bezeq-gw.ip6.tinet.net (2001:668:0:3::4000:3e2)  180.889 ms  183.197 ms  189.396 ms
 8  ::82.212.65.6 (::82.212.65.6)  189.359 ms  197.291 ms *
 9  ::82.212.65.22 (::82.212.65.22)  197.216 ms  200.524 ms  202.500 ms
10  2a02:9c0:0:1::1 (2a02:9c0:0:1::1)  212.501 ms  215.413 ms  219.381 ms
11  2a02:9c0:0:303::1 (2a02:9c0:0:303::1)  224.307 ms  226.269 ms  231.261 ms
12  2a02:9c0:0:300::2 (2a02:9c0:0:300::2)  175.801 ms  174.752 ms  175.944 ms


Are you submitting exactly that?  If I were doing that, this is what I would submit:

Code: [Select]
traceroute6 to nitcipv6.jo (2a02:9c0:0:300::2) from 2001:470:c27d:e000:20c:29ff:fe26:51b7, 64 hops max, 12 byte packets
 1  2001:470:c27d:d000:2e0:81ff:fe79:f4c4  2.445 ms  2.380 ms  2.249 ms
 2  servicespring-1.tunnel.tserv9.chi1.ipv6.he.net  57.223 ms  44.081 ms  60.132 ms
 3  gige-g3-4.core1.chi1.ipv6.he.net  55.947 ms  57.559 ms  42.770 ms
 4  ibx-chi.ip6.tiscali.net  57.220 ms  53.089 ms  57.239 ms
 5  xe-2-1-0.nyc32.ip6.tinet.net  78.313 ms  53.548 ms  82.539 ms
 6  xe-3-1-0.lon25.ip6.tinet.net  86.088 ms  93.185 ms  151.281 ms
 7  ge-0-1-0.lon24.ip6.tinet.net  138.787 ms  54.873 ms  162.414 ms
 8  bezeq-gw.ip6.tinet.net  287.140 ms  292.092 ms  275.909 ms
 9  ::82.212.65.6  295.951 ms  294.744 ms  230.567 ms
10  ::82.212.65.22  218.507 ms  221.545 ms  210.578 ms
11  2a02:9c0:0:1::1  170.135 ms  288.089 ms  155.415 ms
12  2a02:9c0:0:303::1  90.096 ms  294.132 ms  282.563 ms
13  2a02:9c0:0:300::2  245.232 ms  225.781 ms  261.471 ms

You don't need the original traceroute line
Logged

anackin

  • Newbie
  • *
  • Posts: 12
Re: ipv6 daily traceroute bug ?
« Reply #3 on: August 30, 2010, 01:59:41 PM »

Thanks, I tried to submit with and without the original traceroute line,  but I've got the same error :( 
I also tried submitting a "traceroute6 -n", always the same error.

Maybe the problem is the stranges #8 and #9 hops ?
Logged

cholzhauer

  • Hero Member
  • *****
  • Posts: 2714
Re: ipv6 daily traceroute bug ?
« Reply #4 on: August 30, 2010, 06:02:55 PM »

Very possible.  Do other traceroutes work?  You may want to email he... They could tell you for sure
Logged