Red Hat Bugzilla – Bug 961640
[RFE] Firewalld should allow rules that include subnets
Last modified: 2014-06-11 22:28:49 EDT
Description of problem:
Firewall's often include rules that define allows / blocks based on subnet. For example, I may wish anything on the same subnet as my adapter to access port 80, but not outside of the subnet. On a routed network, I may wish to only allow a seperate subnet to access something, IE allowing a monitoring VLAN access to SNMP for example.
This amounts to two features
1) Create a rule that allows traffic only from the subnet of the adapter to this port in this zone.
2) Create a rule that allows traffic from a user defined subnet to adapters of this zone.
The difference being 1 auto-detects the subnet from the adapter, the second is set by the administrator.
This message is a reminder that Fedora 18 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 18. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as WONTFIX if it remains open with a Fedora
'version' of '18'.
Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version'
to a later Fedora version prior to Fedora 18's end of life.
Thank you for reporting this issue and we are sorry that we may not be
able to fix it before Fedora 18 is end of life. If you would still like
to see this bug fixed and are able to reproduce it against a later version
of Fedora, you are encouraged change the 'version' to a later Fedora
version prior to Fedora 18's end of life.
Although we aim to fix as many bugs as possible during every release's
lifetime, sometimes those efforts are overtaken by events. Often a
more recent Fedora release includes newer upstream software that fixes
bugs or makes them obsolete.
Please have a look at rich rules. It has source and destination addresses and address ranges in the rules. You can also bind source addresses and address ranges to zones.
Yes these provide what I need, but in general firewalld is much harder to "achieve" the same as what iptables allows. Commands with lots of -- in them certainly makes typing them out difficult (Fixing that alone would make my life easier!).