0000948: Incoming firewall module fails to delete Blocked Incoming Connections when it is defined as a CIDR

View Issue Details [ Jump to Notes ]

[ Issue History ] [ Print ]

Project

Category

View Status

Date Submitted

Last Update

0000948

ClearOS

app-content-filter - Content Filter

public

2013-01-22 10:25

2013-01-28 15:16

Reporter

dloper

Assigned To

user2

Priority

normal

Severity

minor

Reproducibility

always

Status

closed

Resolution

fixed

Platform

OS Version

Product Version

6.3.0

Target Version

6.3.0 Updates

Fixed in Version

6.4.0 Beta 1

Summary

0000948: Incoming firewall module fails to delete Blocked Incoming Connections when it is defined as a CIDR

Description

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.

Steps To Reproduce

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.

Additional Information

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).

Tags

No tags attached.

Attached Files

Relationships

duplicate of

0000920

closed

Block rule does not handle network notation

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).

Issue History
Date Modified	Username	Field	Change
2013-01-22 10:25	dloper	New Issue
2013-01-28 15:10	user2	Project	ClearCenter => ClearOS
2013-01-28 15:12	user2	Relationship added	duplicate of 0000920
2013-01-28 15:16	user2	Note Added: 0000650
2013-01-28 15:16	user2	Status	new => resolved
2013-01-28 15:16	user2	Fixed in Version	=> 6.4.0 Beta 1
2013-01-28 15:16	user2	Resolution	open => fixed
2013-01-28 15:16	user2	Assigned To	=> user2
2013-01-28 15:16	user2	Status	resolved => closed

ClearOS Bug Tracker