Anonymous | Login | 2024-12-22 00:05 MST |
Main | My View | View Issues | Change Log | Roadmap | Repositories |
View Issue Details [ Jump to Notes ] | [ Issue History ] [ Print ] | ||||||||
ID | Project | Category | View Status | Date Submitted | Last Update | ||||
0002501 | ClearOS | app-firewall-custom - Custom Firewall | public | 2015-04-22 11:11 | 2015-06-09 18:47 | ||||
Reporter | bchambers | ||||||||
Assigned To | dsokoloski | ||||||||
Priority | normal | Severity | minor | Reproducibility | have not tried | ||||
Status | closed | Resolution | fixed | ||||||
Platform | OS | OS Version | |||||||
Product Version | 6.6.0 Updates | ||||||||
Target Version | 6.6.0 Updates | Fixed in Version | |||||||
Summary | 0002501: Does event get triggered for custom firewall rule | ||||||||
Description | Supporting a customer, it would appear his firewall did not get restarted automatically after adding a custom firewall rule via Webconfig. Does a firewall restart get triggered when the following file get modified: /etc/clearos/firewall.d/custom | ||||||||
Tags | No tags attached. | ||||||||
Attached Files | |||||||||
Notes | |
(0001541) user2 2015-05-20 18:41 |
The firewall event catches changes to /etc/clearos/firewall.d/custom, but not the creation of the file. Adding the first custom firewall rule will not trigger a firewall restart, but all subsequent changes are fine. |
Issue History | |||
Date Modified | Username | Field | Change |
2015-04-22 11:11 | bchambers | New Issue | |
2015-04-22 11:11 | bchambers | Status | new => assigned |
2015-04-22 11:11 | bchambers | Assigned To | => dsokoloski |
2015-05-20 18:39 | user2 | Category | app-clearsync - Synchronization and Events => app-firewall-custom - Custom Firewall |
2015-05-20 18:41 | user2 | Note Added: 0001541 | |
2015-05-20 18:41 | user2 | Issue cloned: 0002811 | |
2015-05-20 18:42 | user2 | Severity | major => minor |
2015-05-20 18:46 | user2 | Status | assigned => resolved |
2015-05-20 18:46 | user2 | Resolution | open => fixed |
2015-06-09 18:47 | user2 | Status | resolved => closed |