5 Aug
2015
5 Aug
'15
8:36 a.m.
Hi Lynwood and all,
the latest lessons learned specially from Tom and Rob concern
and imply the standard use of the IPIP encap tunnels (i.e. tunl0)
to effectively link the other, BGP-announced or not, gateways or
amprnets and the amprgw at ucsd.edu/portal.ampr.org.
Adding all BGP routes are not effective being from here, on my site.
Quote from Tom:
We are properly BGP routed, so any machine on the
internet (and not
behind amprgw) should be able to access it.
so, it is impossible, for now, access the hamwan.org being
behind amprgw, as explained.
gus
Gus, Nigel, Tom, et. al,
So are you saying that:
I CAN, or CANNOT send encap traffic to BGPed subnets:
via 169.228.66.251 dev tunl0
cache
My understanding is that there was a routing change at AMPRGW that
made this possible.
If not, it is still remains necessary:
- to manually add all ALL BGP routes (which I'm willing to do, I just
need to KNOW them all), or;
- that they operate an IPENCAP tunnel using a COMMERCIAL IP ADDRESS.
- Lynwood