12 Jul
2020
12 Jul
'20
5:09 a.m.
Running .ham for my own equipment, its easy enough to arrange for intra Ham announcements
without
getting TLD recognized under IANA. Provide a anycast range that we all point DNS
resolution.
Adam
KC7GDY
On Jul 11, 2020, at 3:03 PM, Nate Sales via 44Net
<44net(a)mailman.ampr.org> wrote:
How would you suggest structuring the neighbor relationships here?
Would there be a bunch of route reflectors in each region, or would
this become more of a mesh topology?
Nate
KJ7DMC
On Sat, Jul 11, 2020 at 2:51 PM Rob Janssen via 44Net
<44net(a)mailman.ampr.org> wrote:
I am thinking more of using BGP to distribute the info, could be used as
routing
info as well but not necessarily, usually one can configure BGP to store
the info
in a separate routing table used only for lookup in a firewall rule or
similar.
Everyone only needs to advertise their own IPv6 networks, and will
receive all
the others from the peers. No need to put all that info in a central
database!
Of course you would require some BGP peers and the portal could be a source
of contact info to set them up. But once you have enough peers so that the
network does not split up into islands when some random participant stops,
it does not require some central resource where all info is stored. And when
we would have those global routers as explained in my proposal, they could
run the BGP instance for this as well (and still not be essential for
its operation).
Rob
On 7/11/20 11:41 PM, Erik Seidel wrote:
_________________________________________
44Net mailing list
44Net(a)mailman.ampr.org
https://mailman.ampr.org/mailman/listinfo/44net
Make a list of HAMs who are announcing AMPRnet prefixes along with
their locations and their contact info. Put it on the ampr.org portal
so everybody can access it. That would be more formalized without
being needlessly centralized.
_________________________________________
44Net mailing list
44Net(a)mailman.ampr.org
https://mailman.ampr.org/mailman/listinfo/44net