ClearFoundation Tracker - ClearOS
View Issue Details
0000948ClearOSapp-content-filter - Content Filterpublic2013-01-22 10:252013-01-28 15:16
dloper 
user2 
normalminoralways
closedfixed 
6.3.0 
6.3.0 Updates6.4.0 Beta 1 
0000948: Incoming firewall module fails to delete Blocked Incoming Connections when it is defined as a CIDR
In the incoming firewall module the interface allows you to add CIDR addresses to the block rules under the Blocked Incoming Connections but if you have a rule there it does not allow you to remove it because of the slash. It won't disable it either if you try that.

Please add support for deletion and disabling of CIDR addresses to the Blocked Incoming Connections section of the incoming firewall rules module.

Create a rule under Blocked Incoming Connections in the Incoming firewall app by clicking add. Call the rule 'test1' and for the host, type '1.1.1.0/24', click 'Add.

Now that it shows up, delete or disable the rule. Disable will simply fail to do so. Deletions will give the error will give a confirmation wrongly by reporting only the IP and will preclude the /24. When you confirm, it will state: "Rule does not exist." as the error.
Workaround: to manually delete the rule, edit the /etc/clearos/firewall.conf file and look for lines that have the register 0x10000002. Removal of the whole line removes it from the interface. After the line is removed, save the file and restart the firewall service (service firewall restart).
No tags attached.
duplicate of 0000920closed  Block rule does not handle network notation 
Issue History
2013-01-22 10:25dloperNew Issue
2013-01-28 15:10user2ProjectClearCenter => ClearOS
2013-01-28 15:12user2Relationship addedduplicate of 0000920
2013-01-28 15:16user2Note Added: 0000650
2013-01-28 15:16user2Statusnew => resolved
2013-01-28 15:16user2Fixed in Version => 6.4.0 Beta 1
2013-01-28 15:16user2Resolutionopen => fixed
2013-01-28 15:16user2Assigned To => user2
2013-01-28 15:16user2Statusresolved => closed

Notes
(0000650)
user2   
2013-01-28 15:16   
This may get pushed to 6.3.0 Updates, but the fix is already available in updates-testing (6.4.0 Beta 1).