I’m a network admin for the 44.24.240.0/20 network using the 44.24.221.1 gateway. Marius is exactly correct. 44.24.221.1 is NOT in the encap and is directly BGP announced. And the comments that this will cause problems for those who route all of 44/8 to USCD are correct. We have decided that for our own best interests (we can announce 44.24.221.1 at multiple peers, and thus have highly available tunnel endpoints for all who wish to connect), and in what we believe pushes forward progress for the network as a whole, this is our best option. A blanket route to UCSD for 44/8 is pretty shortsighted, and ignores all users (including ourselves) that announce via BGP, and limits what users can do for highly available gateways.
If a “reverse” list of users who announce via BGP and use 44/net addresses as tunnel endpoints would help with getting these routing setups better situated so traffic doesn’t end up lost in the loop, then I would be pleased to assist in it’s creation. Ideally, this would be put in place at UCSD itself, so that individual users could still route via UCSD, and UCSD would take care of sending it along to the endpoint. (Us or someone else)
Nigel K7NVH
On Nov 12, 2014, at 5:07 AM, Brian n1uro@n1uro.ampr.org wrote:
(Please trim inclusions from previous messages) _______________________________________________ On Wed, 2014-11-12 at 10:16 +0100, Rob Janssen wrote:
Ok, but then I think those gateway entries should not be distributed via RIP. When they are directly routable, should we use a tunnel to reach them?
That's only half the equasion. The other half is when one is SAFed (Source Address FilterED) and they policy route 44/8 via their tunnel interface, and anything else via UCSD... we either need to insure that we have a separate listing of 44-net IPs using BGP so we can reverse munge script those IPs.so that they're not trapped being policy routed via local tunnels, unless amprgate will handle tunnelled routing for these IPs...?
-- If Microsoft intended Windows to be for ham usage, they would have incorporated our protocols into their kernel.
73 de Brian Rogers - N1URO email: n1uro@n1uro.ampr.org Web: http://www.n1uro.net/ Ampr1: http://n1uro.ampr.org/ Ampr2: http://nos.n1uro.ampr.org Linux Amateur Radio Services axMail-Fax & URONode AmprNet coordinator for: Connecticut, Delaware, Maine, Maryland, Massachusetts, New Hampshire, Pennsylvania, Rhode Island, and Vermont.
44Net mailing list 44Net@hamradio.ucsd.edu http://hamradio.ucsd.edu/mailman/listinfo/44net