There is a mechanism, it's the point to point tunnels. Most gateways support that. The routing table is designed to match for point to point gateways before going to the default AMPR gateway at UCSD.

From a configuration perspective, the easy configuration approach is to

first route everything through UCSD to make sure one has mastered local gateway tunneling configuration. Then the local configuration should be expanded to perform direct tunneling to AMPR hosts/gateways and the UCSD gateway should be the lowest priority route. Assi

-----Original Message----- From: 44Net [mailto:44net-bounces+assi=kiloxray.com@hamradio.ucsd.edu] On Behalf Of R P Sent: Saturday, March 26, 2016 9:18 AM To: AMPRNet working group 44net@hamradio.ucsd.edu Subject: Re: [44net] Testers/Consideration/Inquiry - Coordinating the Private AS Numbers

(Please trim inclusions from previous messages) _______________________________________________

..snip...

If there was a mechanism to allow the traffic to go to any local 44 gateway and then the packet will go to the local Internet the trip would be much shorter but i dont know how it can be done these days that every IPS block Source 44 Net address from passing through as for 44 net to 44 net trafic it look ok because it tunnel direct to the gateway and not passing through AMPRGW the only thing I can think off is to put a secondary portal for redundancy . Ronen - 4Z4ZQ http://www.ronen.org