18 Nov
2014
18 Nov
'14
3:37 p.m.
On Tue, Nov 18, 2014 at 12:23 PM, Rob Janssen <pe1chl(a)amsat.org> wrote:
Ok, with the exception that my systems cannot route to there, because the
gateway is
within network-44. Discussed before. Hopefully will change after we are
on BGP ourselves,
Once your 44 network is available via BGP, let us (44.24.240/20) know
and we can whitelist your network for direct routing. Of course the
default route is the Internet BGP route table, but an entry in the
encap file will override that. If you want to route to us directly, I
can tell our systems to ignore your entry in the encap file. We have
this arrangement with a few other BGP-announced networks so we don't
have to maintain tunnels to them.
Tom KD7LXL
>route addprivate 44.24.240/20 encap 44.24.221.1
Now this one is ok. The gateway (44.24.221.1) is BGP announced, but not in
the encap file. Everything ok and working.