driver / standard (pull_request) Successful in 17s
driver / lint (pull_request) Successful in 15s
driver / types (pull_request) Successful in 1m18s
driver / test (3.13) (pull_request) Successful in 4m9s
driver / test (3.12) (pull_request) Successful in 4m28s
driver / lowest (pull_request) Successful in 3m41s
driver / build (pull_request) Successful in 34s
driver / security (pull_request) Successful in 1m18s
CI / driver (pull_request) Successful in 6m0s
driver / publish (pull_request) Skipped
The driver's evidence was all vendor-wide: Zyxel's enterprise OID, Zyxel OUIs and "zyxel" on the web page. Every managed Zyxel device has all three, and they were the driver's whole maximum, so discovery named any Zyxel switch this gateway with high confidence. Discovery now also fetches /getRSAPublickKey on ports 80 and 443, the DAL key exchange the driver logs in with, without counting the port. Its "RSAPublicKey" answer weighs 24: vendor-wide evidence alone is 28 of 52 (medium), a gateway 52 of 52, or 37 of 52 without SNMP. Closes #13
2.5 KiB
2.5 KiB
Changelog
All notable changes to this driver. The format follows Keep a Changelog, versions follow Semantic Versioning.
[Unreleased]
Changed
- Python 3.12 is the floor (
requires-python = ">=3.12"): netOrk runs every driver on 3.12, so 3.10 and 3.11 are no longer tested (NAPALM/driver-standard#6). - The floor on napalm is 5.1: older releases import
pkg_resources, which a Python 3.12 venv no longer has.
Fixed
get_arp_table()reports an unknown age as-1.0(napalm-device-types'ARP_AGE_UNKNOWN) instead of0.0, which means "confirmed just now": the host list says a host is active, not when the gateway last saw it (NetOrk/netork#1327).- The HTTP fingerprint no longer counts
gs1920andgs2210as evidence for this driver: they are Zyxel switches, and discovery offered this gateway driver for them (#4). - Discovery tells a DAL gateway from any other Zyxel device (#13). The Zyxel
enterprise OID, a Zyxel OUI and "zyxel" on the web page fit every Zyxel switch,
firewall or NAS, and together they were this driver's whole maximum score. Discovery
now also fetches
/getRSAPublickKeyon ports 80 and 443 (the key exchange the driver logs in with, answered without a login), and its"RSAPublicKey"answer weighs 24. Vendor-wide evidence alone comes to 28 of 52, below "high"; a gateway with SNMP scores 52 of 52, one without SNMP 37 of 52. - Every HTTP request to the gateway carries the driver's
timeout. It was set on the session, where requests ignores it, so an unresponsive gateway could hang a call indefinitely (#3). ping()no longer reports every target as alive. The DAL only acknowledges aPINGTESTrequest and never says whether the target answered, soping()now returns an error and the driver opts out of ping sweeps (SUPPORTS_PING = False): a LAN scan through this gateway marked every address alive (#2).
[0.3.0] - 2026-10-23
The first release on PyPI.
Changed
- The driver follows the NAPALM driver standard
(https://git.netork.io/NAPALM/driver-standard): CI on Gitea runs ruff, mypy, the
tests on Python 3.10–3.13 and at the lowest declared versions, bandit, pip-audit and
a build check, and a release tag publishes to PyPI. The package now ships
py.typed, a README and a LICENSE file. Python 3.9 is no longer supported; napalm-device-types never ran on it. It needs napalm-device-types 4.21.1 or later. - A failed login keeps the underlying error as the cause of the
ConnectionException.