High Availability gateway trigger fix for site to site VPN #178
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…lability, which is to be expected. Modify the warning trigger so that it does not trigger for VPN connections when the pfSense is a CARP slave.
|
I'm sorry but I'm not experiencing such behavior. Do you set the proper outbound NAT rules for VPN on secondary? gateway should be accessible from secondary no matter what. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
When high availability is used, the gateway on the CARP slave on an openVPN connection is unreachable.
The trigger for high packet loss will fire, but this is normal.
I added the ability for the script to track which connection belongs to which gateway, and an extra condition to this trigger. The trigger will not fire if: