Hello,  I am seeing the same issue.  I am running ampr-ripd 2.3 compiled from http://www.yo2loj.ro/hamprojects/%C2%A0%C2%A0 it says Calling home over and over.. when i run tcpdump i can see the packets coming in past the firewall. 23:55:01.340394 IP 44.0.0.1.520 > 224.0.0.9.520: RIPv2, Response, length: 50423:55:01.396155 IP 44.0.0.1.520 > 224.0.0.9.520: RIPv2, Response, length: 50423:55:01.451895 IP 44.0.0.1.520 > 224.0.0.9.520: RIPv2, Response, length: 50423:55:01.507863 IP 44.0.0.1.520 > 224.0.0.9.520: RIPv2, Response, length: 50423:55:01.563557 IP 44.0.0.1.520 > 224.0.0.9.520: RIPv2, Response, length: 50423:55:01.619404 IP 44.0.0.1.520 > 224.0.0.9.520: RIPv2, Response, length: 284 Jon Lundy K7XUU

On Tuesday, November 6, 2018, 6:20:12 PM MST, Jean Létourneau ve2pkt@gmail.com wrote:

n Tue, Nov 6, 2018 at 4:36 PM Peter Mallett peter.zl2bau@gmail.com wrote:

Hello Peter,

Hi Jean,

Just a thought, have you opened port 520 UDP to your RasPi ?

Just did

Ah, where are you getting the ampr-ripd from ?

169.228.34.84

I do not use DMZ here anymore as I open specific ports to the URONode machine and use iptables to keep out all the nasties.

well I have all other port's working but still same problem. Thanks for you help I will keep looking.

Regards ..... Peter  ZL2BAU 73 de Jean

Hello Jean.

If you have ampr-ripd installed, very simple way to check IF YOU'RE RECEIVING rip44v2 broadcast is shown in the file:    /path/to/ampr-ripd-2.3/examples/find_pass.sh

#!/bin/sh # # Running ampr-ripd without any options except debug and the interface name # allows you to find your RIPv2 password if it ever changes from the default. # You need to adapt the interface name to your setup. #

/path/to/ampr-ripd -d -v -i ampr0

Replace  ampr0  by whatever your  AMPRNet tunnel interface is. In your case looks like it is  tunl0

Not later than after five minutes you should see something similar:

root@linux:/# ampr-ripd -d -v -i tunl0

Using metric 0 for routes. Using TCP window 840 for routes. Using gateway 192.168.0.1 for direct 44net endpoints via interface eth0. Waiting for RIPv2 broadcasts... Simple password: <obfuscated> Simple password: <obfuscated> Simple password: <obfuscated> Simple password: <obfuscated> Simple password: <obfuscated> Simple password: <obfuscated> Simple password: <obfuscated> Simple password: <obfuscated> Simple password: <obfuscated> Simple password: <obfuscated> Simple password: <obfuscated> Simple password: <obfuscated> Simple password: <obfuscated> Simple password: <obfuscated> Simple password: <obfuscated> Simple password: <obfuscated> Simple password: <obfuscated> Simple password: <obfuscated> Simple password: <obfuscated> Simple password: <obfuscated> Simple password: <obfuscated> Simple password: <obfuscated> Simple password: <obfuscated> Simple password: <obfuscated> Simple password: <obfuscated> Simple password: <obfuscated> Simple password: <obfuscated> Simple password: <obfuscated> Simple password: <obfuscated>

root@linux:/#

If not, port 520 on your device is closed. For this test to work, no need to have routing already set up, as this will be your next step...

Best regards.