Issue #19: Tag iptables rules by queue number so cleanup survives a kill. #57
No reviewers
Labels
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
keyop-go/nfq_forwarder!57
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "issue19_firewall_rules_maintenance"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
deleteNfqIptablesRules ran at startup to remove stale rules, but the comment
tag was keyed on the process's own PID, so it could never match anything left
by a previous, uncleanly-terminated (e.g. killed) run. Rules are now tagged
with a stable, queue-number-scoped prefix (PID is still recorded for
per-rule debugging), and startup cleanup runs after initNfqueue's exclusive
queue bind succeeds, so a misconfigured same-queuenum double-start can't
delete a live sibling instance's rules.
Co-Authored-By: Claude Sonnet 5 noreply@anthropic.com
https://gitlab.keyop.co.uk/keyop/go/nfq_forwarder/-/work_items/19
requested review from @danny
assigned to @danny
LGTM and seems to work in practice.
approved this merge request
mentioned in commit
2e09fff4a9mentioned in commit
ebace5f679