Last year I followed this instructions
http://www.qsl.net/kb9mwr/wapr/tcpip/ampr-ripd.html
and was able to get a Amprnet Gateway working on a Raspberry Pi 2 with a second USB Ethernet and VPN working OK.
Few months later, I have problem connecting with VPN. i found out later, I have 2 IPs one static and one dynamic on the RPI. This was due to the new dhcpcd.conf implementation. No longer you declare the static IP in interfaces and some say to add it at the end of dhcpcd.conf. I disable dhcpcd at boot and now 1 static IP and no trouble with VPN.
Now, I have problem not receiving the ampr-ripd encap route broadcast.
ip route show table 44 only shows:
default via 169.228.66.251 dev tunl0 onlink 44.163.22.0/24 dev eth1 scope link 44.163.22.128/25 dev tun0 scope link
tcpdump -i etho proto 4 monitor for a long time a no broadcast
I use this tool to ping 44.163.22.1 http://yo2tm.ampr.org/nettools.php
100% packet lost
But with tcpdump -i eth0 proto 4 it shows the ping arriving but my gateway with no route then no answer:
tcpdump: verbose output suppressed, use -v or -vv for full protocol decode listening on eth0, link-type EN10MB (Ethernet), capture size 65535 bytes 00:33:08.740142 IP mail.yo2loj.ro > 192.168.1.112: IP yo2tm.ampr.org > onx.hp2at.ampr.org: ICMP echo request, id 44708, seq 1, length 64 (ipip-proto-4)
How can I diagnose why my ampr-ripd is not receiving the broadcast? Any tools?
Jose / HP2AT
Hello Jose.
As Rob PE1CHL wisely pointed just while ago...
Run command: ampr-ripd -d -r -i <44-tunnel-interface>
You should see something similar:
root@linux:/# ampr-ripd -d -r -i tunl0 Waiting for RIPv2 broadcasts... Simple password: dumbpassword ... Simple password: dumbpassword
Running above command from the command line on my server Debian-7.9 i686 machine WITHOUT "-r" also does not work!!! So, it seems that it is NOT only Pi specific...
Alternatively, you may set up manually single route to ANY working 44-net host to see whether you will be able to reach that gateway.
Best regards. Tom - SP2L