configure_zabbix_agent(settings) on an access point, which runs no container engine (NetOrk/netork#2571).
zabbix-agentd comes from the feed. The template loads the index first: it lives in RAM, gone after a restart. Zabbix publishes no OpenWrt repository, so _add_zabbix_repository is None.
/etc/zabbix_agentd.conf gets the caller's values (the old file stays as .bak). The agent is enabled in UCI (zabbix_agentd.general.enabled), without which its init script does not start it.
Firewall: tcp/listen_port in the zone that owns the management address, only where a firewall runs (fw4's table or fw3's service). On our APs none runs.
The SNMP agent's firewall step goes through _allow_in_management_zone now, split into zone, rule and reload, so the ratchet holds. The rule it writes is the same, and the SNMP tests stayed green.
The package was checked on ap-1og (OpenWrt 25.12.2, ath79): zabbix-agentd-7.0.32-r1 is in the feed, with 4.1 MB free on the overlay.
Needs napalm-device-types 4.40.0 (ZabbixAgentMixin, NAPALM/napalm-device-types#124). netOrk asks for it in "Install agent" on zabbix_unreachable wherever it has read no container engine on the device.
Checks: ruff, mypy, napalm-standard ratchet/check and 370 tests are green.
`configure_zabbix_agent(settings)` on an access point, which runs no container engine (NetOrk/netork#2571).
- `zabbix-agentd` comes from the feed. The template loads the index first: it lives in RAM, gone after a restart. Zabbix publishes no OpenWrt repository, so `_add_zabbix_repository` is `None`.
- `/etc/zabbix_agentd.conf` gets the caller's values (the old file stays as `.bak`). The agent is enabled in UCI (`zabbix_agentd.general.enabled`), without which its init script does not start it.
- **Firewall:** tcp/`listen_port` in the zone that owns the management address, only where a firewall runs (fw4's table or fw3's service). On our APs none runs.
- The SNMP agent's firewall step goes through `_allow_in_management_zone` now, split into zone, rule and reload, so the ratchet holds. The rule it writes is the same, and the SNMP tests stayed green.
The package was checked on ap-1og (OpenWrt 25.12.2, ath79): `zabbix-agentd-7.0.32-r1` is in the feed, with 4.1 MB free on the overlay.
Needs napalm-device-types 4.40.0 (`ZabbixAgentMixin`, NAPALM/napalm-device-types#124). netOrk asks for it in "Install agent" on `zabbix_unreachable` wherever it has read no container engine on the device.
**Checks:** ruff, mypy, `napalm-standard ratchet`/`check` and 370 tests are green.
An access point runs no container engine. configure_zabbix_agent(settings)
installs zabbix-agentd from the feed after loading the package index, writes the
caller's values into /etc/zabbix_agentd.conf (the old file stays as .bak),
enables the agent in UCI, without which its init script does not start it, and
opens tcp/ListenPort for the allowed sources in the zone that owns the
management address where a firewall runs. Zabbix publishes no repository for
OpenWrt; the feed is the only source.
The SNMP agent's firewall step writes its rule through _allow_in_management_zone
now, split into the zone, the rule and the reload; the rule is the same.
Needs napalm-device-types 4.40.0.
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.
configure_zabbix_agent(settings)on an access point, which runs no container engine (NetOrk/netork#2571).zabbix-agentdcomes from the feed. The template loads the index first: it lives in RAM, gone after a restart. Zabbix publishes no OpenWrt repository, so_add_zabbix_repositoryisNone./etc/zabbix_agentd.confgets the caller's values (the old file stays as.bak). The agent is enabled in UCI (zabbix_agentd.general.enabled), without which its init script does not start it.listen_portin the zone that owns the management address, only where a firewall runs (fw4's table or fw3's service). On our APs none runs._allow_in_management_zonenow, split into zone, rule and reload, so the ratchet holds. The rule it writes is the same, and the SNMP tests stayed green.The package was checked on ap-1og (OpenWrt 25.12.2, ath79):
zabbix-agentd-7.0.32-r1is in the feed, with 4.1 MB free on the overlay.Needs napalm-device-types 4.40.0 (
ZabbixAgentMixin, NAPALM/napalm-device-types#124). netOrk asks for it in "Install agent" onzabbix_unreachablewherever it has read no container engine on the device.Checks: ruff, mypy,
napalm-standard ratchet/checkand 370 tests are green.