Skip to content
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

Firewall: rule_create accepts both integer and string, as port range (e.g. 21-22) #8

Open
andreisusanu opened this issue Apr 10, 2019 · 0 comments

Comments

@andreisusanu
Copy link

According to the Firewall documentation, rule_create accepts the port parameter as integer or string.

port string (optional) TCP/UDP only. This field can be an integer value specifying a port or a colon separated port range.

The current implementation accepts only integer values, so it cannot create a rule on port range.

Pull request

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant