11 Aug
2021
11 Aug
'21
7:55 p.m.
On 8/11/21 2:33 PM, pete M via 44Net wrote:
You are again over simplyfing the situation to squeeze
your solution as possible.
For your solution to work we need a setup a list of net that are either ham only, ham and
internet, internet only.
Imagine that a ham with a /20 and he use them to supply ip to a few service for ham only,
some are for service for both internet and ham only, and some service just for the
internet for club server that have publicity running on it, so it should not be over the
air waves at all. and he supply a way to connect to ampr by a an rf network and each
endpoint can deceide to be A or B. the IP are all scattered between al the use case. Just
imagine the needed list to have that network running as it should by the pop. Now, we
continu with 500 new allocation that do the same, add a few thousand new user asking for a
/28 with each ip that can be used as any of the 3 possibility and put that in the routing
and or firewalling of the pop.
That is actually no problem at all! BGP manages
that automatically. As soon as a user connects to the PoP, their prefix will be announced
on the network and all the other routers (and users who choose to use BGP) will get the
new route. When they disconnect, the route vanishes and the same space may be routed as
part of a larger subnet, or become unreachable.
There is no need to manually maintain a list for that. That is the big difference with
the current IPIP mesh which uses a static table maintained via a webinterface at
portal.ampr.org. There it is the responsibility of the operators to enter the subnets
they route, and the data will remain there long after they have lost interest in being a
gateway.
Rob