Bart,
- NO router in AMPR by default speaks BGP, they speak some form of what can be termed RIP44 - ALL outbound traffic leaving or destined to AMPR GWs via the Public Internet are sent via IPENCAP - every valid 44/8 address has a corresponding rip44 announcement - every 44IP announcement has a corresponding non-44 IP DST to send that IPENCAP traffic to - IF RUNNING BGP, YOU MUST STILL SPEAK IPENCAP and RIP44 with a non44 IP, BGP only speaks to the Public Internet - altering one of the conditions above would cause issues somewhere within AMPR
***e.g. If I send your 44.24.240.0/20 traffic directly to 44.24.221.1 the traffic SRC address is a non-44 IP; and therefore would not return to my GW ~or~ has a SRC of 44.0.0.0 and is dropped by the first hop***
I think you have totally misunderstood, adding the entry will not 'magically' allow every other AMPR gateway to send traffic to 44.24.240.0/20. There is no way within the AMPR routing announcements to specify use of the non AMPR interface - unless a static route is manually entered on every station wishing to contact 44.24.240.0/20. You may be multihomed, but most AMPR GWs are not.
AMPRGW is NOT "broken."
I would probably leave the UCSD communication broken instead, until UCSD fixes the routing issue. We'd still enjoy the benefits of redundant tunnel termination for every other AMPRnet. Can you make the database change to configure 44.24.221.1 as the gateway for 44.24.240.0/20?