[LAC-TF] Problemas de comunicación entre redes ipv6 de los AS16735 y AS12989

Cristian Perez cdlt23 at gmail.com
Wed Aug 3 19:56:50 BRT 2011


Gracias Alexander:
En realidad el problema es entre las redes asociadas a los AS12989 y
AS16735. Ambos grupos de redes se comunican generalmente con el universo de
ASs de Internetipv6 sin problema. Igualmente muchísimas gracias.
Saludos
Cristian

2011/8/3 Jhon Alexander Calderón Sanmartín <j.calderon at ieee.org>

> Hola Cristian,
>
> Mira ejecuto un traceroute6 y si llego sin ningún inconveniente a los dos
> lugares te pongo los saltos que tengo, espero te sea de utilidad.
>
> dxlnx at machute:~$ traceroute6 brudi01.sixxs.net
> traceroute to brudi01.sixxs.net (2001:1291:2::b) from 2800:68:7:32:63::7,
> 30 hops max, 24 byte packets
>  1  fw.unl.edu.ec (2800:68:7:32:32::1)  0.406 ms  0.658 ms  0.571 ms
>  2  2800:68:7:49::4 (2800:68:7:49::4)  1.335 ms  0.72 ms  0.767 ms
>  3  2800:2a0:51:891::1 (2800:2a0:51:891::1)  1.062 ms  0.997 ms  0.857 ms
>  4  ::ffff:10.201.51.214 (::ffff:10.201.51.214)  7.669 ms  7.015 ms  7.771
> ms
>  5  2800:2a0:11:21::1 (2800:2a0:11:21::1)  6.177 ms  6.337 ms  7.349 ms
>  6  2800:2a0:11:2::3 (2800:2a0:11:2::3)  7.423 ms  6.901 ms  6.751 ms
>  7  p16-2-2-0.r21.miamfl02.us.bb.gin.ntt.net (2001:418:1000:5000::25)
> 60.082 ms  59.514 ms  59.649 ms
>  8  p16-1.sprint.miamfl02.us.bb.gin.ntt.net (2001:418:0:4000::7e)  61.761
> ms  61.289 ms  61.037 ms
>  9  sl-st30-mia-po0-9-0-0.v6.sprintlink.net (2600:0:2:1239:144:232:28:77)
> 60.261 ms  65.362 ms  60.384 ms
> 10  sl-st30-mia-te0-3-0-3-out.v6.sprintlink.net (2600:3:1b40::5)  136.485
> ms  135.953 ms  136.248 ms
> 11  2001:1291:0:44::a (2001:1291:0:44::a)  236.033 ms  270.56 ms  236.446
> ms
> 12  ge-2-1-0-0.core-b.spo511.ctbc.com.br (2001:1291:0:5::a)  234.169 ms
> 234.554 ms  234.555 ms
> 13  xe-3-0-0-0.core-b.ula001.ctbc.com.br (2001:1291:0:4::a)  269.606 ms
> 266.821 ms  264.543 ms
> 14  ge-1-0-0.semente.ula001.ctbc.com.br (2001:1291:0:2::a)  264.585 ms
> 264.709 ms  265.142 ms
> 15  brudi01.sixxs.net (2001:1291:2::b)  262.074 ms  261.031 ms  260.23 ms
> dxlnx at machute:~$
> dxlnx at machute:~$ traceroute6 usdal01.sixxs.net
> traceroute to usdal01.sixxs.net (2001:4de0:1000:a3::2) from
> 2800:68:7:32:63::7, 30 hops max, 24 byte packets
>  1  fw.unl.edu.ec (2800:68:7:32:32::1)  0.302 ms  0.39 ms  0.325 ms
>  2  2800:68:7:49::4 (2800:68:7:49::4)  0.88 ms  0.589 ms  0.651 ms
>  3  2800:2a0:51:891::1 (2800:2a0:51:891::1)  1.066 ms  1.29 ms  1.071 ms
>  4  ::ffff:10.201.51.214 (::ffff:10.201.51.214)  6.667 ms  6.8 ms  7.677 ms
>  5  2800:2a0:11:21::1 (2800:2a0:11:21::1)  7.779 ms  6.159 ms  7.092 ms
>  6  2800:2a0:11:2::3 (2800:2a0:11:2::3)  7.302 ms  7.255 ms  6.621 ms
>  7  p16-2-2-0.r21.miamfl02.us.bb.gin.ntt.net (2001:418:1000:5000::25)
> 60.248 ms  60.572 ms  68.149 ms
>  8  ae-5.r20.miamfl02.us.bb.gin.ntt.net (2001:418:0:2000::36d)  61.213 ms
> 59.723 ms  59.375 ms
>  9  ae-8.r21.asbnva02.us.bb.gin.ntt.net (2001:418:0:2000::342)  90.649 ms
> 87.856 ms  94.377 ms
> 10  ae-2.r23.amstnl02.nl.bb.gin.ntt.net (2001:418:0:2000::1b2)  182.887
> ms  182.323 ms  181.801 ms
> 11  as-0.r22.amstnl02.nl.bb.gin.ntt.net (2001:728:0:2000::11)  220.108 ms
> 172.325 ms  173.678 ms
> 12  amsix.ipv6.r2.am.hwng.net (2001:7f8:1::a501:2989:2)  175.519 ms
> 175.105 ms  175.473 ms
> 13  5-1.ipv6.r2.dc.hwng.net (2001:4de0:1000:5::2)  228.213 ms  228.575 ms
> 224.691 ms
> 14  1-1.ipv6.r2.da.hwng.net (2001:4de0:1000:30::1)  248.244 ms  259.22 ms
> 258.822 ms
> 15  1-3.ipv6.r1.da.hwng.net (2001:4de0:1000:29::2)  251.141 ms  246.027
> ms  247.954 ms
> 16  2001:4de0:1000:a3::2 (2001:4de0:1000:a3::2)  250.395 ms  253.085 ms
> 250.459 ms
>
>
>
> El 2 de agosto de 2011 14:08, Cristian Perez <cdlt23 at gmail.com> escribió:
>
>> Estimados:
>> Quería realizarles la siguiente consulta y les agradecería si pueden
>> para darme información de a quien recurrir para resolver este
>> problema:
>> Existe un problema de comunicación que impide la comunicación entre
>> redes ruteadas a través de túneles de Sixxs del POP brudi01
>> perteneciente a la Companhia de Telecomunicações do Brasil Central
>> (AS16735)  y las redes ruteadas  a través de túneles de Sixxs de los
>> POPs usdal01 y usphx01 (AS12989) pertenecientes ambos a Highwinds
>> Network Group Inc. Les envío información de los traceroute realizados
>> que muestran el problema:
>>
>>
>> IPv6 traceroute from brudi01.sixxs.net @ Companhia de Telecomunicações
>> do Brasil Central, AS16735 to usdal01.sixxs.net / Highwinds Network
>> Group Inc, AS12989 :
>>
>> Hop  Node                         Loss%  Sent   Last   Avg  Best Worst
>> StDev       ASN        Organisation
>>  1. 2001:1291:2::a                0.0%     5    0.6   0.6   0.5   0.6
>> 0.0
>>  2. 2001:1291:0:2::b              0.0%     5    0.3   0.4   0.3   0.4
>> 0.1
>>  3. 2001:1291:0:4::b              0.0%     5   19.0  19.0  19.0  19.1
>> 0.0
>>  4. 2001:1291:0:5::b              0.0%     5   19.0  19.1  19.0  19.1
>> 0.0
>>  5. 2001:1291:0:44::b             0.0%     5  125.0 125.0 125.0 125.1
>> 0.0
>>  6. 2001:478:124::176             0.0%     5  171.7 173.9 171.5 179.0
>> 3.2
>>  7. 2001:470:0:a6::2              0.0%     5  180.1 173.8 171.4 180.1
>> 3.6
>>  8. ???                          100.0     5    0.0   0.0   0.0   0.0
>> 0.0
>>
>> IPv6 traceroute from usdal01.sixxs.net @ Highwinds Network Group Inc,
>> AS12989 to brudi01.sixxs.net / Companhia de Telecomunicações do Brasil
>> Central, AS16735 :
>>
>> Hop  Node                         Loss%  Sent   Last   Avg  Best Worst
>> StDev       ASN        Organisation
>>  1. 2001:4de0:1000:a3::1          0.0%     5    0.4   1.3   0.3   5.1
>> 2.1
>>  2. 2001:4de0:1000:a::1           0.0%     5   50.8  48.8  48.2  50.8
>> 1.1
>>  3. ???                          100.0     5    0.0   0.0   0.0   0.0
>> 0.0
>>
>>
>> El problema puede verificarse al usar la siguiente herramienta :
>> http://www.sixxs.net/tools/traceroute/
>> El problema también ha sido reportado por un usuario de Sixxs hace muy
>> poco y desde Sixxs responden que es un problema remoto, o en otras
>> palabras no les incumbe a ellos. El ticket generado para ese problema
>> es el siguiente: https://www.sixxs.net/tickets/?msg=tickets-5286010
>>
>> Desde ya muchas gracias
>> Los saluda atte.
>> Cristian
>> _______________________________________________
>> LACTF mailing list
>> LACTF at lacnic.net
>> https://mail.lacnic.net/mailman/listinfo/lactf
>>
>
>
>
> --
> Saludos.
>
> Atte:
> Jhon Alexander Calderón Sanmartín
>    http://jcalderon.wordpress.com/
>         IEEE Student Member
> Gnu / Linux Registered User # 488192
> FingerPrint 69B6 EB93 1488 74BE 6F91  AF82 DD70 9F9E DA46 3367
> Public Key 0xDA463367 at http://keyserver.ubuntu.com:11371
>
> Loja - Ecuador
>
> _______________________________________________
> LACTF mailing list
> LACTF at lacnic.net
> https://mail.lacnic.net/mailman/listinfo/lactf
>
>


-- 
6Mail
Mail enviado desde GMAIL Over IPV6
red: fastisp.com.ar [2001:1938:110::]
subred: cdlt.com.ar [2001:1938:110:23::]
FASTISP
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://mail.lacnic.net/pipermail/lactf/attachments/20110803/cca56f2a/attachment.html>


More information about the LACTF mailing list