Red Hat Bugzilla – Bug 994044
cli: --timeout should accept time specifiers
Last modified: 2015-03-05 08:22:44 EST
Description of problem:
* --timeout should accept time specifiers like minute, hour, day or week
Version-Release number of selected component (if applicable):
Steps to Reproduce:
firewall-cmd --add-service=http --timeout 4m
please fix or provide information why do you think it shouldn't be fixed this way
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.
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.