I can announce for you as well, on a good blend of transit via as 55016 out of Alberta Canada. Can also provide VPS. ________________________________ From: Toussaint OTTAVI via 44net 44net@mailman.ampr.org Sent: Sunday, April 24, 2022 3:21:04 AM To: AMPRNet working group 44net@mailman.ampr.org Subject: [44net] Re: BGP announcement from two different locations ?
Hi Chris,
Le 24/04/2022 à 10:59, Chris Smith a écrit :
IIRC Vultr will allow you to announce to them from your own ASN if you have one
Thank you for your answer. I was not aware about that. Then, we need to : - Obtain an ASN from a LIR - Migrate our Vultr announcement to that private ASN - Arrange redundant announcement of that ASN from another provider
so how you would then route the prefix to another provider for announcement could get interesting.
It’s possible with tunnels I guess, but the traditional way would be to have your own BGP edge router in a datacenter and hook up feeds from two transit providers. Doing it this way also gives you the option of peering with multiple other networks, if you’re in a carrier neutral datacenter.
All our servers are hosted in a local data center (on our island of Corsica), but it has very limited transit capabilities, and no ISP providing BGP directly (ie, at affordable cost for a radio-club). Currently, we announce via a Vultr VPS in Paris, and we tunnel to Corsica. The second announcement is not defined yet. I still have to investigate all the available options, and choose two of them. Moreover, we plan to deploy a second 44Net data-center on the island. Then, we would have two DCs, connected to each other via iBGP, and each one having its own eBGP announcement. More to follow...
73 de TK1BI
_______________________________________________ 44net mailing list -- 44net@mailman.ampr.org To unsubscribe send an email to 44net-leave@mailman.ampr.org