Hello OMs,
Another addition and a new version.
Added support for setting a specific route metric for the created routes using the -m option (regular routes until now had metric 0). This allows routes from other sources, e.g. BGP or OSPF to take precedence over those created by ampr-ripd.
For those not needing "fancy" routing, there's no need to upgrade.
Download from http://www.yo2loj.ro/hamprojects/ or http://yo2tm.ampr.org/hamprojects/ (as usual), or get it via github: https://github.com/yo2loj/ampr-ripd/
Direct links: http://www.yo2loj.ro/hamprojects/ampr-ripd-1.8.tgz http://yo2tm.ampr.org/hamprojects/ampr-ripd-1.8.tgz
Have fun, Marius, YO2LOJ
This all looks very encouraging.
I just wish it worked with regular RIP at the same time. We have a need for running regular RIP to communicate local routes.
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 Marius Petrescu Sent: Tuesday, February 11, 2014 9:00 AM To: 'AMPRNet working group' Subject: [44net] ampr-ripd 1.8 released
(Please trim inclusions from previous messages) _______________________________________________ Hello OMs,
Another addition and a new version.
Added support for setting a specific route metric for the created routes using the -m option (regular routes until now had metric 0). This allows routes from other sources, e.g. BGP or OSPF to take precedence over those created by ampr-ripd.
For those not needing "fancy" routing, there's no need to upgrade.
Download from http://www.yo2loj.ro/hamprojects/ or http://yo2tm.ampr.org/hamprojects/ (as usual), or get it via github: https://github.com/yo2loj/ampr-ripd/
Direct links: http://www.yo2loj.ro/hamprojects/ampr-ripd-1.8.tgz http://yo2tm.ampr.org/hamprojects/ampr-ripd-1.8.tgz
Have fun, Marius, YO2LOJ
Hi Michael,
I really don't see why you could not run e.g. Quagga at the same time on other interfaces. Receiving RIP messages on the ampr interface has nothing to do with other routing daemons on other interfaces. You just have to redistribute those routes, or, even better, distribute 44.0.0.0/8 with a high metric and let the rest do their job.
e.g. for OSPF:
router ospf network 192.168.74.0/24 area 0 <- my local network network 44.182.20.0/23 area 0.0.0.44 <- my ampr subnets area 0.0.0.44 range 44.0.0.0/8 redistribute kernel redistribute connected !
Marius, YO2LOJ
-----Original Message----- From: 44net-bounces+marius=yo2loj.ro@hamradio.ucsd.edu [mailto:44net-bounces+marius=yo2loj.ro@hamradio.ucsd.edu] On Behalf Of Michael E Fox - N6MEF Sent: Wednesday, February 12, 2014 10:17 To: 'AMPRNet working group' Subject: Re: [44net] ampr-ripd 1.8 released
(Please trim inclusions from previous messages) _______________________________________________ This all looks very encouraging.
I just wish it worked with regular RIP at the same time. We have a need for running regular RIP to communicate local routes.
Michael N6MEF
-
Marius Petrescu -
Michael E Fox - N6MEF