23 May
2014
23 May
'14
11:50 a.m.
It is not trouble, it is just a non functional route in the broadcast which
prevents connections to your subnet.
So the simplest solutions would be either to announce it via RIP as a tunnel
via public IP (44.140.0.0/16 via 192.16.126.18 - in this case ampr users
will retain their 44 src address ) or not announce it at all in RIP/encap
(and in this case everyone will appear with their public address and some
will have issues because of 44.x.x.x being usually routed to UCSD by most of
the setups).
It will make it work in either case.
Just the current setup is nonfunctional from a router's point of view
without manual tuning.