Sorry for the late reply, I just saw your email.

Yes, our edge router runs RouterOS and holds all the IPIP tunnels open for AMPRnet routing.  We (and by "we", I mean Tom/KD7LXL) developed software for us to keep the edge routers refreshed with tunnel updates.  It's available here:

https://github.com/kd7lxl/hamwan_scripts/tree/master/amprupdate

Here's a snippet of what our config looks like on the router itself:

/interface ipip
add disabled=no dscp=0 local-address=198.178.136.80 mtu=1480 name=ampr-118.22.1.194 remote-address=118.22.1.194
add disabled=no dscp=0 local-address=198.178.136.80 mtu=1480 name=ampr-118.82.200.153 remote-address=118.82.200.153
add disabled=no dscp=0 local-address=198.178.136.80 mtu=1480 name=ampr-12.195.50.128 remote-address=12.195.50.128
add disabled=no dscp=0 local-address=198.178.136.80 mtu=1480 name=ampr-121.99.232.227 remote-address=121.99.232.227
...

/ip route
add disabled=no distance=1 dst-address=44.2.1.32/29 gateway=ampr-76.14.161.185 scope=30 target-scope=10
add disabled=no distance=1 dst-address=44.2.8.180/30 gateway=ampr-192.147.172.252 scope=30 target-scope=10
add disabled=no distance=1 dst-address=44.2.10.0/29 gateway=ampr-71.130.72.52 scope=30 target-scope=10
add disabled=no distance=1 dst-address=44.2.11.1/32 gateway=ampr-71.130.72.52 scope=30 target-scope=10
add disabled=no distance=1 dst-address=44.2.14.100/32 gateway=ampr-50.79.156.221 scope=30 target-scope=10
add disabled=no distance=1 dst-address=44.2.50.0/24 gateway=ampr-208.74.106.137 scope=30 target-scope=10
...

We haven't been able to test this since it's hard to know which IPs on the target subnets are actually alive and have corresponding tunnel entries for us.  There's a few hundred of these tunnels installed on our edge router which cover the whole of AMPRnet.  Anyone on HamWAN should have full routability to/from these networks.

--Bart


On 8/20/2013 7:33 AM, Rod Ekholm wrote: