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.

Description of problem:
* --timeout should accept time specifiers like minute, hour, day or week

Version-Release number of selected component (if applicable):
firewalld-0.3.4-1

How reproducible:
always

Steps to Reproduce:
firewall-cmd --add-service=http --timeout 4m

Expected results:
please fix or provide information why do you think it shouldn't be fixed this way
thanks

Additional info:
CCed affiliated users

The timeout is handled by firewalld and not by netfilter. firewalld removes all rules and netfilter helpers, that have been added to activate the feature with the timeout after it timed out.

If you enable for example port forwarding, this is more than one rule and depends also on the target (if it gets forwarded locally or not). netfilter is not able to handle this in a good and usable way.

The timeout is used in the same way in the command line client and also in the D-Bus interface: As a natural number. Allowing the use of other values than seconds in the command line client will not be doable with the current D-Bus interface.

Isn't it possible to translate the value from e.g. hours to seconds before sending it over D-Bus?
If only seconds are possible, then user would need to use something like this:
firewall-cmd --add-service http --timeout $((4*60*60)) to achive 4h value.

Moving to 7.1.

Upstream commit:
https://git.fedorahosted.org/cgit/firewalld.git/commit/?id=dd77e17ea844948094f3c2c5348dfa762051858e

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://rhn.redhat.com/errata/RHBA-2015-0520.html