Description of problem: In current version of firewalld, it is possible and valid to write # firewall-cmd --add-port=120-100 which causes in iptables in -A IN_public_allow -p tcp -m tcp --dport 100:120 ... Swapping port ranges was removed from iptables back in 2002 (see to bz1124382) and I think that it will lead only to mistakes. Some says that this is useful feature, but I don't see any gain in this feature. Another option was to allow this, but to trigger some Warning message to inform user that this is maybe not what he wanted. Version-Release number of selected component (if applicable): upstream git How reproducible: deterministic
This bug appears to have been reported against 'rawhide' during the Fedora 22 development cycle. Changing version to '22'. More information and reason for this action is here: https://fedoraproject.org/wiki/Fedora_Program_Management/HouseKeeping/Fedora22
Fedora 22 changed to end-of-life (EOL) status on 2016-07-19. Fedora 22 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.