Re: [44net] Setting up a tunnel to my BGP's 44net range

Tony With your other questions please contact me off list and I will be send you my config In short nothing changed greatly in our apps. I run tnos, aprs. Mmdvm etc on 44net as well I can duplicate the network via eoip to our colo Sam Vk4aa(a)vk4aa.com.au Sent from MailDroid -----Original Message----- From: Tony Langdon <vk3jed(a)vkradio.com> To: 44net(a)mailman.ampr.org Sent: Wed, 09 May 2018 1:22 pm Subject: [44net] Setting up a tunnel to my BGP's 44net range Now that my BGP announced 44.x range is up and running, I'd like to be able to make it transparently accessible for tunneled networks. I just need to double check a few things. First, I know I'd need to run ampr-ripd on the box. I also have non-44 net addresses to use as the ipip encap endpoint. What else do I need to do? Do I need to advertise the subnet as "tunneled" in addition to direct in the portal? Anything else? Reason for this is I'm likely to be running services other than Echolink proxies, which may require peer-peer connectivity. Currently, 44.x tunneled addresses connecting to the system would go via their local router, which most likely involves NAT. And on a similar note, is there a way to exclude other directly connected subnets capable of IPIP tunneling from using a tunnel? (since that's obviously not required!) -- 73 de Tony VK3JED/VK3IRL http://vkradio.com _________________________________________ 44Net mailing list 44Net(a)mailman.ampr.org https://mailman.ampr.org/mailman/listinfo/44net