Add DESTINATION as a filter for stanzas as well as ENABLE_DESTINATION_RU... #140
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.
...LE which will explicitly set the destination in the firewall rule
access.conf stanzas can now also include a DESTINATION, which will only activate that stanza if destination IP in the SPA packet IP header matches the set in the stanza list. This essentially works exactly the same way the SOURCE directive does (except that it does not dictate a new stanza).
In addition, ENABLE_DESTINATION_RULE controls whether fwknopd will set the destination field on the firewall rule to the destination address specified on the incoming SPA packet. This is useful for interfaces with multiple IP addresses hosting separate services. If ENABLE_IPT_OUTPUT is set to "Y", the source field of the firewall rule is set. FORWARD and SNAT rules are not affected however, DNAT rules will also have their destination field set. The default is "N", which sets the destination field to 0.0.0.0/0 (any).