View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0000458 | AlmaLinux-9 | firewalld | public | 2024-03-21 15:25 | 2024-03-21 15:25 |
| Reporter | devnullsecurity | Assigned To | |||
| Priority | normal | Severity | minor | Reproducibility | always |
| Status | new | Resolution | open | ||
| Summary | 0000458: firewalld has an issue in 1.2.5. Reportedly fixed in 1.2.7. | ||||
| Description | firewalld has an issue in 1.2.5. Reportedly fixed in 1.2.7. Here is the link to my bug report with firewalld: https://github.com/firewalld/firewalld/issues/1307 firewall-cmd --runtime-to-permanent breaks the running config. Restarting firewalld gets the correct config back. | ||||
| Steps To Reproduce | Add a source to the internal zone (192.168.240.103 in my case). Check active-zones and see that public is there with ens192 run firewall-cmd --runtime-to-permanent Check active zones and see that public is not there. Restart firewalld Check active zones and see that public is back firewall-cmd --zone=internal --add-source=192.168.240.103 firewall-cmd --get-active-zones firewall-cmd --runtime-to-permanent firewall-cmd --get-active-zones systemctl restart firewalld firewall-cmd --get-active-zones | ||||
| Additional Information | The firewalld people said this is probably fixed in 1.2.7, so I guess I am really just asking for that package to be updated in Alma. | ||||
| Tags | No tags attached. | ||||
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2024-03-21 15:25 | devnullsecurity | New Issue |
