-
-
Notifications
You must be signed in to change notification settings - Fork 18
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Support for comments and more types #75
base: master
Are you sure you want to change the base?
Conversation
Optional[range] => String, | ||
Optional[comment] => String, |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
can you make this a bit more strict? Are empty strings okay or should we enforce a minimal length?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Optional[range] => Pattern[/^6553[0-5]|655[0-2][0-9]|65[0-4][0-9]{2}|6[0-4][0-9]{3}-6553[0-5]|655[0-2][0-9]|65[0-4][0-9]{2}|6[0-4][0-9]{3}$/],
Optional[comment] => Pattern[/^(.*").*$/],
Port regex blatantly stolen from StackOverflow
According do documentation only "
is an illegal character in the comment.
thanks for the PR. can you please add some unit tests as well? |
Pull Request (PR) description
Add support for comments (#5) and the types from the man page.
counters skbinfo markmask
options are not implemented, they are boolean options. If anyone has any advice on how to implement that cleanly ...example with using hiera data for
bitmap:port
:If you want to limit to udp:
This was primarily implemented to be able to create non consecutive port lists as
iptables
only support a maximum of 15 ports with the--multiports
and theXT_MULTI_PORTS
compile setting source