I think the other thing to keep in mind is that the more that is shown to be routable on the network the more chances we can keep the IP poachers out and stave off any questions from ARIN on why the allocation exists and what it is being used for that a 10/8 space would not be substituent.
Lin
On Tue, Jul 16, 2013 at 4:08 PM, Brian Kantor Brian@ucsd.edu wrote:
(Please trim inclusions from previous messages) _______________________________________________ On Tue, Jul 16, 2013 at 10:59:10PM +0300, Heikki Hannikainen wrote:
Tested, does not work:
Seems to be a routing loop somewhere over there, 137.110.222.1 probably routes all of 44/8 to amprgw (maybe it has a static route for 44/8 and does not have the full BGP routing table with more specific routes announced elsewhere) and amprgw then gives packet destined to 44.74.128.25 back to 137.110.222.1 since it's not in the encap routing table.
That is precisely what's happening. 137.110.222.1 is an internal router with no BGP so it'll never learn about those directly-connected subnets. - Brian _________________________________________ 44Net mailing list 44Net@hamradio.ucsd.edu http://hamradio.ucsd.edu/mailman/listinfo/44net http://www.ampr.org/donate.html