Re: [44net] 44net cool toys

1. Inside each archive, there is a "manual.txt" which describe all parameters and their defaults and the installation procedure. Also there is a script for finding the RIP password and a example startup script. 2. The route exire time is 10 minutes (parameter EXPTIME at the beginning of the source code file), meaning that if after 2 successful RIP receive rounds the route is not announced, it will be dropped. There is no 2 step process. If a route is received with metric 15, it is dropped immediately (not used in the RIP broadcasts but implemented). 3. If updates are not received, no change in existing routes take place unless RIPv2 reception is resumed. 4. No status commands or logs are available, only the latest current route configuration is stored in "/var/lib/ampr-ripd/encap.txt" (it can also be changed in the source file - just a define) For debuging, there is a -d (debug) and -v (verbose) available. For deeper debugging there are 2 additional compile options in the makefile, allowing deeper debug including netlink tracing. (thse need a recompile). 73s de Marius -----Original Message----- From: 44net-bounces+marius=yo2loj.ro(a)hamradio.ucsd.edu [mailto:44net-bounces+marius=yo2loj.ro@hamradio.ucsd.edu] On Behalf Of Michael E Fox - N6MEF Sent: Thursday, March 20, 2014 16:57 To: 'AMPRNet working group' Subject: Re: [44net] 44net cool toys (Please trim inclusions from previous messages) _______________________________________________ Marius, Thanks for all your hard work. I went to your website: http://www.yo2loj.ro/hamprojects/ I didn't find any documentation on how to use it. Specifically, I'd like to understand: 1) After compiling, then what? In other words, what is the recommended way to run it? 2) What timeout or hold-down timers exists and how are they configured (if possible). For example, if a route disappears from the updates sent by amprgw, how long before it is removed from the table? And is that configurable? Also, is it a two-step process (i.e. first marked as unreachable and then later removed)? 3) If amprgw updates cease completely (i.e. amprgw is down or hung), is the behavior different? Or do all routes eventually time out at the above interval? 3) Is there anything else configurable? 4) Are there any status commands? Does it generate a log? Where? What are useful tips on how to manage it and how to troubleshoot problems? Thanks, Michael N6MEF x86, 7. up _________________________________________ 44Net mailing list 44Net(a)hamradio.ucsd.edu http://hamradio.ucsd.edu/mailman/listinfo/44net