I can break down the connection into
two parts, each with their own subparts. A possible
categorisation could be:
Part 1 - Connecting to amprnet. This
part describes the act of connecting to the wider network using a
connection method of your choice. Here there's 3 main
possibilities:
a) BGP - for when you want to connect
your subnet directly to the Internet for Internet facing services
or better Internet access (where permitted). BGP has a specific
process with multiple components, including authorisation (getting
a LOA from ARDC and working with your NSP) and advertising routes
(provider dependent, but commonly used providers like Vultr could
be specifically documented).
b) IPIP mesh - here methods to connect
your gateway to the IPIP mesh can be documented, including
requirements (like needing to be able to pass IP protocol 44 to
your host/router).
c) VPN - Instructions on how to use any
official ARDC VPN system to connect to the network.
A lot of the above is actually
documented, I've been able to follow the existing documentation
for these steps, though I do agree having more formats would be
useful for some - I personally find instructional videos useless,
but many people find them helpful, which is a good reason for
someone who's interested to produce them and donate that effort to
the community.
Part 2 - This is how you structure your
local network behind your gateway. Here, the choices for
configuration are practically endless and limited by one's
imagination and available systems and needs. Probably the best
people can do here is present their own configurations as working
options for others to look at - the wiki as well as YouTube would
definitely be good media options here.
In my case, I currently have two very
different configurations running. For my BGP range, I have a
Vultr VPS announcing my /24 to the world. Half of my range (/25)
terminates on that VPS, while the other /25 is routed via a tunnel
to another VPS, to provide additional public IPs for services
hosted there (pre existing Echolink conferences and additional
proxies). The different routes for the /25s are announced to
Vultr in my bird.conf, while the entire /24 is announced to the
world as a single route (as required).
On my IPIP range, I terminate my IPIP
tunnel on another VPS, where being on the open Internet and away
from my other networks simplifies the configuration. To get
traffic to here, I use ZeroTier to create a virtual LAN, with the
remote gateway as the router for the subnet. I can either connect
each host on my LAN directly vis ZeroTier, or I have created a
bridged LAN segment where I can connect hosts directly via
Ethernet and assign them an IP from my range. There are some
configuration details worthy of documentation here, from setting
up the basic network and assigning IPs to directly connected
clients, to setting up the bridge and also enabling the use of
public addresses (44.x is public address space) and optionally
setting the default route via ZeroTier.
On 5/4/24 6:04 am, Steve L via 44net
wrote:
While I hear what you are saying, and I encourage
anyone and everyone to document their particular use and
setup.......
In reality in computer networking there is no one way to
implement a network. Network size and use cases will be the
largest implementation factors.
There is no one size fits all, and their is no easy plug in
play in networking. If all you need is a single endpoint then
of course that is fairly simple.
Wouldn't it be great if we had youtube videos
and Wikis implemented for this.
Online education should be a goal.
Best,
Lori Guidos
KE6INO
Greetings!
Is there a good place to find a good explanation of how to
implement the 44 network? I’m probably making things more
complicated in my head than they really are, but I don’t
want to configure things wrong.
Thanks!!
73
Dave, AI7R
_______________________________________________
44net mailing list -- 44net@mailman.ampr.org
To unsubscribe send an email to 44net-leave@mailman.ampr.org
_______________________________________________
44net mailing list -- 44net@mailman.ampr.org
To unsubscribe send an email to 44net-leave@mailman.ampr.org
_______________________________________________
44net mailing list -- 44net@mailman.ampr.org
To unsubscribe send an email to 44net-leave@mailman.ampr.org
--
73 de Tony VK3JED/VK3IRL
http://vkradio.com