-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Good morning,
I saw some odd routing during my tests. So I analyzed the routes added by RIP44d. I modified the code to log the command string to add routes, my suspicions where confirmed: rip44d v1.2 adds every route with a prefix length of /32:
(examples)
Mar 29 00:45:03 debian rip44d[19323]: LANG=C /sbin/ip route add 44.161.0.0/32 via 141.75.245.225 dev tunl0 window 840 onlink table 44 Mar 29 00:45:03 debian rip44d[19323]: LANG=C /sbin/ip route add 44.129.0.0/32 via 118.22.1.194 dev tunl0 window 840 onlink table 44 Mar 29 00:45:03 debian rip44d[19323]: LANG=C /sbin/ip route add 44.147.0.0/32 via 121.99.232.227 dev tunl0 window 840 onlink table 44 Mar 29 00:45:03 debian rip44d[19323]: LANG=C /sbin/ip route add 44.183.0.0/32 via 130.208.168.63 dev tunl0 window 840 onlink table 44 Mar 29 00:45:03 debian rip44d[19323]: LANG=C /sbin/ip route add 44.94.0.0/32 via 141.224.128.8 dev tunl0 window 840 onlink table 44
All these routes should be /16
I'm trying to figure where the issue comes from, but I'm not a perl addict, so any help is welcome. I have already confirmed that the RIP message contains the correct netmask:
IP Address: 44.161.0.0, Metric: 1 Address Family: IP (2) Route Tag: 4 IP Address: 44.161.0.0 (44.161.0.0) Netmask: 255.255.0.0 (255.255.0.0) Next Hop: 141.75.245.225 (141.75.245.225) Metric: 1
73 de Marc - -- http://lx1duc.mcs.tel
Hi,
I've bumped the rip44d version number to 1.3:
https://raw.github.com/hessu/rip44d/master/rip44d
Here's the changelog for 1.2 and 1.3:
v1.2 - 2012-01-01 Ronald Jochems, PD1ACF and Heikki Hannikainen, OH7LZB * Added syslog functionality, using module: http://perldoc.perl.org/Sys/Syslog.html * Fixed to use CIDR format when calling /sbin/ip, to support older distributions
v1.3 - 2013-04-11 Heikki Hannikainen, OH7LZB * write pid file and lock it to prevent running multiple copies * fix a bug in interim version after 1.2: added routes with wrong prefix length
In the future I'll make development commits in a development branch and keep the master branch as a "stable release" version, so the above URL should always contain a rather working and tested version.
- Hessu
Hi OMs,
I have a modified version of the rip44 daemon capable to send multicast/unicast the rip packages on another interface so they can be used on an external router for 44net routing. Tested on a mikrotik router and works fine for more than 3 months now. Would it be useful to put it in the officicail daemon (2 command line options, if not used there is no functional change).
e.g.
rip44d (...) -f eth0 This will send RIP packets to 224.0.0.9 on if eth0
rip44d (...) -f eth0 -e 192.168.1.1 This will send the received RIP packets to address 192.168.1.1 via interface eth0
If usefull, I am glad to supply the code...
Marius.
-----Original Message----- From: 44net-bounces+marius=yo2loj.ro@hamradio.ucsd.edu [mailto:44net-bounces+marius=yo2loj.ro@hamradio.ucsd.edu] On Behalf Of Heikki Hannikainen Sent: Friday, April 12, 2013 00:52 To: AMPRNet working group Subject: [44net] rip44d version 1.3
...
In the future I'll make development commits in a development branch and keep the master branch as a "stable release" version, so the above URL should always contain a rather working and tested version.
- Hessu
_________________________________________ 44Net mailing list 44Net@hamradio.ucsd.edu http://hamradio.ucsd.edu/mailman/listinfo/44net http://www.ampr.org/donate.html
-
Heikki Hannikainen -
Marc, LX1DUC -
Marius Petrescu