Hi,
That won't be much trouble, even in the NAT scenario if these traffic
originates/ends on the same router/redundancy group, in case of switch
over, the connections over the old routes will hit a dead end, but new
ones will reach you. Outage can last only a few seconds.
If you are not using NAT, just peer with your upstream and configure
preferences, one link down, the routes will be gone automatically.
There's way too much fun in the BGP!
73,
BH1XQV
On 2/24/20 5:18 PM, Toussaint OTTAVI via 44Net wrote:
Hi,
Thank you all for your answers and comments
Le 22/02/2020 à 05:09, Tony Langdon via 44Net a écrit :
It is
mandatory. But like IPv4 addresses, they are a limited
resource, and you need to have connections to multiple backbone
providers to even apply for one. IOW, you need to be in the
business. Nearly all of us here will use the Public ASN of our
provider.
That's what I did, because I have no need to peer with anyone. My
provider does all of that. All I had to do was to get the LOA (then
from Brian) to them and possibly their upstream (there wa san extra
little step required in the paperwork from memory), and once the
paperwork was sorted, everything started working. :)
That's what I did with Vultr. That's also what I'm planning to do with
my new business operator. With a single BGP operator, there's no need
to have my own public ASN.
But how could I manage redundancy / fault tolerance between two BGP
operators ?
For incoming traffic, there's no problem, I can handle any incoming
packet whatever the provider.
But how could I handle outgoing traffic ? F/ex, my current Vultr VPS
is hosted in Paris, and I'm tunneling from Corsica to Paris. Last
week, they had a network problem, and the BGP routing was down. All
outbound packets sent from my local router to the Vultr BGP VPS were
dropped. Locally, I do not have any easy way to see if Vultr network
is working or not, so that I could redirect outbound traffic to my 2nd
provider.
For now, I do not have any idea about how to handle outbound
redundancy. Having a public ASN, and a local BGP router which peers
with the two providers, may be a clue. Am I wrong ?
73 de TK1BI
_________________________________________
44Net mailing list
44Net(a)mailman.ampr.org
https://mailman.ampr.org/mailman/listinfo/44net