RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 1637894 - There is no check for the toaddr= option when add-forward-port is used on firewalld
Summary: There is no check for the toaddr= option when add-forward-port is used on fir...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: firewalld
Version: 7.5
Hardware: x86_64
OS: Linux
unspecified
low
Target Milestone: rc
: ---
Assignee: Eric Garver
QA Contact: Jiri Peska
URL:
Whiteboard:
Depends On:
Blocks: 1723958
TreeView+ depends on / blocked
 
Reported: 2018-10-10 09:54 UTC by Fani Orestiadou
Modified: 2023-09-07 19:26 UTC (History)
6 users (show)

Fixed In Version: firewalld-0.5.3-5.el7
Doc Type: No Doc Update
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-03-31 20:00:54 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2020:1109 0 None None None 2020-03-31 20:01:39 UTC

Description Fani Orestiadou 2018-10-10 09:54:42 UTC 
Description of problem:

It is possible to specify whatever name instead of the "toaddr" option and firewalld is accepting it, but skips the value. 

--add-forward-port=port=portid[-portid]:proto=protocol[:toport=portid[-portid]][:toaddr=address[/mask]] [--timeout=seconds]

Version-Release number of selected component (if applicable):
I was able to reproduce it on all RHEL 7.x versions.

How reproducible:

Type whatever word instead of toaddr option. 

Steps to Reproduce:

$ cat /etc/redhat-release 
Red Hat Enterprise Linux Workstation release 7.5 (Maipo)
$ firewall-cmd  --add-forward-port=port=1213:proto=tcp:toport=22:TOWHATEVER=10.10.10.1
success
$ firewall-cmd --list-all
public (active)
  target: default
  icmp-block-inversion: no
  interfaces: eth0 ens3 ens10 team0
  sources: 
  services: dhcpv6-client ssh
  ports: 22/tcp
  protocols: 
  masquerade: no
  forward-ports: port=1213:proto=tcp:toport=22:toaddr=    <---
  source-ports: 
  icmp-blocks: echo-request
  rich rules: 

Actual results:

The command is successful and the toaddr value is missing

Expected results:
Some error message like
firewall-cmd: invalid parameter TOWHATEVER

Please let me know in case any further details are needed. 

Thank you 
Fani

Additional info:
Comment 2 Eric Garver 2018-10-11 12:28:41 UTC 
This has been fixed upstream. Recent versions of firewalld are much better at propagating errors to the UIs/user.

# firewall-cmd  --add-forward-port=port=1213:proto=tcp:toport=22:TOWHATEVER=10.10.10.1
Error: INVALID_FORWARD: invalid forward port arg 'TOWHATEVER'
Comment 4 Eric Garver 2018-10-11 12:36:56 UTC 
Mistakenly closed. Reopening.
Comment 10 errata-xmlrpc 2020-03-31 20:00:54 UTC 
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2020:1109
Note You need to log in before you can comment on or make changes to this bug.