I'm confused about the nuances as well. And, I must say, the distinctions made below may be clear to some, but not to me. I know Hessu was trying to be brief, but in the brevity, I see no difference.
It would be VERY helpful if someone would compare and contrast the options. Why would I use A vs. B vs. C? Are there any advantages of this one vs. that one? ... etc. I'm not looking to start a "mine is better than yours war". But as a non-programmer, non-linux-expert, who hasn't ever written any Perl, and hasn't written any C in 30+ years, I surely have no idea which one to use and why/when. So I (and probably others) could use help in understanding more completely when/why A vs. B vs. C.
Thanks much,
Michael N6MEF
-----Original Message----- From: 44net-bounces+n6mef=mefox.org@hamradio.ucsd.edu [mailto:44net-bounces+n6mef=mefox.org@hamradio.ucsd.edu] On Behalf Of Heikki Hannikainen Sent: Tuesday, August 13, 2013 9:32 AM To: AMPRNet working group Subject: Re: [44net] rip44d update
(Please trim inclusions from previous messages) _______________________________________________ On Tue, Aug 13, 2013 at 5:49 PM, lleachii@aol.com wrote:
Is this update for the Perl or C based software?
We may want to consider a different name for each type; since they had the same name, version numbers, etc, it is somewhat confusing.
They have different names, actually:
rip44d is my Perl implementation.
ampr-ripd is the C implementation, pretty much like rip44d in other respects, both use Linux kernel IPIP tunneling and just manage the routing table.
amprd is an encapsulation daemon with RIP, a bit like the old ipip daemon (IPIP encapsulation in user space) but with RIP built in.
- Hessu