Tom is right.
There is absolutely no reason to policy route any outgoing 44/8 traffic to UCSD, since it will be dropped anyway, because UCSD doesn't forward it. The default behavior shoud be to NAT the traffic for which no specific route exists to the public IP, just like any outgoing traffic not in the 44/8 segment.
This is an oddity that remained in the munge script from times long gone, which actually makes no sense.
-----Original Message----- From: 44net-bounces+marius=yo2loj.ro@hamradio.ucsd.edu [mailto:44net-bounces+marius=yo2loj.ro@hamradio.ucsd.edu] On Behalf Of Tom Hayward Sent: Wednesday, November 12, 2014 19:15 To: AMPRNet working group Subject: Re: [44net] Gateways with external address in net-44
(Please trim inclusions from previous messages) _______________________________________________ On Wed, Nov 12, 2014 at 5:07 AM, Brian n1uro@n1uro.ampr.org wrote:
policy route 44/8 via their tunnel interface
I think we're getting a bit ahead of ourselves here proposing new special announcements.
Here's another idea: don't assume anything spans the whole 44/8. Instead of policy-routing 44/8, policy route for each of the routes found in the encap. 44.24.221.0/24 isn't in the encap, so you should source packets to it from your commercial ISP source IP. UCSD is not involved.
Tom KD7LXL _________________________________________ 44Net mailing list 44Net@hamradio.ucsd.edu http://hamradio.ucsd.edu/mailman/listinfo/44net