Skip to content

Select the routed interface in the discovery wizard - #52

Merged
jacobyoby merged 3 commits into
mainfrom
fix/issue-15-interface-selection
Sep 9, 2026
Merged

jacobyoby merged 3 commits into
mainfrom
fix/issue-15-interface-selection

Conversation

@jacobyoby

Copy link
Copy Markdown
Owner

The wizard previously scanned the first IPv4 address returned by the operating system while displaying the gateway from a separate default-route lookup. With VPNs, bridges, or multiple adapters, those values could describe different networks.

This change retains interface names and indexes across Windows, macOS, and Linux discovery. It selects the interface attached to the active default route, supports an explicit -InterfaceName name or numeric index, and stops with an actionable error when multiple adapters cannot be resolved safely. An explicitly selected non-default Unix interface does not inherit an unrelated gateway.

Fixture tests cover Windows route-index selection, macOS and Linux parsing, explicit selection, missing routes, and unavailable selectors. The README documents the override.

Validation: git diff --check passed. This branch was rebased onto current main after #23 merged. GitHub Actions provides three-OS Pester and analyzer validation.

Closes #15

Bound reverse DNS during wizard discovery
@jacobyoby
jacobyoby merged commit 58aa686 into main Sep 9, 2026
@jacobyoby
jacobyoby deleted the fix/issue-15-interface-selection branch September 9, 2026 02:51
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.

P1: Select the scan interface from the default route and allow explicit selection

1 participant