5 Aug
2015
5 Aug
'15
3:32 a.m.
Nigel,
It does?
We considered a lot of these issues before (mainly when developing the
first version of the boot script). Brian is able to ping because, as I
recall, his actual Public IP address is 44...those who IPIP, our IPs are
not.
- IPIP subnets would be required to configure masquerading, making our
Public IPs the one that actually reaching his device, or to require no
further configuration;
- have traffic for BGPed subnets sent through the Main AMPRGW at
44.0.0.1 (on our table 44).
Also, the Security Update and Notes section of the startampr wiki covers
issues for IPENCAP operators with:
-reaching BGP subnets; and
- 44 subnets behind a tunnel with a 44 IP.
(read the last point in the NOTES section - Rob is the one who
discovered it years ago, if you read his email earlier regarding more
specific routes)
http://wiki.ampr.org/index.php/Startampr#2.0_Security_Update
- Lynwood
This is incredible news! WOOOOOOOOOO!
Thank you much for the work in that regard. This simplifies so much of the
interconnectivity between BGP routed subnets, and IPIP users.
Nigel
K7NVH