Changes between Version 1 and Version 2 of Ticket #15060, comment 27
- Timestamp:
- Sep 28, 2022 6:04:21 PM (19 months ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
Ticket #15060, comment 27
v1 v2 10 10 }}} 11 11 12 It appears VirtualBox is trying to attach to ` {\DEVICE\{CA0A5FEA-99B8-4F54-89CC-C3F81004A5FF}` and this interface can't be found.12 It appears VirtualBox is trying to attach to `\DEVICE\{CA0A5FEA-99B8-4F54-89CC-C3F81004A5FF}` and this interface can't be found. 13 13 14 In the VM settings, the list of adapters that VirtualBox presents for bridging too appears to be based off the `InterfaceDescription` property:14 The correct GUID for my network adapter is: 15 15 16 16 {{{ 17 PS C:\> Get-NetAdapter17 PS C:\> get-netadapter | select name,interfacedescription,interfaceguid 18 18 19 Name InterfaceDescription ifIndex Status MacAddress LinkSpeed20 ---- -------------------- ------- ------ -------------------21 Local Area Connection 2 Realtek PCIe GBE Family Controller 18 Up 90-E6-BA-XX-XX-XX 1 Gbps19 name interfacedescription interfaceguid 20 ---- -------------------- ------------- 21 Local Area Connection 2 Realtek PCIe GBE Family Controller {95A5360B-A4D4-4EFB-9DEE-1C6DEEF029C5} 22 22 }}} 23 23 … … 31 31 || ifDescr || Realtek PCIe GBE Family Controller || 32 32 33 Note that the `ifAlias` does _not_ match the `Name` property from `Get-NetAdapter`, above.34 35 33 There is another cousin key, `HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\NetworkSetup2\Interfaces\{95A5360B-A4D4-4EFB-9DEE-1C6DEEF029C5}\Kernel`; its values are: 36 34 … … 38 36 || ifDescr || Realtek PCIe GBE Family Controller || 39 37 40 Note that the `ifAlias` of this key _does_ match the `Name` property of `Get-NetAdapter`.38 Based on the above, I believe VirtualBox is searching for the `Realtek PCIe GBE Family Controller` interface and finding & trying to attach to `\DEVICE\{CA0A5FEA-99B8-4F54-89CC-C3F81004A5FF}`, which does not exist on my system, resulting in the `VERR_INTNET_FLT_IF_NOT_FOUND ` error. 41 39 42 Based on the above, I believe VirtualBox is searching for the `Realtek PCIe GBE Family Controller` interface and finding & trying to attach to `{CA0A5FEA-99B8-4F54-89CC-C3F81004A5FF}`, which does not exist on my system, resulting in the `VERR_INTNET_FLT_IF_NOT_FOUND ` error.40 VirtualBox should be be finding `\DEVICE\{95A5360B-A4D4-4EFB-9DEE-1C6DEEF029C5}`, which does exist on my system. 43 41 44 VirtualBox should be be finding `{95A5360B-A4D4-4EFB-9DEE-1C6DEEF029C5}`, which does exist on my system. 45 46 I think VirtualBox needs to account for the possibility of multiple interfaces with the same `ifAlias`. Rather than presenting/storing/searching for the interface by its description, it should probably be using the interface name, which is unique. Of course, that will break everyone's VM configurations. Alternatively, VirtualBox could not stop searching after the first interface description match, and continue on, trying to attach to each matching interface until one of the attachments is successful. 42 I think VirtualBox needs to account for the possibility of multiple interfaces with the same alias. Rather than presenting/storing/searching for the interface by its description, it should probably be using the interface name, which is unique. Of course, that will break everyone's VM configurations. Alternatively, VirtualBox could not stop searching after the first interface description match, and continue on, trying to attach to each matching interface until one of the attachments is successful. 47 43 48 44 But those are code changes, which I don't want to hold my breath for.
