[lacnog] Prefix Hijacking

[Alex Ojeda]

Hi


  1.  this is not hijack because the AS263774 NOT originate your network. act as transit for your AS 267759
  2.  by my side, Is not visible your "problematic" announce

only have 1 path (for /23, not your specific /24)

BGP routing table entry for 45.167.18.0/23
Paths: (1 available, best #1, table default)
  Not advertised to any peer
  64515 65534 20473 1299 174 28145 264012 267759





Alex Matias Ojeda Mercado
Chile Networks SpA.
Fono:  +56 232 100 300
Móvil: +56 9 719 22 362
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> en nombre de Lucas Willian Bocchi <lucas.bocchi en gmail.com>
Enviado: jueves, 19 de diciembre de 2019 13:10
Para: lacnog en lacnic.net <lacnog en lacnic.net>
Asunto: [lacnog] Prefix Hijacking

Hello.

We have entered in contact with AS263774 informing the problem but we won't provide any solution to the trouble.

Our BGP session with the AS263774 are totally down and the announces don't cease to exists. We believe that these provider hijack our announces

Thu Dec 19 16:08:16.916 UTC
BGP routing table entry for 45.167.18.0/24<http://45.167.18.0/24>
Versions:
  Process           bRIB/RIB  SendTblVer
  Speaker          497636789   497636789
Last Modified: Dec 19 15:36:44.535 for 00:31:32
Paths: (1 available, best #1)
  Advertised IPv4 Unicast paths to peers (in unique update groups):
    38.5.0.99
  Path #1: Received by speaker 0
  Advertised IPv4 Unicast paths to peers (in unique update groups):
    38.5.0.99
  3356 3549 263774 263774 267759
    4.68.111.177 (metric 103030) from 38.28.1.83 (38.28.1.238)
      Origin IGP, metric 4294967294, localpref 100, valid, internal, best, group-best, import-candidate
      Received Path ID 0, Local Path ID 1, version 497636789
      Community: 174:11401 174:20666 174:21100 174:22005
      Originator: 38.28.1.238, Cluster list: 38.28.1.83, 38.28.1.67

How are the correct solution to the case? The NOC are already alerted about the problem but says that "all is ok on your side".

Regards.
------------ próxima parte ------------
Se ha borrado un adjunto en formato HTML...
URL: <https://mail.lacnic.net/pipermail/lacnog/attachments/20191219/4810d03a/attachment-0001.html>