Tnx Lynwood for the update. Maybe adding the amprd daemon to the daemon list would also be useful. That one is the most complete ampr solution yet. It is user space based, but on modern systems, the difference in performance is minimal. It uses internal ripv2 handling, supports multiple subnets on multiple concurrent interfaces and creates virtual ethernet interfaces which can also be bridged like the regular ones. It sets the minimal needed number of routes, on regular gateways a 44.0.0.0/8 route to the virtual interface together with the BGP announced 44 hosts being all that is needed. Configuration is done by a simple (up to complex) configuration file, without the fuss of an impossible long command line. It is worth a try :-) On 02.10.2018 22:48, lleachii--- via 44Net wrote: > Aaron, > As Brian said, I have the following IPs online: > 44.60.44.1 - ping, NTP44.60.44.3 - ping, DNS44.60.44.10 - ping, HTTP44.60.44.254 (only accessible on AMPRNet) - ping > I allow ping from your Public IP endpoint address and your 44 subnet(s) in the Portal. > If you're on AMPRNet, a folder containing the ITU Radio Regulations and compiled ampr-ripd versions will be visible on the web server at: http://44.60.44.10/amprnet_docs/ > -------------------------- > > Miguel, > > Also, I've added Marius' information to the Wiki: http://wiki.ampr.org/wiki/RIP > -------------------------- > Marius, > FYI, I am able to ping 44.0.0.1: > root@OpenWrt:~# ip route get 44.0.0.1 from 44.60.44.144.0.0.1 from 44.60.44.1 via 169.228.34.84 dev tunl0 table 44 uid 0     cache expires 582sec mtu 1480 window 840 > > root@OpenWrt:~# ping 44.0.0.1 -I 44.60.44.1 -c 3PING 44.0.0.1 (44.0.0.1) from 44.60.44.1: 56 data bytes64 bytes from 44.0.0.1: seq=0 ttl=62 time=67.768 ms64 bytes from 44.0.0.1: seq=1 ttl=62 time=67.814 ms64 bytes from 44.0.0.1: seq=2 ttl=62 time=67.492 ms > --- 44.0.0.1 ping statistics ---3 packets transmitted, 3 packets received, 0% packet lossround-trip min/avg/max = 67.492/67.691/67.814 ms > > 73, > > - Lynwood > KB3VWG >

Yes. Marius last explained to me, that as long as I masquerade my subnet on my border, that I can reach BGPed subnets, I can also send traffic to them thru their downstream tunnel: I see these in my route table:> 44.24.172.41 via 71.178.210.1 dev eth0.2 proto 44 44.94.17.129 via 71.178.210.1 dev eth0.2 proto 44 44.130.104.1 via 71.178.210.1 dev eth0.2 proto 44 44.130.105.1 via 71.178.210.1 dev eth0.2 proto 44 44.130.106.1 via 71.178.210.1 dev eth0.2 proto 44 44.130.107.1 via 71.178.210.1 dev eth0.2 proto 44 44.131.14.253 via 71.178.210.1 dev eth0.2 proto 44 44.136.150.2 via 71.178.210.1 dev eth0.2 proto 44 44.151.31.6 via 71.178.210.1 dev eth0.2 proto 44 44.151.31.6 via 71.178.210.1 dev eth0.2 proto 44 44.24.172.40/29 via 44.24.172.41 dev tunl0 proto 44 onlink window 840 44.94.17.128/27 via 44.94.17.129 dev tunl0 proto 44 onlink window 840 44.130.104.0/24 via 44.130.104.1 dev tunl0 proto 44 onlink window 840 44.130.105.0/24 via 44.130.105.1 dev tunl0 proto 44 onlink window 840 44.130.106.0/24 via 44.130.106.1 dev tunl0 proto 44 onlink window 840 44.130.107.0/24 via 44.130.107.1 dev tunl0 proto 44 onlink window 840 44.130.234.0/24 via 44.130.104.1 dev tunl0 proto 44 onlink window 840 44.130.235.0/24 via 44.130.105.1 dev tunl0 proto 44 onlink window 840 44.130.236.0/24 via 44.130.106.1 dev tunl0 proto 44 onlink window 840 44.130.237.0/24 via 44.130.107.1 dev tunl0 proto 44 onlink window 840 44.131.211.136/30 via 44.131.14.253 dev tunl0 proto 44 onlink window 840 44.136.150.0/23 via 44.136.150.2 dev tunl0 proto 44 onlink window 840 44.151.31.6 via 44.151.31.6 dev tunl0 proto 44 onlink window 840 44.153.32.97 via 44.148.177.14 dev tunl0 proto 44 onlink window 840 44.153.35.0/24 via 44.148.177.14 dev tunl0 proto 44 onlink window 840 Also, I have a route for 44.0.0.1:> 44.0.0.1 via 169.228.34.84 dev tunl0 proto 44 onlink window 840 I also recall ping to 44.0.0.1 working since circa the new AMPRGW upgrade. 73, Lynwood KB3VWG