24 May
2017
24 May
'17
1:31 p.m.
There is also the question of how this data is to be
transferred
from the portal to amprgw. We currently download the same encap
file that any gateway would use. Some new file format would also
be needed.
It should be trivial to add another file, gateways.txt, that contains
the per-gateway information. Or it could be added as comment lines into
the existing encap.txt file. Maybe it would also make some tunnel
creation scripts simpler when there is a section with gateway info
(one line for each gateway, with a unique ID, the external IP, and
info like proposed today: an internal IP and the "accept internet traffic"
flag) ahead of the traditional route lines. It would allow the preparation
of all required tunnel interfaces in environments where that is required
before parsing the subnet routes.
Rob