Unfortunately 44-net lives in a quasi private-public world. Hosts on the 44-net IP-IP system can be reachable from the Internet via the gateway at UCSD. One needs to simply have an entry in the "ampr.org" DNS forward and reverse domains to be reachable from the Internet. But keep in mind, that in the U.S. at least, much of the traffic that flows across the Internet, if routed to RF on Amateur Frequencies would be in violation of FCC rules. Encryption (HTTPS and SSH for example) probably violates these rules. A lot of content on the Internet would probably violate these rules too. As the owner of a gateway (to RF) in the US it is likely YOU will be held responsible for the illegal traffic, even if you did not originate it. Other countries may have more (or less) restrictive rules. That's why many gateway operators want the option to not be reachable from the larger Internet. They just want to be able to access other AMPRNet networks and services around the globe via the tunnel system. Using RFC1918 space would not serve that purpose because it lacks the global coordination that AMPRNet has thanks to work of dedicated volunteers like Brian and Chris and the graciousness of UCSD to handle a /8 of traffic. IP-IP tunneling is a standard by the way (RFC 2003, RFC 6864), just like BGP. I admit that rip44d and ampr-ripd are non-standard, but they leverage a standard (RIP) to solve a unique problem. I still have issues with the idea that many ISP's will be happy to peer 44-net traffic on their nets for free. It may be possible to find a small or medium sized ISP in a urban area willing to volunteer equipment, labor, and bandwidth to do it, but here in semi-rural Iowa we have at most 2 ISP's (cable and DSL). Both are operated by large corporations (Mediacom and CenturyLink) who I know wouldn't have any inclination to peer with 44-net without some financial benefit. -Neil On Mon, Mar 31, 2014 at 3:15 PM, Bryan Fields <Bryan(a)bryanfields.net> wrote: -- Neil Johnson http://erudicon.com