Hello everyone,
I released a new version of ampr-ripd (2.1) with fixes and additions.
Changelog: - Fixed a segfault when using the -F option - Added the possibility to use interface names for the -g option - Interface used for raw RIP forwarding restarts on interface error
Download:
http://www.yo2loj.ro/hamprojects/ampr-ripd-2.1.tgz
http://yo2tm.ampr.org/hamprojects/ampr-ripd-2.1.tgz
Have fun,
Marius, YO2LOJ
@Gustavo, Lynwood
Please check the the features as you are one of those that need them ;-)
Marius,
- I noticed all the tunl0 routes are now added to interface ifb0, even when -i argument is used - I don't appear to be receiving routes - Also, I later emailed and agreed that WAN routes MUST specify a gateway IP address; it doesn't appear to work by interface only (in my current configuration), I'll be using autodetect. This could work in a downstream device
73,
- Lynwood KB3VWG
Please check the the features as you are one of those that need them ;-)
Marius,
- I noticed all the tunl0 routes are now added to interface ifb0, even
when -i argument is used
- I don't appear to be receiving routes
- Also, I later emailed and agreed that WAN routes MUST specify a
gateway IP address; it doesn't appear to work by interface only (in my current configuration), I'll be using autodetect. This could work in a downstream device
73,
- Lynwood
KB3VWG
Please check the the features as you are one of those that need them ;-)
Something odd or broken in -F switch with respect to the test version. High kilobytes traffic registered by plotted diagrams:
see the new entry diagram (last two/three hours at right hand): http://44.134.32.240/pastday.png
see the overall server traffic at: http://44.134.32.240/www/index.html
you may get detailed data and statistics by clicking on pictures.
Now come back to 2.1 test version.
Other -E and -g switches don't get routes forwarding towards the target IP or to the target interface :(
@Lynwood
The interface name option is valid ONLY for point to point interfaces, like PPTP or PPoE, where it should support a dynamic IP, and does not support interfaces which allow more than one peer IPs like ethernet. Even if it will create the routes for a ethernet interface, it will not work since it expects that specific IP for which it is created to be physically connected to that interface (which is not the case).
@Gustavo
That traffic reduction/increase is not a relevant indicator since except re-sending the RIP packages on the defined interface there is nothing the daemon does. Except adding the interface handling, nothing is changed from the test version I sent to you.
Marius, YO2LOJ
Marius,
OK, we concur.
Using 2.1
- my tunnel routes still assign to ifb0, regardless of the -i option - I'm not receiving routes
- KB3VWG
Thanks Marius as the -g <interface name> option is just what I need!
Bob VE3TOK
On 2017-05-28 11:27 AM, Marius Petrescu wrote:
(Please trim inclusions from previous messages) _______________________________________________ Hello everyone,
I released a new version of ampr-ripd (2.1) with fixes and additions.
Changelog: - Fixed a segfault when using the -F option - Added the possibility to use interface names for the -g option - Interface used for raw RIP forwarding restarts on interface error
Download:
http://www.yo2loj.ro/hamprojects/ampr-ripd-2.1.tgz
http://yo2tm.ampr.org/hamprojects/ampr-ripd-2.1.tgz
Have fun,
Marius, YO2LOJ
Ok. I managed to reproduce the issue with the interfaces.
Please do not use 2.1. I wil fix it and release a 2.1.1 ASAP
Marius, YO2LOJ
On 28.05.2017 18:27, Marius Petrescu wrote:
(Please trim inclusions from previous messages) _______________________________________________ Hello everyone,
I released a new version of ampr-ripd (2.1) with fixes and additions.
Changelog: - Fixed a segfault when using the -F option - Added the possibility to use interface names for the -g option - Interface used for raw RIP forwarding restarts on interface error
Download:
http://www.yo2loj.ro/hamprojects/ampr-ripd-2.1.tgz
http://yo2tm.ampr.org/hamprojects/ampr-ripd-2.1.tgz
Have fun,
Marius, YO2LOJ