21 Apr
2018
21 Apr
'18
6:51 a.m.
On 20/04/18 01:48, Brian Kantor wrote:
That is what the block 44.190.0.0 is set aside for.
The intent is
to divide it up into /24s to be BGP-routed directly to the Internet,
and people who otherwise would send 44.x.x.x traffic via radio or
tunnel should insert a special routing rule that directs 44.190.0.0/16
to their ISP instead of the radio or tunnels, if they can.
The problem I have with
this is when traffic is routed via the regular
ISP, the source address is no longer 44.x, it's the public IP of the NAT
router. I'd like to see BGP announced subnets also directly accessible
via a tunnel for those of us running IPIP tunnels. I'll soon be in a
good position to test, as I now have both a direct BGP connected subnet
and a tunnelled one at different sites. Obviously, I have a vested
interest in getting the routing right for my own purposes.
The way I see it, the 44.190 and other directly connected space still
need a tunnel interface and routing to communicate transparently with
the tunnelled parts of AMPRnet (and avoid the delays of the main
gateway). What I'd like to know is what is the best practice for doing
this, that won't result in traffic that gets addresses mangled by NAT at
one end?
I have a general idea, but as you know, the devil is in the detail. :)
--
73 de Tony VK3JED/VK3IRL
http://vkradio.com