Re: [44net] Running for ARDC director position

Tom, I agree that the lack of change management can be frustrating; but again, that's something we as a community would have to implement - changing leadership doesn't directly solve that. Regarding documentation and specifications, the WIKI was developed as a method to assemble documentation (see archives). About routing: 44/8 is a flat network, so I'm not certain how a static route to 44/8 would need to be documented (as AMPRGW would be that route on the Public Internet). In fact, my 44GW should be able to send to other gateways if one used: 44.0.0.0/8 via <my GW IP> dev tunl0 onlink I used that method (during testing) for a while until I developed the script. The packets should route onward to you and the return trip would take your specified route. That is a basic understanding of routing. To answer your question about a survey, the last I manually checked (when I tested connectivity with the Linux script), I could route reach 100% of those AMPR gateways being tested and others in the route table. I am able to perform a survey of the entire 44/8, but until I know all hosts that should be online, those only available locally, and those reachable only on AMPR, it would be difficult to compile the data network-wide with any level of accuracy. -KB3VWG