Rob, please stop stating the fact below. UCSD is not able to forward tunnel traffic to other networks.
From UCSD's point of view, there either exists a tunnel to the destination,
and then sthe source shall have a direct tunnel to it, or it is unknown, and then neither UCSD, nor the gateway has data on it. So, sending that unknown traffic to UCSD is pointless, since the ampr-gw has the same information as you on the tunnels. If you can not resolve it locally, neither can the UCSD gateway. The only systems that fall into this category are the ones that are BGP announced. And the only way to reach them is via the regular internet, via your public IP to allow full routing, and thus access to them.
NO GATEWAY SHOULD EVER HAVE A DEFAULT 44/8 ROUTE TO UCSD BECAUSE IT DOESN'T WORK AND IS POINTLESS.
Marius, YO2LOJ
-----Original Message----- From: 44net-bounces+marius=yo2loj.ro@hamradio.ucsd.edu [mailto:44net-bounces+marius=yo2loj.ro@hamradio.ucsd.edu] On Behalf Of Rob Janssen Sent: Wednesday, June 17, 2015 22:49 To: 44net@hamradio.ucsd.edu Subject: Re: [44net] AMPRNet Interoperability with BGP
(...)
When such a system is on a source-address filtered internet connection, the default route for outgoing AMPRnet traffic (to 0.0.0.0/0) is to go via an IPIP tunnel to another mesh system that has unfiltered internet access. Typically the system at UCSD.