IRR and Hurricane Electric and RIPE
First Message on here, please go easy as I am learning every day, just recently a number of our customers have been complaining that they cannot get on to various web sites, so I sent an email to HE, and got this reply back Hello Teledesign AS41614 and your BGP Query Looks like you do not have valid IRR entries for some entries. http://irrexplorer.nlnog.net/search/91.204.244.0/24 says "Prefix is in DFZ, but NOT registered in any IRR You are NOT getting routed to the whole Internet. From BGP.HE.NET https://bgp.he.net/AS41614#_prefixes You should have GREEN check mark next to the prefixes. From route-views.oregon-ix.net: route-views>sh ip b 91.204.244.0/24 l | i 1299 route-views> Please ensure all of your prefixes have valid IRR entries. It seems these may be getting filtered by remote networks. Documentation is available here, but you essentially need to create a route object with your ASN as the origin http://fcix.net/whitepaper/2018/07/14/intro-to-irr-rpsl.html =================================================== could anyone help me find a simple "How To Document" that I can follow and do what HE are asking me to do, or is it something I can ask RIPE to do on my behalf thanks in advance to all Peter ( newbie sysadmin ) Sent via RIPE Forum -- https://www.ripe.net/participate/mail/forum
Hi Peter, You will need to register both 'route' and 'route6' objects for routes assigned to your LIR account at $RIR[0]. HE only very recently started doing route filtering of their customers and peering partners. Which is why you only recently hit into the mentioned issue. [0]: meaning either ripe, arin, lacnic, apnic, afrinic etc. https://bgp.he.net/AS41614 http://routing.he.net/?cmd=search&pattern=AS41614 So depending on from which prefixes the customers complaining comes from. You will then need to go to the RIPE NCC Database https://apps.db.ripe.net/ and register the missing route objects. /Christoffer $ whois -h whois.ripe.net -rB -T route,route6 -i mnt-by NSE-MNT | egrep "route(6)?" route: 194.24.166.0/23 route: 217.18.80.0/21 route: 217.18.88.0/21 route: 77.247.192.0/22 route: 77.247.196.0/24 route: 77.247.197.0/24 route: 77.247.198.0/24 route: 77.247.199.0/24 $ whois -h whois.ripe.net -rB -T inetnum,inet6num -i mnt-by NSE-MNT | egrep "inet(6)?num" inetnum: 194.24.166.0 - 194.24.167.255 inetnum: 217.18.80.0 - 217.18.83.255 inetnum: 217.18.80.0 - 217.18.95.255 inetnum: 217.18.84.0 - 217.18.84.255 inetnum: 217.18.85.0 - 217.18.85.3 inetnum: 217.18.85.128 - 217.18.85.191 inetnum: 217.18.85.16 - 217.18.85.31 inetnum: 217.18.85.32 - 217.18.85.35 inetnum: 217.18.85.36 - 217.18.85.51 inetnum: 217.18.85.4 - 217.18.85.7 inetnum: 217.18.85.52 - 217.18.85.55 inetnum: 217.18.85.56 - 217.18.85.63 inetnum: 217.18.85.64 - 217.18.85.127 inetnum: 217.18.85.8 - 217.18.85.15 inetnum: 217.18.86.0 - 217.18.86.63 inetnum: 217.18.86.128 - 217.18.86.191 inetnum: 217.18.86.192 - 217.18.86.255 inetnum: 217.18.86.64 - 217.18.86.95 inetnum: 217.18.86.96 - 217.18.86.103 inetnum: 217.18.88.0 - 217.18.88.255 inetnum: 217.18.89.0 - 217.18.89.31 inetnum: 217.18.89.160 - 217.18.89.191 inetnum: 217.18.89.192 - 217.18.89.255 inetnum: 217.18.89.32 - 217.18.89.39 inetnum: 217.18.89.40 - 217.18.89.47 inetnum: 217.18.89.48 - 217.18.89.55 inetnum: 217.18.89.56 - 217.18.89.59 inetnum: 217.18.89.64 - 217.18.89.95 inetnum: 217.18.90.0 - 217.18.90.63 inetnum: 217.18.90.128 - 217.18.90.191 inetnum: 217.18.90.192 - 217.18.90.255 inetnum: 217.18.90.64 - 217.18.90.127 inetnum: 217.18.91.0 - 217.18.91.3 inetnum: 217.18.91.16 - 217.18.91.23 inetnum: 217.18.91.176 - 217.18.91.191 inetnum: 217.18.91.192 - 217.18.91.255 inetnum: 217.18.91.24 - 217.18.91.31 inetnum: 217.18.91.32 - 217.18.91.47 inetnum: 217.18.91.4 - 217.18.91.7 inetnum: 217.18.91.8 - 217.18.91.15 inetnum: 217.18.92.0 - 217.18.92.63 inetnum: 217.18.92.128 - 217.18.92.191 inetnum: 217.18.92.192 - 217.18.92.255 inetnum: 217.18.92.64 - 217.18.92.127 inetnum: 217.18.93.0 - 217.18.93.63 inetnum: 217.18.93.128 - 217.18.93.191 inetnum: 217.18.93.64 - 217.18.93.127 inetnum: 217.18.94.0 - 217.18.94.63 inetnum: 217.18.94.128 - 217.18.94.191 inetnum: 217.18.94.192 - 217.18.94.255 inetnum: 217.18.94.64 - 217.18.94.127 inetnum: 217.18.95.192 - 217.18.95.255 inetnum: 77.247.192.0 - 77.247.199.255 inetnum: 77.247.194.0 - 77.247.194.255 inetnum: 77.247.195.0 - 77.247.195.255 inetnum: 77.247.196.0 - 77.247.196.15 inetnum: 77.247.196.16 - 77.247.196.23 inetnum: 77.247.196.24 - 77.247.196.31 inetnum: 77.247.196.32 - 77.247.196.39 inetnum: 77.247.196.40 - 77.247.196.47 inetnum: 77.247.196.48 - 77.247.196.63 inetnum: 77.247.196.64 - 77.247.196.79 inetnum: 77.247.196.80 - 77.247.196.87 inetnum: 77.247.197.48 - 77.247.197.51 inetnum: 91.204.244.0 - 91.204.247.255
Peter, If the customers having IPv4 addresses them self. (& maybe an ASN, too). And have NOT YET registered a route object for their prefixes in the RIPE NCC database. & it is these source addresses the customers in question complaining about unreliability to the Internet (though AS6939(HE)). Then the responsibility to register route objects is on the customers themself (unless you have a sponsoring LIR agreement with the customer(s) in question. /Christoffer
participants (2)
-
Christoffer Hansen -
Peter Courtney