Apparently your subnet is still not advertised in the DFZ. Either Vultr is not receiving your advertisement, or they are ignoring it for some reason.. Is your LOA okay and submitted to Vultr? If yes, I would open up a ticket with Vultr and ask them if they are receiving your advertisement
-- $ show ip bgp 44.135.59.0/24 % Network not in table --
73
Ruben ON3RVH
-----Original Message----- From: 44Net 44net-bounces+on3rvh=on3rvh.be@mailman.ampr.org On Behalf Of pete M via 44Net Sent: Friday, January 15, 2021 19:25 To: AMPRNet working group 44net@mailman.ampr.org Cc: pete M petem001@hotmail.com Subject: Re: [44net] BGP/openvpn finally all ok.
OK I did the change in the interfaces file. I now have those route
ip route show 0.0.0.0/1 via 44.135.59.1 dev ens3 default via 207.246.122.1 dev ens3 44.135.59.0/24 dev tun0 proto kernel scope link src 44.135.59.1 44.135.59.0/24 dev ens3 proto kernel scope link src 44.135.59.1 128.0.0.0/1 via 44.135.59.1 dev ens3 169.254.169.254 via 207.246.122.1 dev ens3 207.246.122.0/23 dev ens3 proto kernel scope link src 207.246.122.57
Now the birdc show birdc s route export vultr BIRD 1.6.6 ready. 44.135.59.0/24 via 207.246.122.57 on ens3 [static1 18:22:30] * (200)
________________________________________ De : 44Net 44net-bounces+petem001=hotmail.com@mailman.ampr.org de la part de Nate Sales via 44Net 44net@mailman.ampr.org Envoyé : 15 janvier 2021 12:53 À : 44net@mailman.ampr.org Cc : Nate Sales Objet : Re: [44net] BGP/openvpn finally all ok.
Thanks, so there is a route exported to Vultr. Please run "birdc s route export vultr" so we can see what the route is.
I would also suggest modifing your import filter to permit 0.0.0.0/0. In this case it's not as much of a problem because you only have a single peer and they're only sending a default route, but it is not a good idea to point static routes at a BGP peer. Doing that on the public internet is a quick way to cause problems :)
Nate KJ7DMC
On Fri, 2021-01-15 at 17:48 +0000, pete M via 44Net wrote:
#Could you show the output of "birdc s protocols all" - and "birdc s #route export vultr" to make sure the route is indeed being exported #over the session.
here it is.
# birdc s protocols all BIRD 1.6.6 ready. name proto table state since info device1 Device master up 17:06:16 Preference: 240 Input filter: ACCEPT Output filter: REJECT Routes: 0 imported, 0 exported, 0 preferred Route change stats: received rejected filtered ignored accepted Import updates: 0 0 0 0 0 Import withdraws: 0 0 --- 0 0 Export updates: 0 0 0 --- 0 Export withdraws: 0 --- --- --- 0
static1 Static master up 17:06:16 Preference: 200 Input filter: ACCEPT Output filter: REJECT Routes: 1 imported, 0 exported, 1 preferred Route change stats: received rejected filtered ignored accepted Import updates: 5 0 0 0 5 Import withdraws: 4 0 --- 0 4 Export updates: 0 0 0 --- 0 Export withdraws: 0 --- --- --- 0
vultr BGP master up 17:06:20 Established Preference: 100 Input filter: REJECT Output filter: ACCEPT Routes: 0 imported, 1 exported, 0 preferred Route change stats: received rejected filtered ignored accepted Import updates: 1 0 1 0 0 Import withdraws: 0 0 --- 1 0 Export updates: 5 0 0 --- 5 Export withdraws: 4 --- --- --- 4 BGP state: Established Neighbor address: 169.254.169.254 Neighbor AS: 64515 Neighbor ID: 209.222.14.236 Neighbor caps: refresh restart-aware AS4 add-path-rx Session: external multihop AS4 Source address: 207.246.122.57 Hold timer: 137/180 Keepalive timer: 10/60
44Net mailing list 44Net@mailman.ampr.org https://mailman.ampr.org/mailman/listinfo/44net
_________________________________________ 44Net mailing list 44Net@mailman.ampr.org https://mailman.ampr.org/mailman/listinfo/44net
_________________________________________ 44Net mailing list 44Net@mailman.ampr.org https://mailman.ampr.org/mailman/listinfo/44net