Re: [44net] Testers/Consideration/Inquiry - Coordinating the Private AS Numbers - 44net

26 Mar 2016

...
  - I'm not certain how one can reach
portal.ampr.org before establishing
 an Internet connection first 
Of course portal.ampr.org should be run on a net-44 address and preferably
have radio connectivity, but for reasons unknown to me it isn't.  As the
worldwide AMPRnet over radio is just a dream, it would not be likely that
everyone would be able to reach that system without internet any day.

You would need internet anyway to search and visit a webshop to buy the
equipment you need to be on radio...

...
  - You stated: "This is not a task of AMPRGR but
of portal.ampr.org..."
 The Portal is simply a backend to configure AMPRGW itself; and
 specifically in the case of IPIP tunnels using RIP44. In the future it
 plans to add DNS functionality, but keep in mind, this is just merely a
 website 
I am bringing this up only because I get the feeling that you don't understand
the topology of the network and the components involved very well.
The title of your initial message is also very indicative of that.  What you
brought up has zero to do with AS numbers and the issue of coordinating AS
numbers was already handled to everyone's satisfaction a couple of months ago.

...
  - I'm not sure how a DNS zone file relates to
real-time connectivity to
 a network 
Not to the connectivity directly, but certainly to the usability.
It appears that one of your goals is to use AMPRnet without internet connection
and that is not really practical when you don't have a DNS on it.   There is
a DNS server 44.0.0.1 but for most people it will be unreachable when they
don't have some internet tunnel.

...
  - AMPRGW is not the ideal route to all subnets because
it is not the
 most geographically closest AMPRNet node with an Internet connection. If
 other nodes were setup in the manner I'd like to test, any node willing
 to establish a session could potentially be a closer node 
I advise you to study the network topology before proposing to change it.
Traffic to another amprnet node does NOT flow through AMPRGW.

...
  - You note again "we have a full mesh:"
***Then please test by pinging
 MY gateway VIA N1URO's***. In your testing, do not connect directly to
 me or use AMPRGW. I will DOWN my tunl0 interface and only connect to
 another AMPR station with AMPRGW connectivity - via RF or over a VPN
 connection. 
...
       + it's my understanding this would fail -
STAR
      + you imply that it should work - MESH 

This is not what defines a star versus a mesh.  When you disconnect yourself
from the mesh and do not update the routing to be reachable via someone else's
connection, of course you will be unreachable.  What makes it a mesh is that
the reliance on AMPRGW that you bring forward all the time IS NOT THERE.
The pings I send to your gateway directly travel from my internet connection
to yours, NOT via AMPRGW.

We use a multi-level subnet system here.   We route the entire country
subnet to a single gateway which has radio and VPN connectivity to users in the
country.  Those users can also have their own IPIP gateway when they like.
In that case the traffic for their subnet will flow directly to them, but when
they stop that the traffic will go to our gateway and then to them via radio.

Of course there is no "alive" detection in the current IPIP gateway system,
so a route will not disappear from the announcements just because the internet
connection of that gateway is broken.  So you will have to disable the gateway
first (functionality that has been removed from the portal.ampr.org system
for reasons totally unclear to me, you now just have to delete the subnets)

Rob