Hmm, there are also global IPv4 multicast addresses :-)
Maybe it is worth some testing:
233.0.0.0/8 per RFC2770 - and here AMPR has its own 16 bit AS number, so 256
addresses could be available
234.0.0.0/8 per RFC 6034 - we could use 234.44.x.x in this scheme, even
split to country level.
If this would work, that would be great. But it depends on the ISP.
-----Original Message-----
From: Marius Petrescu
Sent: Friday, March 25, 2016 20:58
To: AMPRNet working group
Subject: Re: [44net] Testers/Consideration/Inquiry - Coordinating thePrivate
ASNumbers
(Please trim inclusions from previous messages)
_______________________________________________
This sounds nice in theory.
But you still need an initial database of peers to start the connections.
And that means a single point of failure and you are back to square 1.
The only way I see this feasible is to use IPv6 which offers global
multicast groups.
The nodes have only to send out some announcement of presence on that
address, and everyone worldwide which is subscribed to that multicast group
will get the announcements.
But since IPv6 is inaccessible to most of the internet users (due to "not
available", "I do not care if I have it" or "I don't want
it"), it will have
to wait.
Marius, YO2LOJ
-----Original Message-----
From: lleachii--- via 44Net
Sent: Friday, March 25, 2016 14:37
To: 44net(a)hamradio.ucsd.edu
Cc: lleachii(a)aol.com
Subject: [44net] Testers/Consideration/Inquiry - Coordinating the Private
ASNumbers
(Please trim inclusions from previous messages)
_______________________________________________
...
- My router (and, I would assume those of many others that have been
flashed, etc.) are capable of forwarding packets, regardless of
source/destination IP. We could test the possibility of switching from a
star (reliance on AMPRGW's 100% uptime for 'real-time' route updates) to
a mesh, where we peer with those who choose, have a large connection,
are physically interconnected to one another, etc.
- (in the future) anyone, including those on the Public Internet, could
volunteer to announce more specific routes for IPIP allocations (with
the proper authorization requested by the allocation holder) and then
maintain a tunnel, RF link, etc. - could connect to someone who could
provide the AMPRGW.
...
_________________________________________
44Net mailing list
44Net(a)hamradio.ucsd.edu
http://hamradio.ucsd.edu/mailman/listinfo/44net