On a host running firewalld, the SNMP fix inserted an iptables ACCEPT for udp/161. firewalld's own nftables table rejects the packet anyway, so the step reported the port open while SNMP stayed blocked.
With firewalld active (systemctl is-active firewalld), _allow_snmp_sources now adds a rich rule per allowed source to the default zone and every active zone, at runtime and --permanent, each only when the zone lacks it. There is no --reload, which would drop runtime rules others keep (Docker). ufw and iptables hosts behave as before.
Tests: the step's commands on a firewalld host, plus the generated shell run against a stand-in firewall-cmd (zones, IPv4/IPv6, no duplicate rules). 408 passed; test_time_sync fails on main already (#78).
On a host running firewalld, the SNMP fix inserted an iptables ACCEPT for udp/161. firewalld's own nftables table rejects the packet anyway, so the step reported the port open while SNMP stayed blocked.
With firewalld active (`systemctl is-active firewalld`), `_allow_snmp_sources` now adds a rich rule per allowed source to the default zone and every active zone, at runtime and `--permanent`, each only when the zone lacks it. There is no `--reload`, which would drop runtime rules others keep (Docker). ufw and iptables hosts behave as before.
Tests: the step's commands on a firewalld host, plus the generated shell run against a stand-in `firewall-cmd` (zones, IPv4/IPv6, no duplicate rules). 408 passed; `test_time_sync` fails on main already (#78).
Closes #77
On a host running firewalld, iptables is installed too, so the SNMP fix
inserted an iptables ACCEPT. firewalld keeps its own nftables table, whose
reject wins over it, and the step reported the port open while SNMP
stayed blocked.
With firewalld active, the step now adds a rich rule per allowed source to
the default zone (which takes interfaces in no zone, such as a WireGuard
interface) and to every active zone, at runtime and permanently, each only
when missing. No reload, which would drop rules others keep at runtime.
Closes#77
linux.py had grown past its recorded size with the firewalld rule. The
snmpd.conf rendering, the install commands and the firewalld rule now
live in _snmp_agent.py; linux.py shrinks to 2014 lines and the baseline
records that.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
On a host running firewalld, the SNMP fix inserted an iptables ACCEPT for udp/161. firewalld's own nftables table rejects the packet anyway, so the step reported the port open while SNMP stayed blocked.
With firewalld active (
systemctl is-active firewalld),_allow_snmp_sourcesnow adds a rich rule per allowed source to the default zone and every active zone, at runtime and--permanent, each only when the zone lacks it. There is no--reload, which would drop runtime rules others keep (Docker). ufw and iptables hosts behave as before.Tests: the step's commands on a firewalld host, plus the generated shell run against a stand-in
firewall-cmd(zones, IPv4/IPv6, no duplicate rules). 408 passed;test_time_syncfails on main already (#78).Closes #77