As long as the file as being handled manually, then it's under control of the one doing so..

On Mon, Aug 5, 2013 at 7:46 AM, Demetre SV1UY demetre.sv1uy@gmail.comwrote:

(Please trim inclusions from previous messages) _______________________________________________ Hi Don,

Thanks for reply. Should this also happen even if I have added:

ip route add blackhole 44.154/24

as the wiki says here: http://wiki.ampr.org/index.php/Rip44d

73 de SV1UY

On Mon, Aug 5, 2013 at 1:54 PM, Don Moore ve3zda@gmail.com wrote:

...

(Please trim inclusions from previous messages) _______________________________________________ yep

-- 73 de SV1UY Demetre Ch. Valaris IP Coordinator for AMPRnet in Greece e-mail: demetre.sv1uy@gmail.com Radio e-mail: sv1uy@winlink.org (to use my radio e-mail put //WL2K in the beginning of the subject line) http://www.qsl.net/sv1uy _________________________________________ 44Net mailing list 44Net@hamradio.ucsd.edu http://hamradio.ucsd.edu/mailman/listinfo/44net http://www.ampr.org/donate.html

On 13-08-05 12:03 PM, Marius Petrescu wrote:

(Please trim inclusions from previous messages) _______________________________________________ Just add the option -a <your_public_ip> to the rip44d command line. If you run rip44d on the gateway it autodetects its gateway address. Behind a DNAT it can not, so you must add it manually. And there is no need to open port 520 on the router. The RIP packets are IPIP encapsulated so only DNAT of proto 4 to your ampr gateway is needed.

Marius, YO2LOJ

---

44Net mailing list 44Net@hamradio.ucsd.edu http://hamradio.ucsd.edu/mailman/listinfo/44net http://www.ampr.org/donate.html

a gotcha for me was that you have to add the -a (ip) option at the very end, if inserted in the middle, it was ignored somehow with mine...might be solved now tho....sure made me scratch my head figuring that one out, lol!

On 13-08-05 01:39 PM, Marc, LX1DUC wrote:

(Please trim inclusions from previous messages) _______________________________________________

...

a gotcha for me was that you have to add the -a (ip) option at the very end, if inserted in the middle, it was ignored somehow with mine...might be solved now tho....sure made me scratch my head figuring that one out, lol!

Which version of RIP44d are you using? I'm using 1.3 and I have -a as the first option, see:

http://marc.storck.lu/blog/2013/08/howto-setup-an-amprnet-gateway-on-linux/

73 de Marc _________________________________________ 44Net mailing list 44Net@hamradio.ucsd.edu http://hamradio.ucsd.edu/mailman/listinfo/44net http://www.ampr.org/donate.html

yes, I believe it happened back on ver 1.1 or so, and have left it that way since...

Yes, it will happen until the IP address provided via the -a option matches the IP received via RIP44d as the destination for 44.154.0.0/24.

Also you MUST only add a blackhole route if you have more specific routes installed in your routing table, otherwise all your traffic to 44.154.0.0/24 will just be blackholed and will not reach the destination.

73 de Marc, LX1DUC

Quoting Demetre SV1UY demetre.sv1uy@gmail.com:

Thanks for reply. Should this also happen even if I have added:

ip route add blackhole 44.154/24

as the wiki says here: http://wiki.ampr.org/index.php/Rip44d