Re: [44net] TUNNEL vs DIRECT connection of subnets

Hi, I think this is not a problem and is a false issue. A network can be BGP announced AND may offer IPIP tunnel access. irelevant. The criteria for a network to be announced in RIP/encap are simple to define: 1. An IPIP endpoint is available on its gateway address with access from the public internet (confirmed by the TUNNEL flag set in the web interface and a defined gateway address) AND 2. its gateway address is NOT an ampr address from an already announced subnet with another IPIP gateway (no IPIP over IPIP allowed) AND 3. its gateway address is NOT in its own subnet (and there is no simple way to exclude the gateway address from the IPIP network routes at the moment). All other variants are possible and functional, BGP announced or not. The BGP announced networks can be, of course registered, but should not appear in the encap file, nor in the RIP data, unless it offers an IPIP endpoint on a public IP. This public IP can be any address, including BGP announced IPs, as long as criteria 2 and 3 are not violated. -----Original Message----- From: 44net-bounces+marius=yo2loj.ro(a)hamradio.ucsd.edu [mailto:44net-bounces+marius=yo2loj.ro@hamradio.ucsd.edu] On Behalf Of Rob Janssen Sent: Saturday, March 14, 2015 21:10 To: 44net(a)hamradio.ucsd.edu Subject: Re: [44net] TUNNEL vs DIRECT connection of subnets