python-netgear-switch-library 0.0.post359__tar.gz → 0.0.post361__tar.gz

{python_netgear_switch_library-0.0.post359 → python_netgear_switch_library-0.0.post361}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: python-netgear-switch-library
-Version: 0.0.post359
+Version: 0.0.post361
 Summary: Python library and CLI to query and control Netgear switches over SNMP, NSDP and HTTP.
 Author-email: Tim Ansell <me@mith.ro>
 License-Expression: Apache-2.0

{python_netgear_switch_library-0.0.post359 → python_netgear_switch_library-0.0.post361}/docs/superpowers/specs/2026-08-02-snmp-surface-findings.md

@@ -483,3 +483,68 @@ That is enough to implement `_xui_vlan_create`/`_xui_vlan_delete` against
 existing `submit_flag`. It still needs driving against a switch with a throwaway
 VLAN id and reading back before `reads_verified`-style confidence is claimed —
 but the mechanism is no longer inferred.
+
+
+### The ADD button is client-side; APPLY carries the new row
+
+Posting `v_6_1_1=ADD` to `/vlanConfiguration.html/a1` (with the page's tokens
+and nav) returns **12 bytes** — not a form. So `ADD` is a JavaScript action that
+reveals an input row in the table the browser already has; it is not a server
+round trip and it creates nothing.
+
+Section 6 is the page-button block (the page's own comment marks it
+`page_buttons_end`):
+
+| Field | Value |
+|---|---|
+| `v_6_1_1` | `ADD` |
+| `v_6_1_2` | `DELETE` |
+| `v_6_1_3` | `CANCEL` |
+| `v_6_1_4`, `v_6_1_5` | `APPLY` |
+
+The display table is 14 rows addressed `1.<row0>.14.v_2_1_<col>`, all hidden
+inputs, with columns 1=id, 2=name, 3=type and 4=RowStatus.
+
+So the create flow is a SINGLE post: the new row's cells plus an APPLY button,
+with the action cell carrying `createAndGo(4)` — and delete is the same shape
+with `destroy(6)`. It is NOT the two-step ADD-then-APPLY a browser appears to
+perform.
+
+Also captured: `page.action` is `/vlanConfiguration.html/a1`, `page.tokens` is
+empty for this page, and `page.nav` is
+`{v_1_1_1: Disable, v_4_1_1: 4093, v_4_2_1: Descending}` — the nav block that
+`xui_row_apply_form` already knows to send.
+
+**Still unresolved:** the row index a new row must use. Existing rows occupy
+`1.0.14` .. `1.13.14`; whether a create uses `1.14.14` (next free), a fixed
+sentinel, or re-uses index 0 has not been established, and getting it wrong
+would edit an existing VLAN rather than add one. That is the single remaining
+unknown, and it is readable from `xui_common.js`'s row-add handler.
+
+
+### Next action: capture the real POST with a browser
+
+`xui_common.js` (18027 bytes) is generic framework — it drives `submit_flag`
+and the `xeData` attribute maps but contains no row-add handler.
+`_xe_vlanConfiguration.js` only declares column attributes (column 1 carries
+`"mandate"`, i.e. the VLAN id is required). Neither states the index a new row
+takes, and further reading of the framework is poor value.
+
+The definitive answer is one browser capture: load `/vlanConfiguration.html`
+with Playwright, click ADD, enter a throwaway VLAN id from the reserved
+4001-4008 range, click APPLY, and record the actual request body. That yields
+the exact field names and row index the firmware expects, rather than any
+inference — and it is the same technique that cracked the M4300's read-page
+URLs when static analysis dead-ended.
+
+This IS a real create, so it runs under the project's live-hardware rules:
+throwaway id only, record the prior VLAN set, delete afterwards, and prove the
+restore by re-reading. Those rules exist precisely to sanction this kind of
+measurement, and creating VLAN 4007 on a switch that already carries 14 VLANs
+is the least invasive write in this whole area.
+
+Once that body is captured, `_xui_vlan_create`/`_xui_vlan_delete` are a small
+addition next to `_xui_poe_admin`, the `_CSRF_HTTP_WRITES` entry comes out of
+`capabilities.py`, and the xfail in `test_write_outcomes.py` should flip to
+passing — at which point HTTP VLAN creation works on all four FASTPATH models
+and the support table can say so truthfully.

{python_netgear_switch_library-0.0.post359 → python_netgear_switch_library-0.0.post361}/src/netgear_switch/_version.py

@@ -18,7 +18,7 @@ version_tuple: tuple[int | str, ...]
 commit_id: str | None
 __commit_id__: str | None
 
-__version__ = version = '0.0.post359'
-__version_tuple__ = version_tuple = (0, 0, 'post359')
+__version__ = version = '0.0.post361'
+__version_tuple__ = version_tuple = (0, 0, 'post361')
 
 __commit_id__ = commit_id = None