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.

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

Jump to bottom

Documentation is inconsistent on which protocols are accepted for rich language policies #991

Closed
dead-claudia opened this issue Jul 17, 2022 · 1 comment · Fixed by #995 · May be fixed by firewalld/firewalld.github.io#22
Closed

Documentation is inconsistent on which protocols are accepted for rich language policies #991

dead-claudia opened this issue Jul 17, 2022 · 1 comment · Fixed by #995 · May be fixed by firewalld/firewalld.github.io#22

Comments

@dead-claudia
Copy link

dead-claudia commented Jul 17, 2022 •
edited
Loading

Which is reality for which? And do they actually just ultimately rely on /etc/protocols in the end as well, or is this validated within firewalld itself?

Also, do the related protocol fields correspond with this in zones and helpers as well? Or do they also simply use the hardcoded constants?
@TorontoMedia
Copy link
Collaborator

TorontoMedia commented Jul 17, 2022 •
edited
Loading

Thank you for reporting these errors in consistency.

Protocols for port, forward-port, and source-port are limited to tcp|udp|sctp|dccp and that applies to zones and helpers too.

For element protocol, it must be an integer between 0 and 255 or a valid protocol in /etc/protocols.

TorontoMedia added a commit to TorontoMedia/firewalld that referenced this issue Jul 17, 2022
@TorontoMedia
docs: add protocols to rich and zones
3aa5f0c 
Fixes: firewalld#991
@TorontoMedia TorontoMedia mentioned this issue Jul 17, 2022
Merged
TorontoMedia added a commit to TorontoMedia/firewalld.github.io that referenced this issue Jul 17, 2022
@TorontoMedia
docs: add supported protocol options
f9f1f03 
Fixes: firewalld/firewalld#991
@TorontoMedia TorontoMedia mentioned this issue Jul 17, 2022
Open
TorontoMedia added a commit to TorontoMedia/firewalld.github.io that referenced this issue Jul 18, 2022
@TorontoMedia
docs: add supported protocol options
b1249a5 
Fixes: firewalld/firewalld#991
erig0 pushed a commit that referenced this issue Aug 26, 2022
@TorontoMedia @erig0
docs: add protocols to rich and zones
7065f70 
Fixes: #991
erig0 pushed a commit to erig0/firewalld that referenced this issue Sep 28, 2022
@TorontoMedia @erig0
docs: add protocols to rich and zones
e26fd90 
Fixes: firewalld#991
(cherry picked from commit 7065f70)
erig0 pushed a commit that referenced this issue Sep 28, 2022
@TorontoMedia @erig0
docs: add protocols to rich and zones
191cea4 
Fixes: #991
(cherry picked from commit 7065f70)
erig0 pushed a commit to erig0/firewalld that referenced this issue Sep 28, 2022
@TorontoMedia @erig0
docs: add protocols to rich and zones
78c5e0d 
Fixes: firewalld#991
(cherry picked from commit 7065f70)
erig0 pushed a commit that referenced this issue Sep 28, 2022
@TorontoMedia @erig0
docs: add protocols to rich and zones
6867742 
Fixes: #991
(cherry picked from commit 7065f70)
erig0 pushed a commit to erig0/firewalld that referenced this issue Sep 28, 2022
@TorontoMedia @erig0
docs: add protocols to rich and zones
c878df8 
Fixes: firewalld#991
(cherry picked from commit 7065f70)
erig0 pushed a commit that referenced this issue Sep 28, 2022
@TorontoMedia @erig0
docs: add protocols to rich and zones
9111ad1 
Fixes: #991
(cherry picked from commit 7065f70)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
2 participants
@dead-claudia @TorontoMedia