Re: [44net] ampr-ripd

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. -- Tom - SP2L ------------------------------------ It is nice to be important. But it is more important to be nice!