ClearFoundation Tracker - ClearOS | |||||
| View Issue Details | |||||
| ID | Project | Category | View Status | Date Submitted | Last Update |
| 0014261 | ClearOS | app-firewall - Firewall | public | 2017-04-06 13:49 | 2020-03-05 04:51 |
| Reporter | dloper | ||||
| Assigned To | |||||
| Priority | low | Severity | minor | Reproducibility | have not tried |
| Status | closed | Resolution | suspended | ||
| Platform | OS | OS Version | |||
| Product Version | 7.3.1 | ||||
| Target Version | Fixed in Version | ||||
| Summary | 0014261: Import of interface names doesn't jive with systemd | ||||
| Description | When someone does a backup and restore of their system using the configuration backup, the 1:1 NAT rules can cause the imported system to firewall panic when the interface name on 7 doesn't match because of the systemd renaming. Perhaps there is a way to embed the proposed interface name so that when the import occurs it doesn't trash the firewall stack. Another way to address it in 7 would be to mark all firewall rules that contain 'ethN' interface names to be in a permanent disable state (ie. delete only) That way the user can re-add the rule on restore. This activity requirement should show up in the restore scripts output log as 'admin intervention required'. | ||||
| Steps To Reproduce | |||||
| Additional Information | |||||
| Tags | No tags attached. | ||||
| Relationships | |||||
| Attached Files | |||||
| Issue History | |||||
| Date Modified | Username | Field | Change | ||
| 2017-04-06 13:49 | dloper | New Issue | |||
| 2017-04-10 09:08 | user2 | Status | new => acknowledged | ||
| 2017-04-10 10:52 | user2 | Product Version | 6.8.0 => 7.3.1 | ||
| 2017-04-10 10:52 | user2 | Target Version | 6.9.0 => | ||
| 2020-03-05 04:51 | NickH | Note Added: 0013411 | |||
| 2020-03-05 04:51 | NickH | Status | acknowledged => closed | ||
| 2020-03-05 04:51 | NickH | Resolution | open => suspended | ||
| Notes | |||||
|
|
|||||
|
|
||||