[lacnog] RES: Bloqueo de Whatsapp en Brasil afectando acceso al servicio en la Region

Gustavo Rodrigues Ramos gustavo en nexthop.com.br
Vie Dic 18 13:44:16 BRST 2015


Bingo!
On Dec 18, 2015 1:39 PM, "Carlos M. Martinez" <carlosm3011 en gmail.com> wrote:

> Es posible que Level3 solo la haya propagado... y que los que hayan
> permitido que se fugara hayan sido los operadores móviles.
>
> On 12/18/15 12:29 PM, Gustavo Rodrigues Ramos wrote:
> > No me parece que L3 ha generado la ruta nula, al menos por lo que la
> > salida siguiente muestra. Pero todavía estoy buscando en los datos
> > histórico de bgp.
> >
> > (La salida és desde el correo de Alejandro D'Egidio).
> >
> > route-server.phx1>show ip route 184.173.147.39
> > Routing entry for 184.173.147.39/32 <http://184.173.147.39/32>
> > Known via "bgp 3549", distance 200, metric 0
> > Tag 18881, type internal
> > Last update from 67.16.148.37 12:05:25 ago
> > Routing Descriptor Blocks:
> > * 67.16.148.37, from 4.69.243.196, 12:05:25 ago
> > Route metric is 0, traffic share count is 1
> > AS Hops 1
> > Route tag 18881  <--------
> >
> > Saludos,
> > Gustavo.
> >
> >
> > 2015-12-18 12:49 GMT-02:00 Christian O'Flaherty
> > <christian.oflaherty en gmail.com <mailto:christian.oflaherty en gmail.com>>:
> >
> >     > Entiendo la responsabilidad de origen, el orden del juez, pero no
> >     > entiendo por que L3 dejó el bloqueo escapar hacia afuera de
> Brasil. Es
> >     > sobre esta responsabilidad específica que pregunto.
> >
> >     No sabemos donde fue la configuración, tampoco sabemos si “dejó
> >     escapar” o es el efecto normal. Solo vemos el efecto en la red de
> >     Level3 porque es un operador serio que tiene looking glass y muestra
> >     en forma transparente lo que hay dentro de su red (no podemos verlo
> en
> >     otros operadores).
> >
> >     Decir que Level3 dejó escapar el bloqueo es injusto...
> >
> >     >
> >     > Tampoco sé si otras operadoras de tránsito hicieron lo mismo.
> >
> >     En un email anterior aparecían otros también:
> >
> >     >>> En Argentina esto está afectando al menos a través de TASA,
> NAUTILUS y Level3.
> >
> >     Christian
> >
> >     >
> >     > []s fraternos
> >     >
> >     > --c.a.
> >     >
> >     > On 18-12-15 07:35, Christian O'Flaherty wrote:
> >     >> 2015-12-18 9:22 GMT-03:00 Carlos A. Afonso <ca en cafonso.ca
> >     <mailto:ca en cafonso.ca>>:
> >     >>> Si, entiendo que opera en Brasil pero no oferta servicios de
> >     banda ancha, apenas conecta las operadoras de movil y fijo. De todas
> >     maneras, se puede decir que la propagación del bloqueo hacia afiera
> >     ha sido responsabilidad de L3, correcto?
> >     >>
> >     >>
> >     >> No... la responsabilidad fue del juez que envió una orden
> >     judicial incorrecta.
> >     >>
> >     >> Level3 implementó la orden y las consecuencias las debe asumir
> quien
> >     >> lo ordenó. Tal vez Level3 hubiera podido hacerlo mejor... eso será
> >     >> discutido. El operador no es responsable si lo obligan a hacer
> cosas
> >     >> incorrectas.
> >     >>
> >     >> Christian
> >     >>
> >     >>>
> >     >>> [] fraterno
> >     >>>
> >     >>> --c.a.
> >     >>>
> >     >>> sent from a dumbphone
> >     >>>
> >     >>>> On 18 de dez de 2015, at 07:16, Christian O'Flaherty
> >     <christian.oflaherty en gmail.com
> >     <mailto:christian.oflaherty en gmail.com>> wrote:
> >     >>>>
> >     >>>> Carlos,
> >     >>>>
> >     >>>> Level3 es un operador en Brasil. Seguramente recibió la orden
> >     judicial
> >     >>>> y por eso envió el tráfico a null (que por error se propago a
> >     toda su
> >     >>>> red regional).
> >     >>>>
> >     >>>> Level3 compró a Global Crossing que antes había comprado a
> >     Impsat que
> >     >>>> compró a Mandic. Recuerdas Mandic?
> >     >>>>
> >     >>>> Saludos,
> >     >>>>
> >     >>>> 2015-12-17 23:44 GMT-03:00 Carlos Afonso <ca en cafonso.ca
> >     <mailto:ca en cafonso.ca>>:
> >     >>>>> Caros, se puede decir que el *origen* del error que motivó la
> >     >>>>> propagación a otros países es Level 3? O Level 3 apenas "dejó
> >     pasar" el
> >     >>>>> bloqueo en sus tablas de rutas desde una red de las operadoras
> >     brasileñas?
> >     >>>>>
> >     >>>>> Pregunto porque hay mención acá en Brasil que Level 3 también
> >     habría
> >     >>>>> recebido la solicitud de la justicia para bloquear, lo que me
> >     parece raro.
> >     >>>>>
> >     >>>>> []s fraternos
> >     >>>>>
> >     >>>>> --c.a.
> >     >>>>>
> >     >>>>>> On 17-12-15 15:56, Roque Gagliano wrote:
> >     >>>>>> Si te fijas los shows que mandaron, el ASPATH es de largo
> >     uno, por lo que
> >     >>>>>> lamentablemente no hemos aprendido nada en tanto tiempo desde
> la
> >     >>>>>> experiencia de Pakistán...
> >     >>>>>>
> >     >>>>>> Creo que deberíamos ver con la gente de RIPE o de Dyn o mismo
> >     Facebook si
> >     >>>>>> podemos medir el alcance del problema basado en sus sensores.
> >     Lo digo pues
> >     >>>>>> podemos publicar un blogger y alertar sobre las consecuencias
> >     regionales de
> >     >>>>>> medidas como estas.
> >     >>>>>>
> >     >>>>>> Carlos, vos tenes contactos no?
> >     >>>>>>
> >     >>>>>> Roque
> >     >>>>>>> On Dec 17, 2015 5:32 PM, "Ivan Chapero"
> >     <info en ivanchapero.com.ar <mailto:info en ivanchapero.com.ar>> wrote:
> >     >>>>>>>
> >     >>>>>>> ¿Pero esos /32 (o /128 no nos olvidemos de IPv6) salieron
> >     del ASN de
> >     >>>>>>> Global/Level?, me parece que el error se limitó a no acotar
> >     la propagación
> >     >>>>>>> "dentro" de su ASN a la región/tabla/VRF de Brasil.
> >     >>>>>>>
> >     >>>>>>> Al ser un Tier1 el efecto igual fue inmenso, si me pasa a mi
> >     dentro de mi
> >     >>>>>>> AS se limita a 4 ciudades ¬¬
> >     >>>>>>>
> >     >>>>>>> Slds!
> >     >>>>>>>
> >     >>>>>>> El 17 de diciembre de 2015, 15:54, Alex Ojeda
> >     <alex en chilenetworks.com <mailto:alex en chilenetworks.com>>
> >     >>>>>>> escribió:
> >     >>>>>>>
> >     >>>>>>>> Recuerdo muchas opiniones de las que conversamos en Bogota
> >     en el WG junto
> >     >>>>>>>> a Ariel y otros interesados en generar documentos y mejores
> >     practicas...
> >     >>>>>>>>
> >     >>>>>>>>
> >     >>>>>>>> Una lástima ocurran estos fallos en un Tier1 que afecte más
> >     allá de la
> >     >>>>>>>> jurisdicción de la normativa como fue este el caso...
> >     >>>>>>>>
> >     >>>>>>>> Carita triste para level3...
> >     >>>>>>>>
> >     >>>>>>>>
> >     >>>>>>>>
> >     >>>>>>>>
> >     >>>>>>>>
> >     >>>>>>>>
> >     >>>>>>>> Alex Matias Ojeda Mercado
> >     >>>>>>>> Chile Networks SpA.
> >     >>>>>>>> Fono: (+56 2) 258 58 120
> <tel:%28%2B56%202%29%20258%2058%20120>
> >     >>>>>>>> Fono: (+56 2) 258 30 117
> <tel:%28%2B56%202%29%20258%2030%20117>
> >     >>>>>>>> Móvil: (+56 9) 719 22 362
> >     <tel:%28%2B56%209%29%20719%2022%20362>
> >     >>>>>>>> https://chilenetworks.com/
> >     >>>>>>>>
> >     >>>>>>>> ------------------------------
> >     >>>>>>>> Correo Electrónico Procesado en la Plataforma Microsoft
> >     Exchange Office365
> >     >>>>>>>> Servicios Corporativos en la nube.
> >     >>>>>>>> Estos servicios son entregados por Chile Networks SpA.
> >     >>>>>>>> ------------------------------
> >     >>>>>>>>
> >     >>>>>>>> Mail Disclaimer :
> >     >>>>>>>> Descargo de responsabilidad Correo electronico :
> >     >>>>>>>> https://chilenetworks.com/g/maildisclaimer/
> >     >>>>>>>>
> >     >>>>>>>>
> >     >>>>>>>>
> >     >>>>>>>> ------------------------------
> >     >>>>>>>> *De:* LACNOG <lacnog-bounces en lacnic.net
> >     <mailto:lacnog-bounces en lacnic.net>> en nombre de Ariel Weher <
> >     >>>>>>>> ariel en weher.net <mailto:ariel en weher.net>>
> >     >>>>>>>> *Enviado:* jueves, 17 de diciembre de 2015 10:57
> >     >>>>>>>> *Para:* Latin America and Caribbean Region Network
> >     Operators Group
> >     >>>>>>>> *Cc:* lacnog en lacnog.org <mailto:lacnog en lacnog.org>
> >     >>>>>>>> *Asunto:* Re: [lacnog] RES: Bloqueo de Whatsapp en Brasil
> >     afectando
> >     >>>>>>>> acceso al servicio en la Region
> >     >>>>>>>>
> >     >>>>>>>> +1 para el corte en Argentina vía L3.
> >     >>>>>>>>
> >     >>>>>>>> Dado los últimos eventos ocurridos (nulleadas, leaks, etc)
> >     entiendo que
> >     >>>>>>>> la gente de Level3 nunca aprendió a usar BGP.
> >     >>>>>>>>
> >     >>>>>>>> S2
> >     >>>>>>>>
> >     >>>>>>>> 2015-12-17 10:42 GMT-03:00 Roberto Feijoo
> >     <rfeijoo en gigared.com.ar <mailto:rfeijoo en gigared.com.ar>>:
> >     >>>>>>>>
> >     >>>>>>>>> Exactamente en Argentina Level 3 no funciona, TECO si.
> >     >>>>>>>>>
> >     >>>>>>>>> Saludos.
> >     >>>>>>>>>
> >     >>>>>>>>>
> >     >>>>>>>>> Roberto G. Feijoó
> >     >>>>>>>>> Jefe de centro de operaciones de red
> >     >>>>>>>>> Gigared S.A.
> >     >>>>>>>>> Donado 840 – C1427CZB
> >     >>>>>>>>> Ciudad Autónoma de Buenos Aires
> >     >>>>>>>>> Tel.: (54011)6040.6071
> >     >>>>>>>>> www.gigared.com.ar <http://www.gigared.com.ar>
> >     >>>>>>>>>
> >     >>>>>>>>> -----Mensaje original-----
> >     >>>>>>>>> De: LACNOG [mailto:lacnog-bounces en lacnic.net
> >     <mailto:lacnog-bounces en lacnic.net>] En nombre de Alejandro
> >     >>>>>>>>> D'Egidio
> >     >>>>>>>>> Enviado el: jueves, 17 de diciembre de 2015 10:37 a.m.
> >     >>>>>>>>> Para: Latin America and Caribbean Region Network Operators
> >     Group
> >     >>>>>>>>> CC: lacnog en lacnog.org <mailto:lacnog en lacnog.org>
> >     >>>>>>>>> Asunto: Re: [lacnog] RES: Bloqueo de Whatsapp en Brasil
> >     afectando acceso
> >     >>>>>>>>> al
> >     >>>>>>>>> servicio en la Region
> >     >>>>>>>>>
> >     >>>>>>>>> En Argentina esto está afectando al menos a través de
> >     TASA, NAUTILUS y
> >     >>>>>>>>> Level3.
> >     >>>>>>>>> No puede ser que a esta altura no sepan hacer bloqueos.
> >     Están afectando
> >     >>>>>>>>> a la
> >     >>>>>>>>> región!!
> >     >>>>>>>>>
> >     >>>>>>>>> Evidentemente deben haber puesto una estática a Null0 ya
> >     que se está
> >     >>>>>>>>> distribuyendo IPs del servicio como /32 y son unreachable:
> >     >>>>>>>>>
> >     >>>>>>>>> route-server.phx1>show ip route 184.173.147.39 Routing
> >     entry for
> >     >>>>>>>>> 184.173.147.39/32 <http://184.173.147.39/32> Known via
> >     "bgp 3549", distance 200, metric 0 Tag
> >     >>>>>>>>> 18881,
> >     >>>>>>>>> type internal Last update from 67.16.148.37 12:05:25 ago
> >     Routing
> >     >>>>>>>>> Descriptor
> >     >>>>>>>>> Blocks:
> >     >>>>>>>>> * 67.16.148.37, from 4.69.243.196, 12:05:25 ago Route
> >     metric is 0,
> >     >>>>>>>>> traffic
> >     >>>>>>>>> share count is 1 AS Hops 1 Route tag 18881 MPLS label: none
> >     >>>>>>>>> route-server.phx1>show ip route 192.155.212.202 Routing
> >     entry for
> >     >>>>>>>>> 192.155.212.202/32 <http://192.155.212.202/32> Known via
> >     "bgp 3549", distance 200, metric 0 Tag
> >     >>>>>>>>> 18881,
> >     >>>>>>>>> type internal Last update from 67.16.148.37 12:06:28 ago
> >     Routing
> >     >>>>>>>>> Descriptor
> >     >>>>>>>>> Blocks:
> >     >>>>>>>>> * 67.16.148.37, from 4.69.243.196, 12:06:28 ago Route
> >     metric is 0,
> >     >>>>>>>>> traffic
> >     >>>>>>>>> share count is 1 AS Hops 1 Route tag 18881 MPLS label: none
> >     >>>>>>>>> route-server.phx1>show ip route 192.155.212.203 Routing
> >     entry for
> >     >>>>>>>>> 192.155.212.203/32 <http://192.155.212.203/32> Known via
> >     "bgp 3549", distance 200, metric 0 Tag
> >     >>>>>>>>> 18881,
> >     >>>>>>>>> type internal Last update from 67.16.148.37 12:06:04 ago
> >     Routing
> >     >>>>>>>>> Descriptor
> >     >>>>>>>>> Blocks:
> >     >>>>>>>>> * 67.16.148.37, from 4.69.243.196, 12:06:04 ago Route
> >     metric is 0,
> >     >>>>>>>>> traffic
> >     >>>>>>>>> share count is 1 AS Hops 1 Route tag 18881 MPLS label: none
> >     >>>>>>>>> route-server.phx1>show ip route 184.173.147.38 Routing
> >     entry for
> >     >>>>>>>>> 184.173.147.38/32 <http://184.173.147.38/32> Known via
> >     "bgp 3549", distance 200, metric 0 Tag
> >     >>>>>>>>> 18881,
> >     >>>>>>>>> type internal Last update from 67.16.148.37 12:06:20 ago
> >     Routing
> >     >>>>>>>>> Descriptor
> >     >>>>>>>>> Blocks:
> >     >>>>>>>>> * 67.16.148.37, from 4.69.243.196, 12:06:20 ago Route
> >     metric is 0,
> >     >>>>>>>>> traffic
> >     >>>>>>>>> share count is 1 AS Hops 1 Route tag 18881 MPLS label: none
> >     >>>>>>>>>
> >     >>>>>>>>> route-server.phx1>ping 184.173.147.60
> >     >>>>>>>>> Type escape sequence to abort.
> >     >>>>>>>>> Sending 5, 100-byte ICMP Echos to 184.173.147.60, timeout
> >     is 2 seconds:
> >     >>>>>>>>> U.U.U
> >     >>>>>>>>> Success rate is 0 percent (0/5)
> >     >>>>>>>>>
> >     >>>>>>>>>
> >     >>>>>>>>>
> >     >>>>>>>>>
> >     >>>>>>>>> Saludos,
> >     >>>>>>>>>
> >     >>>>>>>>> Alejandro D'Egidio
> >     >>>>>>>>> Jefe de Ingeniería de Backbone
> >     >>>>>>>>> adegidio en telecentro.net.ar <mailto:
> adegidio en telecentro.net.ar>
> >     >>>>>>>>>
> >     >>>>>>>>> Apolinario Figueroa 254 | Tel: 54 11 3977 1025 C1414EDF |
> >     CABA |
> >     >>>>>>>>> Argentina
> >     >>>>>>>>> TELECENTRO S.A.
> >     >>>>>>>>>
> >     >>>>>>>>> ESTE MENSAJE ES CONFIDENCIAL. Puede contener información
> >     amparada por el
> >     >>>>>>>>> secreto profesional. Si usted ha recibido este e-mail por
> >     error, por
> >     >>>>>>>>> favor
> >     >>>>>>>>> comuníquenoslo inmediatamente vía e-mail y tenga la
> >     amabilidad de
> >     >>>>>>>>> eliminarlo
> >     >>>>>>>>> de su sistema; no deberá copiar el mensaje ni divulgar su
> >     contenido a
> >     >>>>>>>>> ninguna persona. Muchas gracias.
> >     >>>>>>>>>
> >     >>>>>>>>> THIS MESSAGE IS CONFIDENTIAL. It may also contain
> >     information that is
> >     >>>>>>>>> privileged or otherwise legally exempt from disclosure. If
> >     you have
> >     >>>>>>>>> received
> >     >>>>>>>>> it by mistake please let us know by e-mail immediately and
> >     delete it from
> >     >>>>>>>>> your system; should also not copy the message nor disclose
> >     its contents
> >     >>>>>>>>> to
> >     >>>>>>>>> anyone. Many thanks.
> >     >>>>>>>>>
> >     >>>>>>>>>
> >     >>>>>>>>>
> >     >>>>>>>>>
> >     >>>>>>>>>
> >     >>>>>>>>>
> >     >>>>>>>>>
> >     >>>>>>>>>
> >     >>>>>>>>>
> >     >>>>>>>>>
> >     >>>>>>>>> ----- Mensaje original -----
> >     >>>>>>>>> De: "Evandro POLIZEI" <polizei en polizei.com.br
> >     <mailto:polizei en polizei.com.br>>
> >     >>>>>>>>> Para: "Latin America and Caribbean Region Network
> >     Operators Group"
> >     >>>>>>>>> <lacnog en lacnic.net <mailto:lacnog en lacnic.net>>
> >     >>>>>>>>> CC: lacnog en lacnog.org <mailto:lacnog en lacnog.org>
> >     >>>>>>>>> Enviados: Jueves, 17 de Diciembre 2015 10:21:41
> >     >>>>>>>>> Asunto: [lacnog] RES: Bloqueo de Whatsapp en Brasil
> >     afectando acceso al
> >     >>>>>>>>> servicio en la Region
> >     >>>>>>>>>
> >     >>>>>>>>> Buenas Hernamo Sebastian,
> >     >>>>>>>>>
> >     >>>>>>>>> Se es possible contornar lo problema com la VPN, tiene um
> >     app que abre la
> >     >>>>>>>>> conexion segura com servidoras Whatsapp, que possibilita
> >     la conexion, se
> >     >>>>>>>>> lhana BETTERNET, ele conecta com uma VPN e acesso
> >     normalmente o WhatsApp.
> >     >>>>>>>>>
> >     >>>>>>>>>
> >     >>>>>>>>> Best Regards,
> >     >>>>>>>>>
> >     >>>>>>>>> ------------------------------------
> >     >>>>>>>>> POLIZEI, Evandro
> >     >>>>>>>>> Mobile: +55 19 99980-1777 <tel:%2B55%2019%2099980-1777>
> >     >>>>>>>>> Skype: evandropolizei
> >     >>>>>>>>> CREA-SP: 5069654920 <tel:5069654920>
> >     >>>>>>>>> CREA-MT: MT027535
> >     >>>>>>>>> RNP: 1214837140
> >     >>>>>>>>> http://www.creadigital.com.br/mt/polizei
> >     >>>>>>>>> Comites ABNT:
> >     >>>>>>>>> ABNT/CB-021 Computadores e Processamento de Dados
> >     >>>>>>>>> ABNT/CEE-063 Gestão de Riscos
> >     >>>>>>>>>
> >     >>>>>>>>> Lattes: http://lattes.cnpq.br/4976637957925814
> >     >>>>>>>>>
> >     >>>>>>>>>
> >     >>>>>>>>>
> >     >>>>>>>>>
> >     >>>>>>>>> Quando capaz, finja ser incapaz; quando pronto, finja
> >     estar despreparado;
> >     >>>>>>>>> quando próximo, finja estar longe; quando longe, façam
> >     acreditar que está
> >     >>>>>>>>> próximo.
> >     >>>>>>>>>
> >     >>>>>>>>> Sun Tzu
> >     >>>>>>>>>
> >     >>>>>>>>>
> >     >>>>>>>>>
> >     >>>>>>>>> -----Mensagem original-----
> >     >>>>>>>>> De: LACNOG [mailto:lacnog-bounces en lacnic.net
> >     <mailto:lacnog-bounces en lacnic.net>] Em nome de Sebastian
> >     >>>>>>>>> Bellagamba Enviada em: quinta-feira, 17 de dezembro de
> >     2015 10:45
> >     >>>>>>>>> Para: Latin America and Caribbean Region Network Operators
> >     Group
> >     >>>>>>>>> Cc: lacnog en lacnog.org <mailto:lacnog en lacnog.org>
> >     >>>>>>>>> Assunto: Re: [lacnog] Bloqueo de Whatsapp en Brasil
> >     afectando acceso al
> >     >>>>>>>>> servicio en la Region
> >     >>>>>>>>>
> >     >>>>>>>>> Esta bloqueado de hecho, hoy y mañana, aunque el bloqueo
> >     es solo para las
> >     >>>>>>>>> redes de datos de las moviles. Si la persona con la que
> >     hablaste estaba
> >     >>>>>>>>> en
> >     >>>>>>>>> wifi, el bloqueo no aplica.
> >     >>>>>>>>>
> >     >>>>>>>>> Saludos
> >     >>>>>>>>>
> >     >>>>>>>>> Sebastián Bellagamba
> >     >>>>>>>>> bellagamba en isoc.org <mailto:bellagamba en isoc.org>
> >     >>>>>>>>> -------------------------------
> >     >>>>>>>>> Director - Oficina Regional para América Latina y el
> >     Caribe Regional
> >     >>>>>>>>> Bureau
> >     >>>>>>>>> Director for Latin America and the Caribbean
> >     ================== Internet
> >     >>>>>>>>> Society www.internetsociety.org
> >     <http://www.internetsociety.org>
> >     >>>>>>>>>
> >     >>>>>>>>>
> >     >>>>>>>>>
> >     >>>>>>>>>
> >     >>>>>>>>>
> >     >>>>>>>>>>> On Dec 17, 2015, at 09:42, Ernesto Perez
> >     <ernesto.perez en cedia.org.ec <mailto:ernesto.perez en cedia.org.ec>>
> >     >>>>>>>>>> wrote:
> >     >>>>>>>>>>
> >     >>>>>>>>>> Bueno : Acabo de hablar con alguien del estado de sp sin
> >     problemas.
> >     >>>>>>>>>> Quizá
> >     >>>>>>>>> no sea hoy?
> >     >>>>>>>>>>
> >     >>>>>>>>>> --
> >     >>>>>>>>>> Saludos
> >     >>>>>>>>>> Epe
> >     >>>>>>>>>>
> >     >>>>>>>>>>> El 17 dic 2015, a las 7:23 a.m., Alex Ojeda
> >     <alex en chilenetworks.com <mailto:alex en chilenetworks.com>>
> >     >>>>>>>>> escribió:
> >     >>>>>>>>>>>
> >     >>>>>>>>>>> Nuestros amigos de Brasil nos podrían contar un poco lo
> >     que ha
> >     >>>>>>>>> significado llevar a cabo la orden judicial que solicitó
> >     bloquear
> >     >>>>>>>>> whatsapp.
> >     >>>>>>>>>>>
> >     >>>>>>>>>>> En Chile a través de varios ISP estamos sin acceso al
> >     servicio.
> >     >>>>>>>>>>>
> >     >>>>>>>>>>> Algún otro país ?
> >     >>>>>>>>>>>
> >     >>>>>>>>>>>
> >     >>>>>>>>>>>
> >     >>>>>>>>>>>
> >     >>>>>>>>>>> Alex Ojeda
> >     >>>>>>>>>>>
> >     >>>>>>>>>>>
> >     >>>>>>>>>>> _______________________________________________
> >     >>>>>>>>>>> LACNOG mailing list
> >     >>>>>>>>>>> LACNOG en lacnic.net <mailto:LACNOG en lacnic.net>
> >     >>>>>>>>>>> https://mail.lacnic.net/mailman/listinfo/lacnog
> >     >>>>>>>>>>> Cancelar suscripcion:
> >     https://mail.lacnic.net/mailman/options/lacnog
> >     >>>>>>>>>>
> >     >>>>>>>>>> Email secured by Check Point
> >     >>>>>>>>>> _______________________________________________
> >     >>>>>>>>>> LACNOG mailing list
> >     >>>>>>>>>> LACNOG en lacnic.net <mailto:LACNOG en lacnic.net>
> >     >>>>>>>>>> https://mail.lacnic.net/mailman/listinfo/lacnog
> >     >>>>>>>>>> Cancelar suscripcion:
> >     https://mail.lacnic.net/mailman/options/lacnog
> >     >>>>>>>>>
> >     >>>>>>>>> _______________________________________________
> >     >>>>>>>>> LACNOG mailing list
> >     >>>>>>>>> LACNOG en lacnic.net <mailto:LACNOG en lacnic.net>
> >     >>>>>>>>> https://mail.lacnic.net/mailman/listinfo/lacnog
> >     >>>>>>>>> Cancelar suscripcion:
> >     https://mail.lacnic.net/mailman/options/lacnog
> >     >>>>>>>>>
> >     >>>>>>>>> _______________________________________________
> >     >>>>>>>>> LACNOG mailing list
> >     >>>>>>>>> LACNOG en lacnic.net <mailto:LACNOG en lacnic.net>
> >     >>>>>>>>> https://mail.lacnic.net/mailman/listinfo/lacnog
> >     >>>>>>>>> Cancelar suscripcion:
> >     https://mail.lacnic.net/mailman/options/lacnog
> >     >>>>>>>>> _______________________________________________
> >     >>>>>>>>> LACNOG mailing list
> >     >>>>>>>>> LACNOG en lacnic.net <mailto:LACNOG en lacnic.net>
> >     >>>>>>>>> https://mail.lacnic.net/mailman/listinfo/lacnog
> >     >>>>>>>>> Cancelar suscripcion:
> >     https://mail.lacnic.net/mailman/options/lacnog
> >     >>>>>>>>>
> >     >>>>>>>>> _______________________________________________
> >     >>>>>>>>> LACNOG mailing list
> >     >>>>>>>>> LACNOG en lacnic.net <mailto:LACNOG en lacnic.net>
> >     >>>>>>>>> https://mail.lacnic.net/mailman/listinfo/lacnog
> >     >>>>>>>>> Cancelar suscripcion:
> >     https://mail.lacnic.net/mailman/options/lacnog
> >     >>>>>>>>
> >     >>>>>>>>
> >     >>>>>>>> _______________________________________________
> >     >>>>>>>> LACNOG mailing list
> >     >>>>>>>> LACNOG en lacnic.net <mailto:LACNOG en lacnic.net>
> >     >>>>>>>> https://mail.lacnic.net/mailman/listinfo/lacnog
> >     >>>>>>>> Cancelar suscripcion:
> >     https://mail.lacnic.net/mailman/options/lacnog
> >     >>>>>>>
> >     >>>>>>>
> >     >>>>>>> --
> >     >>>>>>>
> >     >>>>>>> *Ivan ChaperoÁrea Técnica y Soporte*
> >     >>>>>>> Fijo: 03464-470280 (interno 535) | Móvil:  03464-155-20282
> >     | Skype ID:
> >     >>>>>>> ivanchapero
> >     >>>>>>> --
> >     >>>>>>> GoDATA Banda Ancha - CABLETEL S.A. | Av. 9 de Julio 1163 -
> >     2183 - Arequito
> >     >>>>>>> - Santa Fe - Argentina
> >     >>>>>>>
> >     >>>>>>>
> >     >>>>>>>
> >     >>>>>>>
> >     >>>>>>>
> >     >>>>>>>
> >     >>>>>>>
> >     >>>>>>>
> >     >>>>>>> _______________________________________________
> >     >>>>>>> LACNOG mailing list
> >     >>>>>>> LACNOG en lacnic.net <mailto:LACNOG en lacnic.net>
> >     >>>>>>> https://mail.lacnic.net/mailman/listinfo/lacnog
> >     >>>>>>> Cancelar suscripcion:
> >     https://mail.lacnic.net/mailman/options/lacnog
> >     >>>>>>
> >     >>>>>>
> >     >>>>>>
> >     >>>>>> _______________________________________________
> >     >>>>>> LACNOG mailing list
> >     >>>>>> LACNOG en lacnic.net <mailto:LACNOG en lacnic.net>
> >     >>>>>> https://mail.lacnic.net/mailman/listinfo/lacnog
> >     >>>>>> Cancelar suscripcion:
> >     https://mail.lacnic.net/mailman/options/lacnog
> >     >>>>> _______________________________________________
> >     >>>>> LACNOG mailing list
> >     >>>>> LACNOG en lacnic.net <mailto:LACNOG en lacnic.net>
> >     >>>>> https://mail.lacnic.net/mailman/listinfo/lacnog
> >     >>>>> Cancelar suscripcion:
> >     https://mail.lacnic.net/mailman/options/lacnog
> >     >>>> _______________________________________________
> >     >>>> LACNOG mailing list
> >     >>>> LACNOG en lacnic.net <mailto:LACNOG en lacnic.net>
> >     >>>> https://mail.lacnic.net/mailman/listinfo/lacnog
> >     >>>> Cancelar suscripcion:
> >     https://mail.lacnic.net/mailman/options/lacnog
> >     >>> _______________________________________________
> >     >>> LACNOG mailing list
> >     >>> LACNOG en lacnic.net <mailto:LACNOG en lacnic.net>
> >     >>> https://mail.lacnic.net/mailman/listinfo/lacnog
> >     >>> Cancelar suscripcion:
> https://mail.lacnic.net/mailman/options/lacnog
> >     >> _______________________________________________
> >     >> LACNOG mailing list
> >     >> LACNOG en lacnic.net <mailto:LACNOG en lacnic.net>
> >     >> https://mail.lacnic.net/mailman/listinfo/lacnog
> >     >> Cancelar suscripcion:
> https://mail.lacnic.net/mailman/options/lacnog
> >     >>
> >     > _______________________________________________
> >     > LACNOG mailing list
> >     > LACNOG en lacnic.net <mailto:LACNOG en lacnic.net>
> >     > https://mail.lacnic.net/mailman/listinfo/lacnog
> >     > Cancelar suscripcion:
> https://mail.lacnic.net/mailman/options/lacnog
> >     _______________________________________________
> >     LACNOG mailing list
> >     LACNOG en lacnic.net <mailto:LACNOG en lacnic.net>
> >     https://mail.lacnic.net/mailman/listinfo/lacnog
> >     Cancelar suscripcion: https://mail.lacnic.net/mailman/options/lacnog
> >
> >
> >
> >
> > _______________________________________________
> > LACNOG mailing list
> > LACNOG en lacnic.net
> > https://mail.lacnic.net/mailman/listinfo/lacnog
> > Cancelar suscripcion: https://mail.lacnic.net/mailman/options/lacnog
> >
> _______________________________________________
> LACNOG mailing list
> LACNOG en lacnic.net
> https://mail.lacnic.net/mailman/listinfo/lacnog
> Cancelar suscripcion: https://mail.lacnic.net/mailman/options/lacnog
>
------------ próxima parte ------------
Se ha borrado un adjunto en formato HTML...
URL: <https://mail.lacnic.net/pipermail/lacnog/attachments/20151218/110ac446/attachment.html>


Más información sobre la lista de distribución LACNOG