Ticket #16826 (closed defect: fixed)

Opened 5 years ago

Last modified 5 years ago

Wrong host-only netmask in Windows 10

Reported by: rui.godinho.lopes Owned by:
Component: network/hostif Version: VirtualBox 5.1.22
Keywords: windows netmask hostonly Cc:
Guest type: other Host type: Windows


host-only interfaces are being created with the wrong netmask. You can reproduce the problem by following the next steps.

Create a host-only interface:

    VBoxManage hostonlyif create
Interface 'VirtualBox Host-Only Ethernet Adapter #7' was successfully created

Assign it an IP and netmask:

    VBoxManage hostonlyif ipconfig "VirtualBox Host-Only Ethernet Adapter #7" --ip --netmask

List host-only interfaces:

    VBoxManage list hostonlyifs
Name:            VirtualBox Host-Only Ethernet Adapter #7
GUID:            4028bf58-b908-47e1-a96a-0b2b9a0f6321
DHCP:            Disabled
IPV6Address:     fe80:0000:0000:0000:c5ba:3657:c0a8:df00
IPV6NetworkMaskPrefixLength: 64
HardwareAddress: 0a:00:27:00:00:03
MediumType:      Ethernet
Status:          Up
VBoxNetworkName: HostInterfaceNetworking-VirtualBox Host-Only Ethernet Adapter #7

NB as you can see, NetworkMask is incorrectly returned as instead of

List the interface through Windows:

    netsh interface ip show addresses "VirtualBox Host-Only Network #7"
Configuration for interface "VirtualBox Host-Only Network #7"
    DHCP enabled:                         No
    IP Address:                 
    Subnet Prefix:               (mask
    InterfaceMetric:                      25

NB as you can see, the network interface in Windows is correctly configured as

Change History

comment:1 follow-up: ↓ 2 Changed 5 years ago by frank

Thanks for this report. Actually the netmask was correctly set to the host-only adapter but when fetching the netmask back from the adapter, the prefix length was incorrectly converted to a netmask. Only Windows hosts affected. The most recent 5.1 Windows test build (>= 116114) has the fix.

comment:2 in reply to: ↑ 1 Changed 5 years ago by socratis

Replying to frank:

The most recent 5.1 Windows test build (>= 116114) has the fix.

The test builds go only up to 116111. Is that a future promise? :D

comment:3 Changed 5 years ago by frank

Of course :) New 5.1 Windows build now available.

comment:4 Changed 5 years ago by frank

  • Status changed from new to closed
  • Resolution set to fixed

Fix is part of 5.1.24.

Note: See TracTickets for help on using tickets.
ContactPrivacy policyTerms of Use