The ip is fix, so no they did not change the ip. They could do it but I have a doamain name pointed to it and it is still working and the DNS is not at vultr so they have no control over it.
will have to check with vultur why bgp does not work
________________________________________ De : 44Net 44net-bounces+petem001=hotmail.com@mailman.ampr.org de la part de Dave Gingrich via 44Net 44net@mailman.ampr.org Envoyé : 15 janvier 2021 13:41 À : AMPRNet working group Cc : Dave Gingrich Objet : Re: [44net] BGP/openvpn finally all ok.
Your route is still not showing up. Time to open a ticket with Vultr, Show them the output from the birdc command.
Oh, did you power cycle the VPS? A reboot from linux is not enough. Beware, if you do not have a reserved IP, your main IP will likely change on the power cycle, requiring you to reconfigure things. You can reserve an IP, but they charge $3/mo. Sounds small, but if you are only paying $5 or $6 for the machine, it is significant.
-- Dave K9DC
On Jan 15, 2021, at 13:24, pete M via 44Net 44net@mailman.ampr.org wrote:
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)
_________________________________________ 44Net mailing list 44Net@mailman.ampr.org https://mailman.ampr.org/mailman/listinfo/44net