On Sun, Aug 11, 2013 at 9:21 PM, Gamalier Sanchez, TRI
<[email protected]> wrote:
> Just a little correction about the block.
>
> It's the 186.150/16
>
> Maybe the block available to look from a route server is a /19 subnet.
>
>

sure. so... maybe you could send an update to the opened ticket with
google with an example source-/32 that's a problem?

-chris

>
> El 11/08/2013, a las 21:08, "Randy Bush" <[email protected]> escribió:
>
>>> The block is announced to our internet providers. We can see at route
>>> servers.
>>
>> then you are using different route servers than i am
>>
>> route-views>sh ip bg 186.50.0.0
>> BGP routing table entry for 186.50.0.0/20, version 307454
>>                                      ^^^
>> randy
>
>
> Importante: Este mensaje o correo electrnico y todos sus archivos adjuntos 
> pueden contener informacin confidencial y es exclusivamente para el uso del 
> individuo o entidad al cual es enviado. Si usted no es el destinatario del 
> mismo favor desecharlo inmediatamente, borrndolo de su computadora, y proceda 
> a informar al remitente respondiendo este correo electrnico. Queda 
> formalmente notificado que cualquier divulgacin, distribucin, reproduccin, 
> copiado o uso de esta informacin, por otras personas que no sean las 
> destinatarias, queda estrictamente prohibido. Las opiniones expresadas en 
> este mensaje son propias del autor y no necesariamente coinciden con las de 
> TRICOM, S.A. www.tricom.net
>
> Important: This message or electronic mail and all attached files therein 
> could contain confidential information and it is of the exclusive use of the 
> individual or entity to which it is sent. If you are not the intended user of 
> the message, please discard it immediately by erasing the e-mail from your 
> computer, and proceed to inform the recipient by replying this electronic 
> mail. It is formally notified that any and all dissemination, distribution, 
> reproduction, copying or use of this information, by any other persons who 
> are not the recipients, is strictly prohibited. Any opinions expressed in 
> this message are of the property of the author and do not necessarily express 
> or coincide with those of TRICOM, S.A. www.tricom.net
>

Reply via email to