26 Apr
2022
26 Apr
'22
7:02 p.m.
In short it is technically possible, but not recommended as a stable/production way of
doing things.
TL;DR
Strictly speaking you could do this without your own ASN but you would have to setup some
internal routing between the two providers and your network to ensure that your network is
reachable to and from both providers, for example if you sent out a packet of data via
provider A but the destination return packet came via provider B. You may also run into
issues with any stateful services if packets take different paths. Some carriers may also
drop one of the routes, depending on how the route objects are setup.
Best practice says get your own ASN and do it “properly”.
73,
Chris - G1FEF
On 26 Apr 2022, at 11:18, R.D. Montgomery via 44net
<44net(a)mailman.ampr.org> wrote:
Antonios is correct. Getting your own ASN is not required if you work through a hosting
company. Perhaps this is an opportunity for us to update the Wiki with the providers we
are aware of? I'd be happy to do this.
I know of:
Vultr <https://www.vultr.com/>. No BGP setup fees or added fees. Available to the
lowest VM plan.
SpartanHost <https://spartanhost.org/>.
Inferno Communications <https://infernocomms.com/>. London-based company, LIR, and
extremely helpful.
There is a BGP-community updated list, some of the providers may be too complex for a
simple network learning option on the cheap. But feel free to take a look at
https://bgp.services/ <https://bgp.services/>
Hope this helps &
Stay well!
_________________________
Ronnie Montgomery (WØrdm)
Missouri AMPRnet Coordinator <https://mo.ampr.org/>
𝜋.666.4.999 <tel://3146664999> | rdm(a)rdm.io <mailto:rdm@rdm.io>
https://mo.ampr.org <https://mo.ampr.org/>
On Tue, Apr 26, 2022 at 4:52 AM Antonios Chariton (daknob) via 44net
<44net(a)mailman.ampr.org <mailto:44net@mailman.ampr.org>> wrote:
I don’t think a public AS is absolutely required if you don’t want to get one. If you can
find another company that does it similarly to Vultr, then you can begin even today. It’s
just that people will see this IP prefix announced both from Vultr as well as the new
provider. And they will take the closest route anyways. You will just have to create two
route objects instead of one though.
However, getting an AS + IPv6 is a great to expand and add IPv6 to your network, and
allows for more options in the future.
If Switzerland is acceptable (it’s close to Milano, with very good connectivity), then
maybe I can help.. There are also VM providers here that offer a similar service to Vultr
for almost the same cost (and do BGP) and you can also go to them directly.
On Mon, Apr 25, 2022 at 4:30 AM Toussaint OTTAVI
via 44net <44net(a)mailman.ampr.org <mailto:44net@mailman.ampr.org>> wrote:
Le 24/04/2022 à 15:04, Colin Bodor a écrit :
_______________________________________________
44net mailing list -- 44net(a)mailman.ampr.org <mailto:44net@mailman.ampr.org>
To unsubscribe send an email to 44net-leave(a)mailman.ampr.org
<mailto:44net-leave@mailman.ampr.org>
_______________________________________________
44net mailing list -- 44net(a)mailman.ampr.org
To unsubscribe send an email to 44net-leave(a)mailman.ampr.org I can announce for you as well, on a good blend
of transit via as 55016 out of Alberta Canada. Can also provide VPS.
Thank you very much. Echolink traffic from here often goes through VK gateways (!!!) ,
but I'd like to avoid BGP routing through VE, HI :-) I already have several BGP
options in France. And I'll see if I can find something in Italy for optimal
redundancy (we'll have a new connection to a submarine cable landing in Genova / pity
Vultr does not have any data center in Genova/Milano)
73 de TK1BI
_______________________________________________
44net mailing list -- 44net(a)mailman.ampr.org <mailto:44net@mailman.ampr.org>
To unsubscribe send an email to 44net-leave(a)mailman.ampr.org
<mailto:44net-leave@mailman.ampr.org>
_______________________________________________
44net mailing list -- 44net(a)mailman.ampr.org <mailto:44net@mailman.ampr.org>
To unsubscribe send an email to 44net-leave(a)mailman.ampr.org
<mailto:44net-leave@mailman.ampr.org>