shorewall: make sure asterisk ipset are ready #118
Merged
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
If the ipset are not created, shorewall may fail at boot with: shorewall[989]: WARNING: Ipset f2b-asterisk-tcp does not exist /etc/shorewall/blrules (line 30) shorewall[989]: WARNING: Ipset f2b-asterisk-udp does not exist /etc/shorewall/blrules (line 31)
|
@stephdl its seems you were right: there is one case where we need to explicitly create the ipset. |
|
yes it is....I was not sure if we could remove this fragment but now I know it is a mandatory. approved |
stephdl
approved these changes
Dec 3, 2021
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.
If the ipset are not created, shorewall may fail at boot with:
NethServer/dev#6608