5 Aug
2015
5 Aug
'15
7:57 a.m.
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