[44net] Testing

All, I'll drop my line of discussion about the AMMPRNet rules requiring BGP announced subnets to provide connectivity; this isn't a mater of law, hence the entire community's here putting our heads together on how to accommodate Bart's request without breaking the consistency of the rest of AMPRNet, or some stations simply not having connectivity to him. Per Bart's recommendation, I evaluated simply removing or somehow editing Line 47 or 48 in my startampr http://44.60.44.13/startampr_v1.1 script, it will not work without complex configuration beyond a plug and play script (and I had to reference notes when developing to understand why) . If I add a line for his subnet, the issue is solved: + ip rule add to 44.24.221.1/32 table main priority 43 ***I added the following line, but rip44 deletes it when it receives the first announcement*** + ip route add 44.24.240.0/20 via 44.24.221.1 dev tunl0 onlink table 44 I've found many other issues with this configuration, but I won't list them as it will still result in a working connection to Bart. Lastly, the issues are not solved that even if he's permitted to add the route, the issue is not fixed with other 44GWs Feel free to test: http://44.60.44.10/tools *** Pinging from my tool to 44.24.221.1 does not work, as it requires masquerade to be setup, the first hop appears to be dropping the packet (as it should). - Lynwood KB3VWG