Ok, just this afternoon I'd shut down the amprd and set up ampr-ripd with this in
/etc/network/interfaces :
auto ampr0
iface ampr0 inet static
address 44.131.170.1
netmask 255.255.255.255
metric 100
pre-up ip tun add ampr0 mode ipip ttl 64 local 192.168.1.2 dev eth0
up ip route add default via 169.228.34.84 dev ampr0 onlink table default
up ip rule add from 44.131.170.1 table default
up /usr/local/sbin/ampr-ripd -s -i ampr0 -m 50 -a 192.168.1.2 -f eth0 -x "ip route
| grep 'proto 44' >/var/lib/ampr-ripd/routes" -L M1BKF@JO02pp
up ping -c1 -Iampr0 44.0.0.1 > /dev/null 2>&1
pre-down ip route del default via 169.228.34.84 dev ampr0 onlink table default
post-down killall ampr-ripd
post-down ip rule del from 44.131.170.1 table default
post-down ip tunnel del ampr0
post-down rmmod ipip
All seemed to be working:
ping -q -c3 -Iampr0 44.182.21.1 ; ping -q -c3 -Iampr0 44.92.21.35 ; ping -q -c3 -Iampr0
44.92.21.50
PING 44.182.21.1 (44.182.21.1) from 44.131.170.1 ampr0: 56(84) bytes of data.
--- 44.182.21.1 ping statistics ---
3 packets transmitted, 3 received, 0% packet loss, time 2002ms
rtt min/avg/max/mdev = 46.887/47.348/47.702/0.341 ms
PING 44.92.21.35 (44.92.21.35) from 44.131.170.1 ampr0: 56(84) bytes of data.
--- 44.92.21.35 ping statistics ---
3 packets transmitted, 3 received, 0% packet loss, time 2001ms
rtt min/avg/max/mdev = 119.530/119.693/119.977/0.201 ms
PING 44.92.21.50 (44.92.21.50) from 44.131.170.1 ampr0: 56(84) bytes of data.
--- 44.92.21.50 ping statistics ---
3 packets transmitted, 3 received, 0% packet loss, time 2003ms
rtt min/avg/max/mdev = 118.846/124.840/136.335/8.135 ms
And ip route | grep 'proto 44' | wc -l
749
And I can reach 44.131.170.1 from an AWS machine.
Any obvious problems there? I'll check the PKTerrors again, but how often does that
update?
I haven't yet set up filtering...
Thanks. Bill (M1BKF)