Re: [44net] 44 Network behind BGPed 44 Address

Brian N1URO, I guess I'll present my thought processes as well. I found the problems to be: a.) solving the OSI Layer 1 issue: the limitation in RIP44; in that it only permits routing to one (1) interface; or b.) solving the OSI Layer 3 issue: that all 44/8 IPs are not necessarily on AMPRNet, some are on the ICANN Network; or c.) being satisfied with routing packets for any unknown subnet - unencapsulated via ICANN (with masquerade); or using static rules and routing I've found no dynamic routing solution that solves Problem B on AMPRGW or our 44net routers; except by solving Problem A. So long as the Main AMPRGW uses BGP first, a RIP44v2 could fix it; but present the issues that Marius described. Solutions to Problem C are all workarounds to Problems A and B. You suggested somehow incorporating interfaces into RIP44 announcements; that requires a rewrite of the RIP44 protocol, which permanently solves the problem at Layer 1. Perhaps it's time for RIP44v2 to add: - add other interface flags - provide CLI variables for those flags to specify eth interfaces, in addition to tunl0 - perhaps ability to save the RIP44 announcement to a file - only overwrite the persistent file when a new announcement is received, otherwise refer to the file The only problem, is that RIP44v2 would not be backwards compatible with RIP44; this requires an upgrade of all AMPRNet routers. --------------------- Marius, To your first question: I would have to reference the mail archive (I recall the user stating the 44 IP is valid; but under ICANN logic applied to AMPRNet, it's not); the solution all 44GWs would be to use a Public IP. To your second point, the BGPed subnet is NOT announced. The BGPed address is 44.24.221.1/32 An IP inside the network that's reachable: 44.24.240.1: @kb3vwg-001:~$ ping 44.24.240.1 -c 3 PING 44.24.240.1 (44.24.240.1) 56(84) bytes of data. 64 bytes from 44.24.240.1: icmp_seq=1 ttl=60 time=114 ms 64 bytes from 44.24.240.1: icmp_seq=2 ttl=60 time=116 ms 64 bytes from 44.24.240.1: icmp_seq=3 ttl=60 time=109 ms --- 44.24.240.1 ping statistics --- 3 packets transmitted, 3 received, 0% packet loss, time 2003ms rtt min/avg/max/mdev = 109.991/113.715/116.392/2.730 ms @kb3vwg-001:~$ traceroute 44.24.240.1 traceroute to 44.24.240.1 (44.24.240.1), 30 hops max, 60 byte packets 1 switch.seattle-er1.hamwan.net (44.24.241.97) 84.877 ms 84.962 ms 84.865 ms 2 ether1.queenanne.seattle.hamwan.net (44.24.241.99) 85.174 ms 85.365 ms 85.330 ms 3 wlan1.ptp1-westin.queenanne.hamwan.net (44.24.242.35) 89.324 ms 89.633 ms 89.618 ms 4 ether1.capitolpark.queenanne.hamwan.net (44.24.241.83) 90.055 ms 89.900 ms 89.859 ms 5 ether1.paine.capitolpark.hamwan.net (44.24.240.7) 118.569 ms 118.855 ms 119.233 ms 6 capitolpark-r1.hamwan.net (44.24.240.1) 120.432 ms 93.757 ms 96.728 ms