fix_snmp enabled community public and opened UDP/161 from any source on every interface. Now configure_snmp_agent(settings) (napalm-device-types 4.13):
install os-net-snmp only when missing;
community/contact/location/listen from the caller (DNS name → listen everywhere; refused save fails the fix);
one floating pass rule per allowed source; the old [netork] Allow SNMP any-source rule and rules of an earlier run are replaced, operators' rules untouched; no sources → firewall unchanged;
restart net-snmp. The hand-built UDP probe goes.
The REST API cannot tell which address netOrk comes from (get_management_peer not implemented), so netOrk needs the snmp_allowed_sources setting for OPNsense; without it the firewall is left as it is.
Not in this PR (#16): the other [netork] markers (DNS overrides, certificates, ping jobs) — the DNS tag interacts with netork-01's DNS work (#1123).
Closes#13. Merge order: independent; netOrk already asks for the template first (#1130), so it needs only the pin bump in netOrk.
Security fix #13 and step 4 of NetOrk/netork#1105.
`fix_snmp` enabled community `public` and opened UDP/161 **from any source on every interface**. Now `configure_snmp_agent(settings)` (napalm-device-types 4.13):
- install os-net-snmp only when missing;
- community/contact/location/listen from the caller (DNS name → listen everywhere; refused save fails the fix);
- one floating pass rule **per allowed source**; the old `[netork] Allow SNMP` any-source rule and rules of an earlier run are replaced, operators' rules untouched; no sources → firewall unchanged;
- restart net-snmp. The hand-built UDP probe goes.
The REST API cannot tell which address netOrk comes from (`get_management_peer` not implemented), so netOrk needs the `snmp_allowed_sources` setting for OPNsense; without it the firewall is left as it is.
Not in this PR (#16): the other `[netork]` markers (DNS overrides, certificates, ping jobs) — the DNS tag interacts with netork-01's DNS work (#1123).
Closes #13. **Merge order:** independent; netOrk already asks for the template first (#1130), so it needs only the pin bump in netOrk.
fix_snmp enabled os-net-snmp with community "public", contact
netork@localhost and location "Managed by netOrk", and added a
floating pass rule for UDP/161 from any source on every interface: a
firewall managed over WAN answered its SNMP tree to anyone there (#13).
The driver implements napalm-device-types 4.13's configure_snmp_agent
steps instead:
- install: os-net-snmp only when missing (a reinstall resets it);
- configure: community, contact, location and listen address from the
caller; a DNS name is not a listen address; a refused save fails;
- firewall: one floating pass rule per allowed source, the old
any-source rule and rules of an earlier run replaced, operators'
rules untouched; no sources, no change;
- start: restart net-snmp.
The hand-built UDP probe goes; the caller asks the agent itself.
BREAKING CHANGE: run_device_action is removed. Requires
napalm-device-types 4.13.
Closes#13
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.
Security fix #13 and step 4 of NetOrk/netork#1105.
fix_snmpenabled communitypublicand opened UDP/161 from any source on every interface. Nowconfigure_snmp_agent(settings)(napalm-device-types 4.13):[netork] Allow SNMPany-source rule and rules of an earlier run are replaced, operators' rules untouched; no sources → firewall unchanged;The REST API cannot tell which address netOrk comes from (
get_management_peernot implemented), so netOrk needs thesnmp_allowed_sourcessetting for OPNsense; without it the firewall is left as it is.Not in this PR (#16): the other
[netork]markers (DNS overrides, certificates, ping jobs) — the DNS tag interacts with netork-01's DNS work (#1123).Closes #13. Merge order: independent; netOrk already asks for the template first (#1130), so it needs only the pin bump in netOrk.