4 Oct
2020
4 Oct
'20
2:42 p.m.
On Oct 4, 2020, at 13:17, Rob Janssen via 44Net
<44net(a)mailman.ampr.org> wrote:
Please make sure you understand that the use of BGP I am mentioning here
has nothing to do with the use of BGP on internet to route all the internet
networks. It is the same protocol, but they are different use cases.
Don't get confused when people say they have their AMPRnet subnet BGP
routed to them on internet, and other people propose to use BGP internal
to the AMPRnet network to route things the correct way, these are two
different things.
Rob
Yeah this thread kinda went off the rails. Originally we WERE talking about global
Internet BGP. That is what the folks need that are using net-44 for IRLP, Allstar,
Echolink, D-Star and various types of DMR. 44-net addresses that need access to and from
the global Internet.
It took my local data center provider about three weeks to set up advertising one of my
/23. Mostly waiting for all of their upstream providers to accept the newly advertised
routes. Vultr.com has a very slick set of tools allowing one to get it going in a few
hours, assuming proper license from ARDC is obtained. Neither one charges anything extra
for doing that.
But it is nothing anyone here can do on their own from home. Basically it requires support
from a large data center or ISP. All of my blocks are globally routable, courtesy of my
data center providers. I run an implementation of OpenVPN on a Linux VM to pass individual
addresses (/32) to client IRLP nodes.
BGP can be used for smaller scale network routing, although there are many other routing
protocols that may be better suited to smaller or isolated (Ampr only) networks.
-k9dc