On Thu, Apr 17, 2014 at 11:08 AM, lleachii@aol.com wrote:
most people try to do. After I inquired more about Bart's proposed solution and offered to re-write my entire station router script, he stated he did not want to contribute any more time to the problem. Now he reappears lobbying for a board position in lieu of working to fix his perceived "issues" with ARDC - citing old technology and old ideas; all one can be
I believe Bart got frustrated with the lack of change-management and specifications in AMPR. How your script is written depends on these things.
It seems that to be allowed/compliant in AMPR, it just has to work with the existing system. But what is the existing system? There are a lot of existing systems and most of them are not documented. For example, we learned via the mailing list that many AMPR gateways have a static route to 44/8. This isn't documented in the encap file, it's just added by their scripts. Where is the specification for this? Little details like this are important when trying to figure out how to write script to route to other AMPR systems. Until we know all these details, it's not worth writing more software.
Where is the official specification? The wiki links to a couple scripts on third party sites. These are current implementations, not specs, and they aren't identical. Which one do we trust? What is AMPR/ARDC's policy for creating, accepting, and publishing specifications?
I'm curious if you have done a survey: what percentage of AMPR allocations can you route to from your gateway? I've been meaning to write some software to test from ours. I expect the results to be disappointing.
Tom KD7LXL