Skip to content

Add IPENCAP to Firewalls Rules Config #678

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.

Sign up for GitHub

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

Merged
merged 1 commit into from
Sep 19, 2022
Merged

Add IPENCAP to Firewalls Rules Config #678

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
15 changes: 6 additions & 9 deletions openapi.yaml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -21463,6 +21463,7 @@ components:
- TCP
- UDP
- ICMP
- IPENCAP
description: >
The type of network traffic to allow.
example: TCP
Expand All @@ -21471,16 +21472,12 @@ components:
description: |
A string representing the port or ports on which traffic will be allowed:

- The string may be a single port, a range of ports, or a comma-separated list
of single ports and port ranges. A space is permitted following each comma.
- A range of ports is inclusive of the start and end values for the range. The
end value of the range must be greater than the start value.
- The string may be a single port, a range of ports, or a comma-separated list of single ports and port ranges. A space is permitted following each comma.
- A range of ports is inclusive of the start and end values for the range. The end value of the range must be greater than the start value.
- Ports must be within 1 and 65535, and may not contain any leading zeroes. For example, port "080" is not allowed.
- Ports may not be specified if a rule's protocol is `ICMP`. At least one port
must be specified if a rule's protocol is `TCP` or `UDP`.
- The ports string can have up to 15 *pieces*, where a single port is treated
as one piece, and a port range is treated as two pieces. For example,
the string "22-24, 80, 443" has four pieces.
- Ports may not be specified if a rule's protocol is `ICMP` or `IPENCAP`.
- At least one port must be specified if a rule's protocol is `TCP` or `UDP`.
- The ports string can have up to 15 *pieces*, where a single port is treated as one piece, and a port range is treated as two pieces. For example, the string "22-24, 80, 443" has four pieces.
example: '22-24, 80, 443'
addresses:
type: object
Expand Down