Changes between Version 1 and Version 2 of Ticket #15060, comment 31
- Timestamp:
- Sep 29, 2022 8:49:11 AM (20 months ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
Ticket #15060, comment 31
v1 v2 5 5 ''I can use bridged networking for the first time in 7 years! '' 6 6 7 Leaving this open because I think VirtualBox shouldn't be trawling around inside the completely undocumented {{{HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\NetworkSetup2\Interfaces}}} to discover available network interfaces (and getting the wrong data when duplicate interfaces with the same description are present).7 ~~Leaving this open because I think !VirtualBox shouldn't be trawling around inside the completely undocumented {{{HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\NetworkSetup2\Interfaces}}} to discover available network interfaces (and getting the wrong data when duplicate interfaces with the same description are present)~~. 8 8 9 VirtualBox should fetch information about available interfaces using the normal APIs as used by e.g., `Get-NetAdapter`.9 !VirtualBox uses INetCfg <https://learn.microsoft.com/en-us/previous-versions/windows/hardware/network/ff547694(v=vs.85)> to enumerate network interfaces which, I guess, is trawling through {{{HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\NetworkSetup2\Interfaces}}}. In doing so, ¬VirtualBox needs account for fact that the interface description is //not// unique across the interfaces returned by INetCfg. 10 10 11 11 And a **hearty curse** at Windows for keeping the crucial registry key that would have let me solve this problem years ago locked away in a way that prevents administrators from even reading it. God, I wish I could bill Microsoft for the many hours of my life that they have wasted.
