Skip to content

Wizard + Invoke-NetworkDiscovery: IPv6 / dual-stack scan follow-on #61

Closed

Description

@jacobyoby

Context

#57 dual-stacked subnet matching and ARP, but the discovery UX remains IPv4-only:

  • examples/New-NetworkDiagram.ps1 selects only IPv4 interfaces / default routes, parses inet (not inet6), and enumerates hosts with UInt32 IPv4 math.
  • Invoke-NetworkDiscovery requires an IPv4 CIDR via ConvertTo-NormalizedIPv4Cidr and the same UInt32 host enumeration.

On dual-stack or v6-preferred LANs the wizard still draws an IPv4-only picture even though the module can parent v6 nodes.

What

Ship a bounded dual-stack discovery follow-on:

  1. Interface selection: Prefer the active default route’s interface; support IPv6 (and dual) address selection with -InterfaceName still overriding.
  2. Scan targets: For IPv4 keep current Quick/Medium/Full + /22 cap. For IPv6, do not attempt to sweep a /64 — instead use neighbor discovery sources (local ND/ARP table via Get-LocalARPTable) plus optional explicit -Cidr for small prefixes (document a hard cap, e.g. ≤ /120 or a max host count).
  3. Invoke-NetworkDiscovery: Either reject oversized v6 CIDRs with a clear error pointing at ARP-assisted discovery, or implement the same capped strategy.
  4. Wizard inventory write-out must remain importable once Import-Inventory accepts v6 (coordinate / depend on that issue).

Why it matters

Without discovery, #57 only helps hand-authored or ARP-fed topologies. The advertised quick-start path never surfaces v6 hosts.

Acceptance criteria

  • Documented behavior for v6: what is scanned, what is capped, and when ARP/ND is used instead of CIDR sweep.
  • Wizard on a dual-stack fixture path can include at least one IPv6 neighbor from the local neighbor table in the topology/inventory.
  • Invoke-NetworkDiscovery -Cidr with a huge v6 prefix fails with an actionable message (no multi-minute hang).
  • Existing IPv4 wizard/discovery Pester cases still pass.
  • README quick-start notes dual-stack limitations and the new flags/behavior.

Related

Follows #57 / #40. Depends on or stacks after Import-Inventory dual-stack support. Builds on #15 interface selection and #16 DNS timeout.

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

Metadata

Metadata

Assignees

No one assigned

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions