Github user swill commented on the issue:
https://github.com/apache/cloudstack/pull/872
Tomorrow I will pick a recommended S2S VPN configuration and verify the
rest of the different possible options with that single configuration to give a
better global picture of the state of this PR.
Also, the testing of the Remote Access VPN connections on my branch are
going well as well. We have found a pretty serious unrelated bug in the IP
allocation in the VR on VR reboot. If a PF rule is set on the VR and it is
reboot, the `eth1` interface gets the PF IP instead of the Source NAT IP, so
that breaks the Remote Access VPN connection. We have been troubleshooting it,
but the problem has been relatively tricky to track down. More details on
that once we root cause the issue.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---
