Github user swill commented on the issue:
https://github.com/apache/cloudstack/pull/1741
I have isolated and fixed the issue where the reboot through the API
results in the Remote Access VPN no longer working if either a PF rule or
Static NAT rule is defined. The problem existed because the public IPs on
`eth1` were getting reversed, so the Source NAT IP was no longer the primary
IP. Because of this, the Remote Access VPN would stop working after an API VR
reboot if there were other public IPs configured on that VR.
I have done basic testing to verify this fixes the problem. We are doing
more extensive testing now...
---
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.
---
