I use tons where i still usr encapsulation.
Sent from MailDroid
-----Original Message----- From: Tony Langdon vk3jed@vkradio.com To: 44net@mailman.ampr.org Sent: Wed, 09 May 2018 3:20 pm Subject: Re: [44net] Setting up a tunnel to my BGP's 44net range
On 09/05/18 15:03, vk4aa@vk4aa.com.au wrote:
Tony
I advertise my /23 via 2 providers. We then use our internal routers to break them down into subnets i require.
That doesn't answer my question at all, seems to answer an entirely different question, which I'm not sure is relevant.
Sam Vk4aa
Sent from MailDroid
-----Original Message----- From: Tony Langdon vk3jed@vkradio.com To: 44net@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!)