Re: [44net] New ampr-ripd 1.16 and amprd 1.5 released

On 3 April 2017 at 20:29, Marius Petrescu <marius(a)yo2loj.ro> wrote: Hi, I have 44.131.14.0/24 advertised via BGP. This prefix is actually being anycasted from multiple locations, which wasn't really supported by the existing system and I hadn't gotten around to finding a solution yet. The prefix is split over multiple networks, and I am using IPIP encapsulation internally, so it was trivial to add the new gateway mechanism to my existing setup. The prefix was not previously "on-net", so I don't think I risk breaking anything with this experimental configuration. I have added a gateway at 44.131.14.255 and pointed the prefix to it on the portal. I am pulling the encap list for outbound routes every 2 hours, using a manual script which does the same thing of adding a route when it comes across a 44/8 gateway address. root@vpn:~# traceroute 44.130.122.3 traceroute to 44.130.122.3 (44.130.122.3), 30 hops max, 60 byte packets 1 London.AS206671 (45.63.97.98) 1.913 ms 1.880 ms 1.834 ms 2 44.130.122.3 (44.130.122.3) 30.611 ms 30.575 ms 30.515 ms The first hop is the nearest instance of my anycasted router that handles both BGP and the IPIP tunnels, it has 44.131.14.255 on a loopback interface. Wireshark confirms I am going out encapsulated from 45.63.97.98 to 44.130.122.2 and the replies are coming back encapsulated from 44.130.122.2 to 44.131.14.255. If you want to test it, 44.131.14.254 is a second loopback on the gateway that is used for status monitoring. 44.131.14.192 is a unicast node "inside" my network to check end to end connectivity. - Mike, M6XCV (PS. If you need anyone else to help with testing BGP stuff, I can advertise any prefix from my personal AS with minimal effort.)