get_snmp_information (tplink_jetstream.py:1463) parses show snmp community by taking the first word of every row after the dashes (comm_name = parts[0]), and its mode check reads parts[1]. A table recorded from a real JetStream switch (swt-l0-2-15, 2026-11-01) starts with an Index column:
Index Name Type MIB-View
----- ---- ---- --------
1 public read-only viewDefault
So get_snmp_information reports the community "1", and its mode check reads the name column instead of the type, so every community comes out read-only.
get_snmp_config had the same bug; PR #13 (branch fix/bugs-2026-11) fixes it with a header-based parser parse_snmp_communities in the new napalm_tplink_jetstream/parsers.py, against this recording as fixture. configure_snmp_agent's check searches the whole output and is unaffected.
The command is sent in three places (lines 1449, 1943, 2025) with three readings of its output; the driver sends show snmp community, the recording used show snmp-server community (presumably an abbreviation of the same keyword — unverified).
Expected
get_snmp_information uses parse_snmp_communities (once PR #13 is merged) and reads the access from the Type column.
Priority: P4 — wrong community name in get_snmp_information; netOrk reads SNMP settings through get_snmp_config.
Found during the bug sweep of 2026-11-01.
## What happens
`get_snmp_information` (`tplink_jetstream.py:1463`) parses `show snmp community` by taking the first word of every row after the dashes (`comm_name = parts[0]`), and its mode check reads `parts[1]`. A table recorded from a real JetStream switch (swt-l0-2-15, 2026-11-01) starts with an Index column:
```
Index Name Type MIB-View
----- ---- ---- --------
1 public read-only viewDefault
```
So `get_snmp_information` reports the community `"1"`, and its mode check reads the name column instead of the type, so every community comes out read-only.
`get_snmp_config` had the same bug; PR #13 (branch `fix/bugs-2026-11`) fixes it with a header-based parser `parse_snmp_communities` in the new `napalm_tplink_jetstream/parsers.py`, against this recording as fixture. `configure_snmp_agent`'s check searches the whole output and is unaffected.
The command is sent in three places (lines 1449, 1943, 2025) with three readings of its output; the driver sends `show snmp community`, the recording used `show snmp-server community` (presumably an abbreviation of the same keyword — unverified).
## Expected
`get_snmp_information` uses `parse_snmp_communities` (once PR #13 is merged) and reads the access from the Type column.
Priority: P4 — wrong community name in `get_snmp_information`; netOrk reads SNMP settings through `get_snmp_config`.
Found during the bug sweep of 2026-11-01.
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.
What happens
get_snmp_information(tplink_jetstream.py:1463) parsesshow snmp communityby taking the first word of every row after the dashes (comm_name = parts[0]), and its mode check readsparts[1]. A table recorded from a real JetStream switch (swt-l0-2-15, 2026-11-01) starts with an Index column:So
get_snmp_informationreports the community"1", and its mode check reads the name column instead of the type, so every community comes out read-only.get_snmp_confighad the same bug; PR #13 (branchfix/bugs-2026-11) fixes it with a header-based parserparse_snmp_communitiesin the newnapalm_tplink_jetstream/parsers.py, against this recording as fixture.configure_snmp_agent's check searches the whole output and is unaffected.The command is sent in three places (lines 1449, 1943, 2025) with three readings of its output; the driver sends
show snmp community, the recording usedshow snmp-server community(presumably an abbreviation of the same keyword — unverified).Expected
get_snmp_informationusesparse_snmp_communities(once PR #13 is merged) and reads the access from the Type column.Priority: P4 — wrong community name in
get_snmp_information; netOrk reads SNMP settings throughget_snmp_config.Found during the bug sweep of 2026-11-01.