napalm-netgear

8 Commits

Include renames

Author	SHA1	Message	Date
Christian Manivong	10a3b1efbf	chore: adopt the NAPALM driver standard driver / standard (pull_request) Successful in 13s Details driver / lint (pull_request) Successful in 11s Details driver / types (pull_request) Successful in 44s Details driver / test (3.10) (pull_request) Successful in 47s Details driver / test (3.11) (pull_request) Successful in 44s Details driver / test (3.12) (pull_request) Successful in 44s Details driver / test (3.13) (pull_request) Successful in 39s Details driver / lowest (pull_request) Failing after 21s Details driver / security (pull_request) Successful in 47s Details driver / build (pull_request) Successful in 22s Details CI / driver (pull_request) Failing after 5m32s Details driver / publish (pull_request) Skipped Details - The distribution is renamed to napalm-netgear-switches: napalm-netgear on PyPI belongs to another project. The import package napalm_netgear and the napalm.drivers entry points netgear_smart and netgear_plus stay; [tool.napalm-standard] package names the import package for the check. README install line and CHANGELOG say the new name. - CI moves to .gitea/workflows/ci.yml and calls the shared driver workflow of NAPALM/driver-standard; .github/ is gone. - requires-python >=3.10 (napalm-device-types needs it), floor napalm-device-types>=4.21.1, LICENSE file, py.typed, SPDX license string, links to git.netork.io, a dev extra with floors, CHANGELOG.md. - mypy strict for the package; napalm_netgear.netgear_plus and napalm_netgear.netgear_smart are exempt for now (139 errors), recorded in the quality baseline with their long and complex functions and the 2070-line netgear_smart module. Coverage floor 48 % (measured 48.23 %). Closes #14	2026-10-23 08:36:28 +02:00
Christian Manivong	fa10d6617b	style: ruff format and the lint rules of the driver standard Mechanical: ruff format, and ruff check --fix with the rule set every NAPALM driver uses (E, F, I, UP, B at line length 100, Python 3.10). What ruff cannot fix comes in the next commit.	2026-10-23 08:32:43 +02:00
Christian Manivong	2de5844f92	fix(ssh): verify the host key netOrk expects, report the one seen (NetOrk/netork#1167 ) CI / test (3.10) (push) Successful in 33s Details CI / test (3.11) (push) Successful in 32s Details CI / test (3.12) (push) Successful in 31s Details CI / test (3.10) (pull_request) Successful in 27s Details CI / test (3.11) (pull_request) Successful in 24s Details CI / test (3.12) (pull_request) Successful in 26s Details The driver accepted any SSH host key. It now verifies through napalm-device-types' HostKeyCheck (>= 4.19.0): with a known key in optional_args["ssh_host_keys"] any other key is refused before login, and every key seen is reported to optional_args["ssh_host_key_observer"]. Without either argument it connects as before (first use).	2026-10-18 21:23:41 +02:00
Christian Manivong	4ccb2b5879	feat: report the firmware Netgear offers, not a warning (0.4.0) CI / test (3.10) (push) Successful in 25s Details CI / test (3.11) (push) Successful in 23s Details CI / test (3.12) (push) Successful in 26s Details CI / test (3.10) (pull_request) Successful in 24s Details CI / test (3.11) (pull_request) Successful in 23s Details CI / test (3.12) (pull_request) Successful in 25s Details The Plus driver looked the newest firmware up in Netgear's download catalogue and named firmware_update_available itself. It now reports get_firmware_offer() (napalm-device-types 4.16 FirmwareOfferMixin): what runs, the newest offered, whether that is newer by Netgear's versioning, and the download link; netOrk names the warning (netOrk #1111). The Smart driver's empty get_device_warnings goes too. Requires napalm-device-types 4.16.0.	2026-10-17 13:04:36 +02:00
Christian Manivong	34554eade9	feat!: configure_snmp_agent with the caller's values replaces fix_snmp (0.3.0) CI / test (3.10) (push) Successful in 24s Details CI / test (3.11) (push) Successful in 23s Details CI / test (3.12) (push) Successful in 25s Details CI / test (3.10) (pull_request) Successful in 24s Details CI / test (3.11) (pull_request) Successful in 23s Details CI / test (3.12) (pull_request) Successful in 24s Details fix_snmp hard-coded community "public" and sent its config-mode line through _send_command, which waits for the exec prompt: in config mode it ran into its timeout and left the session there (#6). netgear_smart implements napalm-device-types 4.13's configure_snmp_agent steps: community (read-only), contact and location from the caller through _apply_config_lines, which waits for any prompt and reports a refused line; config mode is left in all cases; the configuration is saved and the community checked in show snmp. v7 firmware, which has no SNMP commands in its CLI, says so. A value that would break the CLI is refused. napalm-device-types is now declared in pyproject.toml and requirements.txt (#7). BREAKING CHANGE: run_device_action is removed. Closes #6. Part of #7 and #8.	2026-10-17 08:38:07 +02:00
Christian Manivong	6b305c3d47	feat: declare the SNMP health OIDs instead of collecting them (0.2.0) CI / test (3.10) (push) Successful in 32s Details CI / test (3.11) (push) Successful in 32s Details CI / test (3.12) (push) Successful in 33s Details CI / test (3.10) (pull_request) Successful in 32s Details CI / test (3.11) (pull_request) Successful in 29s Details CI / test (3.12) (pull_request) Successful in 33s Details netgear_smart no longer collects over SNMP. SNMP_HEALTH_PROFILE states where the switch publishes uptime (standard sysUpTime), memory (total and free in KiB) and CPU (a text value whose five-second figure counts); the application polls and computes (napalm-device-types docs/STRUCTURE.md). Interface counters now come from the 64-bit ifXTable where the switch has it, as the application reads them for every device.	2026-10-16 12:03:00 +02:00
Christian Manivong	383563d714	fix(deps): pin paramiko>=5.0.0 (CVE-2026-44405)	2026-07-02 12:22:55 +02:00
Christian Manivong	a8ce5a8033	initial commit	2026-05-29 09:13:59 +02:00