Skip to content

fix: accept IPv6 TargetIP in Invoke-SnmpWalk - #82

Closed
slsgzs-cloud wants to merge 1 commit into
jacobyoby:mainfrom
slsgzs-cloud:main
Closed

slsgzs-cloud wants to merge 1 commit into
jacobyoby:mainfrom
slsgzs-cloud:main

Conversation

@slsgzs-cloud

Copy link
Copy Markdown

Fixes #73 - Invoke-SnmpWalk TargetIP ValidateScript only accepted IPv4 and hostnames, blocking dual-stack SNMP targets.

Changed to use [System.Net.IPAddress]::TryParse() for IPv4+IPv6, with hostname fallback for FQDN.

@jacobyoby

Copy link
Copy Markdown
Owner

Already shipped on main via #78 (908af220, closes #73). This fork PR is a duplicate (head slsgzs-cloud:main). Closing rather than rebasing a contributor main.

@jacobyoby

Copy link
Copy Markdown
Owner

Duplicate of merged #78 — no rebase.

@jacobyoby jacobyoby closed this Sep 13, 2026
@jacobyoby

Copy link
Copy Markdown
Owner

Closing as duplicate / already on main.

Issue #73 was fixed and merged in #78 (fix(snmp): accept IPv6 TargetIP on Invoke-SnmpWalk). Current main (4b2beb00 / 1.4.0) already has [System.Net.IPAddress]::TryParse for IPv4+IPv6 TargetIP plus Pester coverage.

This fork PR is DIRTY because it rebases against a pre-#78 tree and would conflict with the shipped fix. Prefer close over rebase (dirty-PR playbook).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Invoke-SnmpWalk: accept IPv6 TargetIP

2 participants