﻿ticket,summary,version,host,created,modified,_changetime,_description,_reporter
21280,Host Only Network Blocked by VPN,VirtualBox-7.0.2,Mac OS X,2022-11-18T07:19:19Z,2022-12-20T01:56:08Z,2022-12-20T01:56:08Z,"Many VPNs, such as Palo Alto GlobalConnect, mask routes in order to avoid split networks. This breaks Host-only Networks on virtual machines.

Once the VPN is connected all of the bridge interfaces used to dynamically mange Host-only Networks are routed through the VPN instead of locally to the virtual machines.

Prior to VirtualBox 7, Host-only Adapters were available, which worked consistently even when a VPN had locked the route table.

Here is an example of what GlobalProtect does to the route tables on Windwos and macOS to avoid split networks.

https://knowledgebase.paloaltonetworks.com/kCSArticleDetail?id=kA10g000000ClTm

This is particularly troublesome for macOS users because upgrading to Ventura (macOS 13) breaks VirtualBox 6.x, so an upgrade to VirtualBox 7 is required.",chuckwolber
19502,VM cannot start if network adapter has a trailing space(s) in FriendlyName,VirtualBox 6.1.6,Windows,2020-04-16T22:51:34Z,2020-04-16T22:51:34Z,2020-04-16T22:51:34Z,"For some reasons my VM's with all kind of guest OS (Ubuntu, Windows, FreeBSD) suddenly refused to start with error ""Cannot start a VM because Network adapter <...> not found. You can shutdown or ..."". Name of adapter in dropdown list matched those in Windows network adapter properties.[[BR]]

After digging in debug logs I mentioned this -[[BR]]
 
@log Vbox.log.2:[[BR]]
============================[[BR]]
00:00:16.458034 AssertLogRel F:\tinderbox\win-rel\src\VBox\Main\src-client\ConsoleImpl2.cpp(5274) int cdecl Console::i_configNetwork(const char *,unsigned int,unsigned int,struct INetworkAdapter *,struct CFGMNODE *,struct CFGMNODE *,struct CFGMNODE *,bool,bool): <NULL>[[BR]]
00:00:16.458076 NetworkAttachmentType_Bridged: FindByName failed, rc=E_INVALIDARG (0x80070057)VMSetError: F:\tinderbox\win-rel\src\VBox\Main\src-client\ConsoleImpl2.cpp(5275) int cdecl Console::i_configNetwork(const char *,unsigned int,unsigned int,struct INetworkAdapter *,struct CFGMNODE *,struct CFGMNODE *,struct CFGMNODE *,bool,bool); rc=VERR_INTERNAL_ERROR[[BR]]
00:00:16.458174 VMSetError: Nonexistent host networking interface, name ''''NVIDIA nForce 10/100 Mbps Ethernet''''[[BR]]
00:00:16.459027 Constructor failed with rc=VERR_INTERNAL_ERROR pfnCFGMConstructor=000007fef02e0b00[[BR]]
00:00:16.459846 ERROR [COM]: aRC=E_FAIL (0x80004005) aIID={872da645-4a9b-1727-bee2-5585105b9eed} aComponent={ConsoleWrap} aText={Nonexistent host networking interface, name 'NVIDIA nForce 10/100 Mbps Ethernet' (VERR_INTERNAL_ERROR)}, preserve=false aResultDetail=-225[[BR]]
00:00:16.460104 Console: Machine state changed to 'PoweredOff'[[BR]]
=============================[[BR]]
@Vbox.log[[BR]]
00:00:03.619271 [/Devices/e1000/1/LUN#0/Config/] (level 5)[[BR]]
00:00:03.619273   IfPolicyPromisc      <string>  = ""deny"" (cb=5)[[BR]]
00:00:03.619274   IgnoreConnectFailure <integer> = 0x0000000000000000 (0)[[BR]]
00:00:03.619275   Network              <string>  = '''""HostInterfaceNetworking-NVIDIA nForce 10/100 Mbps Ethernet ""''' (cb=60)[[BR]]
00:00:03.619276   Trunk                <string>  = ""\DEVICE\{77FEAE02-6B93-4633-B53D-9B670059780A}"" (cb=47)[[BR]]
00:00:03.619277   TrunkType            <integer> = 0x0000000000000003 (3)[[BR]]
=============================[[BR]]
Registry key at[[BR]]
""\\\Registry\HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Enum\PCI\VEN_10DE&DEV_03EF&SUBSYS_03EF1849&REV_A2\3&267a616a&0&38\FriendlyName"" was '''""NVIDIA nForce 10/100 Mbps Ethernet ""'''[[BR]]
=============================[[BR]]
So I suggest that somewhere in VBox's code trailing (and maybe leading) spaces in  the adapter's name are trimmed, causing further mismatch.[[BR]]
After I changed registry key (deleted trailing space character) all my VM's started perfectly, as before.

",Dyno_bel
20879,Error creating a new Host Network Manager,VirtualBox 6.1.32,Windows,2022-03-24T11:15:50Z,2022-08-06T09:35:15Z,2022-08-06T09:35:15Z,"When I try to create a new Host Network Manager I receive this error:

Assertion failed: [!aInterfaceName.isEmpty()] at 'F:\tinderbox\win-6.1\src\VBox\Main\src-server\HostNetworkInterfaceImpl.cpp' (76) in long __cdecl HostNetworkInterface::init(class com::Utf8Str,class com::Utf8Str,class com::Guid,enum __MIDL___MIDL_itf_VirtualBox_0000_0000_0046).
Please contact the product vendor!.

I am running a 6.1.3 version on a Windows 11 Microsoft Surface Laptop.",mestebanpt
20983,Will crash everytime after WIFI router rebooted.,VirtualBox 6.1.32,Windows,2022-06-13T20:29:27Z,2022-06-13T20:29:27Z,2022-06-13T20:29:27Z,"VBOX will always crash and exit with ""Application Error"" after WIFI router rebooted, don't know why still, hope you can fix it soon, thanks.",gvvice
20829,cannot assign static IP in host only adapter - other than 192.168.56.0/21,VirtualBox 6.1.32,other,2022-02-16T12:05:22Z,2022-02-16T16:20:47Z,2022-02-16T16:20:47Z,"I'm trying to use my old vboxnetX adapters with my custom IPs, but for the last releases I cannot. Interfaces are starting but with no IPs

Fedora 35 / VirtualBox-6.1-6.1.32_149290_fedora33-1.x86_64

# VBoxManage hostonlyif create 
0%...10%...20%...30%...40%...50%...60%...70%...80%...90%...100%
Interface 'vboxnet0' was successfully created

# VBoxManage hostonlyif ipconfig vboxnet0 --ip 10.88.88.1 --netmask 255.255.255.0
VBoxManage: error: Code E_ACCESSDENIED (0x80070005) - Access denied (extended info not available)
VBoxManage: error: Context: ""EnableStaticIPConfig(Bstr(pszIp).raw(), Bstr(pszNetmask).raw())"" at line 242 of file VBoxManageHostonly.cpp

in log I get:

00:00:00.154243 nspr-2   NetIfAdpCtl: failed to create process for /usr/lib/virtualbox/VBoxNetAdpCtl: iStats=38 enmReason=1
00:00:00.154256 nspr-2   Failed to EnableStaticIpConfig with rc=VERR_ACCESS_DENIED

# strace /usr/lib/virtualbox/VBoxNetAdpCtl vboxnet0 10.88.88.1 netmask 255.255.255.0
...
stat(""/sbin/ip"", {st_mode=S_IFREG|0755, st_size=719208, ...}) = 0
openat(AT_FDCWD, ""/etc/vbox/networks.conf"", O_RDONLY) = 3
newfstatat(3, """", {st_mode=S_IFREG|0644, st_size=28, ...}, AT_EMPTY_PATH) = 0
read(3, ""10.88.88.0/24\n10.88.89.0/24\n"", 4096) = 28
read(3, """", 4096)                       = 0
close(3)                                = 0
write(2, ""Error: permission denied\n"", 25Error: permission denied

cat /etc/vbox/networks.conf 
10.88.88.0/24
10.88.89.0/24

ls -ld /etc/vbox/networks.conf 
-rw-r--r-- 1 root root 28 Feb 16 13:46 /etc/vbox/networks.conf

all commands are as root

If I manually edit VirtualBox.xml and add the ips (this was my config until I removed the adapters to try from scratch)

# VBoxManage list hostonlyifs 

Name:            vboxnet0
GUID:            786f6276-656e-4074-8000-0a0027000000
DHCP:            Disabled
IPAddress:       10.88.88.1
NetworkMask:     255.255.255.0
IPV6Address:     
IPV6NetworkMaskPrefixLength: 0
HardwareAddress: 0a:00:27:00:00:00
MediumType:      Ethernet
Wireless:        No
Status:          Down
VBoxNetworkName: HostInterfaceNetworking-vboxnet0

Name:            vboxnet1
GUID:            786f6276-656e-4174-8000-0a0027000001
DHCP:            Disabled
IPAddress:       10.88.89.1
NetworkMask:     255.255.255.0
IPV6Address:     
IPV6NetworkMaskPrefixLength: 0
HardwareAddress: 0a:00:27:00:00:01
MediumType:      Ethernet
Wireless:        No
Status:          Down
VBoxNetworkName: HostInterfaceNetworking-vboxnet1

When I start VirtualBox I get in logs:
00:00:00.122927 nspr-2   failed to create vboxnet0, error (0xffffffff)
00:00:00.126670 nspr-2   failed to create vboxnet1, error (0xffffffff)

and upon starting a VM:

00:00:53.167974 nspr-2   NetIfAdpCtl: failed to create process for /usr/lib/virtualbox/VBoxNetAdpCtl: iStats=38 enmReason=1
00:00:53.168021 nspr-2   Failed to EnableStaticIpConfig with rc=VERR_ACCESS_DENIED

ifconfig vboxnet0

vboxnet0: flags=4098<BROADCAST,MULTICAST>  mtu 1500
        ether 0a:00:27:00:00:00  txqueuelen 1000  (Ethernet)
        RX packets 0  bytes 0 (0.0 B)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 0  bytes 0 (0.0 B)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0
",bilias
20790,vboxnetx adapters are having a wrong broadcast address,VirtualBox 6.1.32,Linux,2022-01-24T18:22:39Z,2022-02-01T13:11:49Z,2022-02-01T13:11:49Z,"If I create a hostonly adapter (e.g. vboxnet2) having the following IPV4 parameters:

Address: 10.10.10.1
Netmask: '''255.255.252.0'''

I expect the following result in my host:
# ip addr
6: vboxnet2: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP group default qlen 1000
    link/ether 0a:00:27:00:00:02 brd ff:ff:ff:ff:ff:ff
    inet 10.10.10.1/22 '''brd 10.10.11.255''' scope global vboxnet2

and NOT (see brd value)

6: vboxnet2: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP group default qlen 1000
    link/ether 0a:00:27:00:00:02 brd ff:ff:ff:ff:ff:ff
    inet 10.10.10.1/22 '''brd 10.10.10.255''' scope global vboxnet2

It seems that there is an error creating the broadcast value on the HOST.",gabrymark26
20761,"VirtualBox VM shows 2 pcs of VirtualBox Host-Only Ethernet Adapter, but there is only one",VirtualBox 6.1.30,Windows,2022-01-06T14:01:18Z,2022-01-06T14:01:18Z,2022-01-06T14:01:18Z,"As described here: https://forums.virtualbox.org/viewtopic.php?f=6&t=104892&start=15

Currently, i saw that issue on v6.1.97 (testing with TPM support), but i also saw it months ago on older release versions",jmar83
20650,host-only network is not working on windows 10 pro with 6.1.28,VirtualBox 6.1.28,Windows,2021-11-05T15:24:45Z,2022-01-19T11:11:01Z,2022-01-19T11:11:01Z,"I have upgraded the virtualbox to 6.1.28, and host-only network is not working.

on the gui of host-only network manager, there is only an empty list, and can't add an adapter. I also try to add an adapter by command line, but get exception as the following:

Progress state: E_FAIL
VBoxManage.exe: error: Failed to create the host-only adapter
VBoxManage.exe: error: Querying NetCfgInstanceId failed (0x00000002)
VBoxManage.exe: error: Details: code E_FAIL (0x80004005), component HostNetworkInterfaceWrap, interface IHostNetworkInterface
VBoxManage.exe: error: Context: ""enum RTEXITCODE __cdecl handleCreate(struct HandlerArg *)"" at line 95 of file VBoxManageHostonly.cpp

could you help to solve this problem??",kklin
20538,Virtualbox 6.1.26 and current 6.1.27 not installable and working on my Windows 11 22249,VirtualBox 6.1.26,Windows,2021-09-08T05:31:33Z,2021-10-01T13:34:12Z,2021-10-01T13:34:12Z,"Possibly related: #20536
Since after well awaited and beloved update to 22249 pre_release, is the error with the Host-Only Adaptor (Filter Error Message). And after deinstall no reinstall possible, sadly no message on rollback, but probably same issue.

After update with existing VM: VirtualBox Host-Only Ethernet Adapter' (VERR_INTNET_FLT_IF_NOT_FOUND).

Could remove and readd adaptor without error message, but no change.

This is, as you all know, very critical, as VMs running in my fixed Windows 11 for production might have a problem now, as Virtual Box not working on the same computer..",Delphi
20382,Unable to create a HostOnly network on Windows 10 NetCfgInstanceId failed,VirtualBox 6.1.22,Windows,2021-05-28T18:29:05Z,2021-11-05T13:24:30Z,2021-11-05T13:24:30Z,"Using the GUI and ctrl+H to show the host network manager, running as administrator in Windows 10 home, I am no longer able to define a HostOnly network. This is the error I receive:

Failed to create a host network interface.

Querying NetCfgInstanceId failed (0x00000002).

Result Code: E_FAIL (0x80004005)
Component: HostNetworkInterfaceWrap
Interface: IHostNetworkInterface {455f8c45-44a0-a470-ba20-27890b96dba9}

Failed to create a host network interface.

Querying NetCfgInstanceId failed (0x00000002).

Result Code: E_FAIL (0x80004005)
Component: HostNetworkInterfaceWrap
Interface: IHostNetworkInterface {455f8c45-44a0-a470-ba20-27890b96dba9}

How can I fix this?
",fjb_saper
20046,Host-Only Adapter not migrated during Windows 10 inplace upgrade,VirtualBox 6.1.16,Windows,2020-11-17T13:20:49Z,2020-11-17T13:20:49Z,2020-11-17T13:20:49Z,during an inplace upgrade of Windows 10 (doesn't matter which version) the VB Host-Only Adapter does not getting migrated (also it doesn't matter which VB version). Logfiles says driver is not supported and is therefore excluded from migration. (see screenshot attached) As consequence the adapter doesn't exist anymore after feature update and also cannot be created with the same IP settings since some keys remain in the registry (which can basically be deleted as a workaround).,csps
19799,Incorrect DHCP lease command output,VirtualBox 6.1.10,Windows,2020-08-07T07:18:51Z,2020-08-07T07:18:51Z,2020-08-07T07:18:51Z,"VirtualBox 6.1.12r139181

Please, take a look at leases file fragment below:

{{{#!xml
<?xml version=""1.0""?>
<Leases version=""1.0"">
  <Lease mac=""08:00:27:6a:51:e9"" id=""010800276a51e9"" network=""0.0.0.0"" state=""acked"">
    <Address value=""192.168.8.254""/>
    <Time issued=""1596783415"" expiration=""600""/>
  </Lease>
  <Lease mac=""08:00:27:6a:51:e9"" network=""0.0.0.0"" state=""acked"">
    <Address value=""192.168.8.252""/>
    <Time issued=""1596783702"" expiration=""600""/>
  </Lease>
}}}

Command output:

{{{#!python
C:\Users\User>""C:/Program Files/Oracle/VirtualBox/VBoxManage.exe"" dhcpserver findlease --interface ""VirtualBox Host-Only Ethernet Adapter"" --mac-address 0800276A51E9
IP Address:  192.168.8.254
MAC Address: 08:00:27:6a:51:e9
State:       acked
Issued:      2020-08-07T06:56:55Z (1596783415)
Expire:      2020-08-07T07:06:55Z (1596784015)
TTL:         600 sec, currently 10 sec left
}}}

Should return the latest lease, not the first one I assume.

And it didn't return the correct lease even when first one expired:

{{{#!python
C:\Users\user>""C:/Program Files/Oracle/VirtualBox/VBoxManage.exe"" dhcpserver findlease --interface ""VirtualBox Host-Only Ethernet Adapter"" --mac-address 0800276A51E9
IP Address:  192.168.8.254
MAC Address: 08:00:27:6a:51:e9
State:       expired
Issued:      2020-08-07T06:56:55Z (1596783415)
Expire:      2020-08-07T07:06:55Z (1596784015)
TTL:         600 sec, currently 0 sec left
}}}

Expected behaviour: return the last lease for MAC address.",imort
18707,Windows 1903 - Host Only Adapter - VM not starting,VirtualBox 6.0.8,Windows,2019-06-14T08:08:27Z,2019-06-14T08:52:54Z,2019-06-14T08:52:54Z,"Problem with Windows 1903 and latest VirtualBox / Extension Package
VM won't start when a Host-Only Adapter was attached.

Removal and a new fresh install of VirtualBox did not solve this issue.
Under Windows 1809 the VM runs fine but not under 1903 it crashes.

This error occurs also by the newly created machine. Recreating a new Host-Only-Adapter with DHCP enabled don't do the trick, too.

* Version 6.0.8 r130520 (Qt5.6.2)
* Latest Ext Pack installed

Error Message:[[BR]]
{{{
Für die virtuelle Maschine Cacti konnte keine neue Sitzung eröffnet werden.

Failed to open/create the internal network 'HostInterfaceNetworking-
VirtualBox Host-Only Ethernet Adapter' (VERR_INTNET_FLT_IF_NOT_FOUND).

Failed to attach the network LUN (VERR_INTNET_FLT_IF_NOT_FOUND).

Fehlercode:E_FAIL (0x80004005)
Komponente:ConsoleWrap
Interface:IConsole {872da645-4a9b-1727-bee2-5585105b9eed}
}}}

Technical details:
{{{
sc query vboxdrv

SERVICE_NAME: vboxdrv
        TYPE               : 1  KERNEL_DRIVER
        STATE              : 4  RUNNING
                                (STOPPABLE, NOT_PAUSABLE, IGNORES_SHUTDOWN)
        WIN32_EXIT_CODE    : 0  (0x0)
        SERVICE_EXIT_CODE  : 0  (0x0)
        CHECKPOINT         : 0x0
        WAIT_HINT          : 0x0
}}}
",Cookie
18696,Host-only interface does not support IPv6 NDP properly?,VirtualBox 6.0.8,Windows,2019-06-07T17:33:12Z,2019-06-07T17:33:12Z,2019-06-07T17:33:12Z,"I'm having some issues with IPv6 networking via a host-only interface between a Windows 10 1803 host and Arch Linux guest...

Without configuring any additional addresses and just using IPv6 link-local addresses, I'm able to ping the guest intermittently from the host but the reverse does not work at all. It appears the host doesn't respond to neighbor solicitations...

IPv4 on the same interface works fine with the RFC1918 address and ARP...

See the attachments for command line output on both sides. Not included from the Windows side is the firewall rules from Windows Firewall but core stuff is allowed by default and I allowed incoming Echo Requests for ping testing.",vbutilizer
18637,"HostInterfaceNetworking-VirtualBox Host-Only Ethernet Adapter WIn10 host, v6.0",VirtualBox 6.0.6,Windows,2019-05-13T01:05:31Z,2019-06-26T20:47:30Z,2019-06-26T20:47:30Z,"Had VMs working.  Win10 1809 update, then stopped working on all VMs.  Now get ""Failed to open a session for the virtual machine KubuntuVM.

Failed to open/create the internal network 'HostInterfaceNetworking-VirtualBox Host-Only Ethernet Adapter' (VERR_INTNET_FLT_IF_NOT_FOUND).

Result Code: E_FAIL (0x80004005)
Component: ConsoleWrap
Interface: IConsole {872da645-4a9b-1727-bee2-5585105b9eed}""

of course removed existing adapter.  Added a new one.  It was manually configured.  I did have to click Enable box.  And still get this message.",RoryGriffin
18587,Host-Only Adapter reverse to 0.0.0.0,VirtualBox 6.0.6,Windows,2019-04-20T20:15:20Z,2019-04-21T07:18:50Z,2019-04-21T07:18:50Z,"Hello, i was using Host-Only Adapter and when i try to configure adapter, it change back to 0.0.0.0 . I was searching but i only got sites without solution. Any help will be good.",SCr
19140,MacOS / Random network disconnect (Host-only Adapter) - ARP: duplicate use of $IP detected,VirtualBox 6.0.14,Mac OS X,2019-12-09T14:43:26Z,2020-02-10T17:06:35Z,2020-02-10T17:06:35Z,"Hi VirtualBox Use/Admin/Dev,

We are using VirtualBox in my company to launch Alpine Linux for Docker usage. All developers use it for development and the main application in Docker is Apache, MySQL and PHP. (The network is Host-only Adapter)

It's work really fine since several years but since 6 months peoples on MacOS suffer of random network disconnect. That lasts 2 to 3 minutes and it comes back without any intervention ...(This happens between 2 to 6 times over a period of one hour)


{{{
Jeu 14 nov 2019 13:22:40 EST: 64 bytes from 172.21.21.5: icmp_seq=6644 ttl=64 time=0.439 ms
Jeu 14 nov 2019 13:22:41 EST: 64 bytes from 172.21.21.5: icmp_seq=6645 ttl=64 time=0.296 ms
Jeu 14 nov 2019 13:22:42 EST: 64 bytes from 172.21.21.5: icmp_seq=6646 ttl=64 time=0.369 ms
Jeu 14 nov 2019 13:22:44 EST: Request timeout for icmp_seq 6647
[...]
Jeu 14 nov 2019 13:25:07 EST: Request timeout for icmp_seq 6789
Jeu 14 nov 2019 13:25:07 EST: 64 bytes from 172.21.21.5: icmp_seq=6790 ttl=64 time=0.832 ms
Jeu 14 nov 2019 13:25:08 EST: 64 bytes from 172.21.21.5: icmp_seq=6791 ttl=64 time=0.412 ms
}}}

 
First we check on the Guest host:

- Check network/application logs 
- Update OS and packages
- Allocate more memory
-  ....

After we make somes changes on Host:

- Update MacOS from 10.14 to 10.15
- Disable Bluetooth
- ...


Here the Host IP/vboxnet0:
{{{
MacBook-Pro:platform-website turbulent$ ifconfig vboxnet0
vboxnet0: flags=8943<UP,BROADCAST,RUNNING,PROMISC,SIMPLEX,MULTICAST> mtu 1500
	ether 0a:00:27:00:00:00 
	inet 172.21.21.1 netmask 0xffffff00 broadcast 172.21.21.255
}}}


Here the Guest IP/eth1:
{{{
substance@work:~$ ifconfig eth1
eth1      Link encap:Ethernet  HWaddr 08:00:27:DA:BC:C4  
          inet addr:172.21.21.5  Bcast:0.0.0.0  Mask:255.255.255.0
          inet6 addr: fe80::a00:27ff:feda:bcc4/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:96227 errors:0 dropped:0 overruns:0 frame:0
          TX packets:68725 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          RX bytes:9772660 (9.3 MiB)  TX bytes:280592087 (267.5 MiB)
}}}

After when I check on ""Console"" on the Host, I have all time this error on the disconnect: 

{{{
13:22:43.454970 -0500	lsd	LSExceptions shared instance invalidated for timeout.
13:22:43.479991 -0500	kernel	X86PlatformPlugin result 0
13:22:43.479997 -0500	kernel	X86PlatformPlugin result 0
13:22:43.743794 -0500	locationd	{""msg"":""kCLConnectionMessageWatchdog"", ""event"":""activity"", ""this"":""0x7fdcf0c808d0"", ""registrationRequired"":0, ""registrationReceived"":1}
13:22:43.776090 -0500	kernel	vboxnet0 duplicate IP address 172.21.21.1 sent from address 08:00:27:5a:96:1c
}}}

After I installed  Wireshark to inspect the netwok and you can view the ARP package from this MAC:

[[Image(https://cdn.clarenne.name/virtualbox-network.png)]]

I open this ticket because this mac address start with ""08:00:27:5a"" look to be the DHCPServer assignments.

Can you please have a check on this issue ? 
",TB-Quentin
17500,macOS 10.13.3 - Host Only Networking - Host not accessible,VirtualBox 5.2.6,Mac OS X,2018-01-25T23:22:52Z,2020-02-13T04:37:34Z,2020-02-13T04:37:34Z,"After installing macOS update to 10.13.3,  VirtualBox 5.2.6 host only networking started to show an issue never seen before.
VMs on the same hostonly network can communicate, 
while VM-host, in both direction, communication does not happen, every attempted connection times out

Eventually I worked around the issue with a host restart, but every new host-only network created is defective.
This is a big issue for example when using vagrantfiles to create clusters of VMs.

create a vboxnetX hostonly network in the VBox UI, with DHCP enabled
start a simple VM defined to use vboxnetX (eg vanilla ubuntu with DHCP) : host will NOT be reachable from VM, VM will NOT be reachable by host

shut down VM
restart macOS !!!
vboxnetX adapter is now NOT listed by ifconfig (before VB starts)

start VBox (-> vboxnetX created but not assigned an IP)

start the VM previously defined as using the vboxnetX adapter
vboxnetX will be assigned an ip ... and this time VM/host communication works

",Edoardo
17648,Host-Only adapter failed to install on Windows 10 OS,VirtualBox 5.2.6,Windows,2018-03-29T07:20:36Z,2018-03-29T07:20:36Z,2018-03-29T07:20:36Z,"'''[How to reproduce]''' [[BR]][[BR]]
From fresh installation, I had no problem to use host-only network and the host-only adapter was present.[[BR]]
The problem began when I removed my host-only adapters using VirtualBox GUI. I was then not able to re-create it using either the GUI and the command line.

'''[Research]''' [[BR]][[BR]]
I've walk through the VirtualBox forum and Bug tracker before posting and I found a similar issue : [[BR]]
+ https://www.virtualbox.org/ticket/17354 [[BR]]
+ https://forums.virtualbox.org/viewtopic.php?f=6&t=86179 [[BR]]
Here the antivirus was involded and disable it resolved the issue. [[BR]]In my case I've completely uninstall my corporate antivirus + deactivate Windows Defender without success. [[BR]]

'''[Troubleshooting]''' [[BR]][[BR]]
+ Repair VirtualBox [[BR]]
+ Uninstall VirtualBox [[BR]]
+ Remove %userprofile%\.virtualbox [[BR]]
+ Remove drivers in %windir%\System32\drivers [[BR]]
+ Remove registry keys about VirtualBox [[BR]]
+ Install 5.2 VirtualBox [[BR]]
+ Run Installer as Admin right [[BR]]
+ Run a Ccleaner registry cleaning [[BR]]
[[BR]]
With a result always the same, failed to create host-only adapter. [[BR]]

'''[logs]''' [[BR]][[BR]]

VirtualBox Gui logs are showing : [[BR]]
{{{
Failed to create a host network interface.

Querying NetCfgInstanceId failed (0x00000002).

Code d'erreur : E_FAIL (0x80004005)
Composant : HostNetworkInterfaceWrap
Interface : IHostNetworkInterface {455f8c45-44a0-a470-ba20-27890b96dba9}
}}}

C:\Windows\INF\setupapi.dev.log
{{{
>>>  [Configure Driver Package - c:\windows\system32\driverstore\filerepository\vboxnetadp6.inf_amd64_37fe176ed22ac0b0\vboxnetadp6.inf]
>>>  Section start 2018/03/27 18:20:45.493
      cmd: ""C:\Program Files\Oracle\VirtualBox\VBoxSVC.exe"" /Helper VirtualBox\SVCHelper\{a2f92065-56fc-42e5-ada7-359a3774292e}
     sto: Source Filter  = VBoxNetAdp6.ndi
     sto: Target Filter  = ROOT\NET\0002
     inf: Class GUID     = {4d36e972-e325-11ce-bfc1-08002be10318}
     inf: Class Options  = Configurable
!!!  idb: Failed to open driver package object 'vboxnetadp6.inf_amd64_37fe176ed22ac0b0'. Error = 0x00000005
<<<  Section end 2018/03/27 18:20:45.540
<<<  [Exit status: FAILURE(0x00000005)]
}}}

'''[other]'''[[BR]][[BR]]
I remember once clicking [NO] on the UAC pop-up message asking to install host-only driver. Could the issue be trigered by this action?
[[BR]][[BR]]

Thanks for your help.",AlexRoux42
17406,Failed to create a host network interface (windows10),VirtualBox 5.2.4,other,2017-12-28T17:40:59Z,2018-01-19T22:55:01Z,2018-01-19T22:55:01Z,"Feature update to Windows 10, version 1709
i click on file ->Host Network Manager
create+
I get the following error:

Failed to create a host network interface.
Querying NetCfgInstanceId failed (0x00000002).

Result Code: 
E_FAIL (0x80004005)
Component: 
HostNetworkInterfaceWrap
Interface: 
IHostNetworkInterface {455f8c45-44a0-a470-ba20-27890b96dba9}",gdubs
15975,VBoxManage always shows host only interfaces as disabled,VirtualBox 5.1.6,Windows,2016-09-22T22:41:20Z,2017-05-29T14:22:50Z,2017-05-29T14:22:50Z,"VBoxManage list --long hostonlyifs

always shows DHCP disabled, even for an enabled, and functioning NIC.",silvermangb
15970,Failed to create the host-only adapter (Windows 7),VirtualBox 5.1.6,Windows,2016-09-22T13:15:27Z,2017-01-19T21:35:50Z,2017-01-19T21:35:50Z,"I cannot create host-only adapter neither with the command 
{{{
VBoxManage.exe hostonlyif create
}}}
nor from UI. I get error:

{{{
0%...
Progress state: E_FAIL
VBoxManage.exe: error: Failed to create the host-only adapter
VBoxManage.exe: error: Could not operate the communication channel (VERR_BROKEN_PIPE)
VBoxManage.exe: error: Details: code E_FAIL (0x80004005), component VirtualBoxWrap, interface IVirtualBox
VBoxManage.exe: error: Context: ""enum RTEXITCODE __cdecl handleCreate(struct HandlerArg *)"" at line 71 of file VBoxManageHostonly.cpp
}}}

When I try to do it from UI I get error message with the text:
{{{
Failed to create the host network interface.

Could not operate the communication channel (VERR_BROKEN_PIPE).

Result Code: E_FAIL (0x80004005)
Component: VirtualBoxWrap
Interface: IVirtualBox {0169423f-46b4-cde9-91af-1e9d5b6cd945}
}}}

This doesn't allow me to use Docker so it is blocker for me.

It is reproducable with older 5.0.* versions too. I tried to reinstall VirtualBox, install with ""-msiparams NETWORKTYPE=NDIS5"" parameter, reset driver cache in ""windir%\inf\INFCACHE.1"" without any result.

After error there is new ""Unknown Device"" in Windows Device Manager.

Lines added to setupapi.app.log after failure:
{{{
>>>  [Build Driver List - ROOT\NET\0002]
>>>  Section start 2016/09/22 16:00:22.977
      cmd: ""C:\Program Files\Oracle\VirtualBox\VBoxSVC.exe"" /Helper VirtualBox\SVCHelper\{86beac27-6c97-479d-9f92-48857dbe7773}
     cpy: Policy is set to make all digital signatures equal.
!    sig: No installed catalogs matching catalog name '' were found that validated the file.
!    sig: Error 1168: Element not found.
!    sig: Verifying file against specific (valid) catalog failed! (0x800b0109)
!    sig: Error 0x800b0109: A certificate chain processed, but terminated in a root certificate which is not trusted by the trust provider.
!    sig: Verifying file against specific (valid) catalog failed! (0x800b0109)
!    sig: Error 0x800b0109: A certificate chain processed, but terminated in a root certificate which is not trusted by the trust provider.
!    sig: Verifying file against specific (valid) catalog failed! (0x800b0109)
!    sig: Error 0x800b0109: A certificate chain processed, but terminated in a root certificate which is not trusted by the trust provider.
!    sig: Verifying file against specific (valid) catalog failed! (0x800b0109)
!    sig: Error 0x800b0109: A certificate chain processed, but terminated in a root certificate which is not trusted by the trust provider.
!    sig: Verifying file against specific (valid) catalog failed! (0x00000057)
!    sig: Error 87: The parameter is incorrect.
!    sig: Verifying file against specific Authenticode(tm) catalog failed! (0x80092003)
!    sig: Error 0x80092003: An error occurred while reading or writing to a file.
<<<  Section end 2016/09/22 16:00:23.698
<<<  [Exit status: SUCCESS]


>>>  [DIF_REGISTERDEVICE - ROOT\NET\0002]
>>>  Section start 2016/09/22 16:00:23.761
      cmd: ""C:\Program Files\Oracle\VirtualBox\VBoxSVC.exe"" /Helper VirtualBox\SVCHelper\{86beac27-6c97-479d-9f92-48857dbe7773}
<<<  Section end 2016/09/22 16:00:23.763
<<<  [Exit status: SUCCESS]


>>>  [DIF_ALLOW_INSTALL - ROOT\NET\0002]
>>>  Section start 2016/09/22 16:00:23.763
      cmd: ""C:\Program Files\Oracle\VirtualBox\VBoxSVC.exe"" /Helper VirtualBox\SVCHelper\{86beac27-6c97-479d-9f92-48857dbe7773}
<<<  Section end 2016/09/22 16:00:23.765
<<<  [Exit status: SUCCESS (DI_DO_DEFAULT)]


>>>  [DIF_INSTALLDEVICEFILES - ROOT\NET\0002]
>>>  Section start 2016/09/22 16:00:23.765
      cmd: ""C:\Program Files\Oracle\VirtualBox\VBoxSVC.exe"" /Helper VirtualBox\SVCHelper\{86beac27-6c97-479d-9f92-48857dbe7773}
<ins>
}}}

also (which looks weird) some lines are added to section dated 2015/09/23:
{{{
>>>  [DIF_INSTALLDEVICEFILES - ROOT\NET\0002]
>>>  Section start 2015/09/23 20:02:36.865
...
!    sig: Verifying file against specific (valid) catalog failed! (0x800b0109)
!    sig: Error 0x800b0109: A certificate chain processed, but terminated in a root certificate which is not trusted by the trust provider.
     dvi: Committing file queue...
     flq: CopyFile: 'C:\Windows\system32\DRIVERS\VBoxNetAdp.sys'
     flq:       to: 'C:\Windows\Temp\OLD1D54.tmp'
     flq: CopyFile: 'C:\Windows\System32\DriverStore\FileRepository\vboxnetadp.inf_amd64_neutral_978f7ab983bb20bd\VBoxNetAdp.sys'
     flq:       to: 'C:\Windows\system32\DRIVERS\SET1D54.tmp'
     flq: MoveFile: 'C:\Windows\system32\DRIVERS\SET1D54.tmp'
     flq:       to: 'C:\Windows\system32\DRIVERS\VBoxNetAdp.sys'
}}}


Please let me know what information may I provide to help to fix this defect or find some workaround.

OS: Windows 7, 64bit, SP1.

I have Aventail VPN installed but it is inactive when I reproduce the problem. 
",Dron007
15974,python host.create_host_only_network_interface returns bad object,VirtualBox 5.1.6,Windows,2016-09-22T22:21:10Z,2016-09-22T22:46:19Z,2016-09-22T22:46:19Z,"vbmanager = virtualbox.Manager()
vbox      = vbmanager.get_virtualbox()
host      = vbox.host   

hoa,progress = p_host.create_host_only_network_interface()
progress.wait_for_completion(32000)

print hoa.name

The print statement generates an error 

Failed to find attribute name in <virtualbox.library.IHostNetworkInterface object at 0x0000000008FB6898>



However, the interface was created.",silvermangb
15943,Wrong hostonlyif mask,VirtualBox 5.1.6,Windows,2016-09-16T11:14:02Z,2016-09-16T11:14:02Z,2016-09-16T11:14:02Z,"I'm using VirtualBox as a Vagrant provider and when I specify an netmask of 255.255.255.240, the first vagrant up works fine but on subsequent ups a new interface is generated with automatic ip address.

As I explore the source of the issue I find that at vboxmanage list hostonlyifs the interface with the pretended network has a printed netmask of 255.255.255.'''15'''. This is an issue since that in fact, at network interface settings, the actual network mask is the 255.255.255.240.

I'm suspecting that this issue is leading Vagrant to assume that there's no interface for the pretended network and then it creates a new one and setted to the already existing network which cases VirtualBox to change adapter to automatic IP.",nbranco
17354,Can't setup Host-Only Network Adapter on Windows 10 Client,VirtualBox 5.1.30,Windows,2017-12-06T18:20:42Z,2018-10-26T04:03:44Z,2018-10-26T04:03:44Z,"Hi,


'''[How to reproduce it]'''
From fresh installation, installation was ok, no errors, the problem began when I tried to setup the missing IP and network mask for the Host-Only Network Adapter, first thing I noticed is that upon setting up the values VBox was resetting the values every time and clean the values up.

-I'm using VirtualBox Version 5.1.30 also tried with 5.2.0 for Windows
-I have Windows 10 Pro running on a Dell Precision, 16GB RAM, 64-bit, core i7 vPro
-I'm trying to host a Linux VM that contains some web application, so I can access them via u.r.l. , this is a RedHat VM

After this I tried a lot of things to make the Host-Only adapter work

- I had 3 VM, I remove 2 of them and test 1 with one
- Remove every single VM and try to set the values
-Try to set the values using TCP/IP v4 properties in the actual Network device on Windows' Network connections
- Uninstall VBox, install a older version (VirtualBox-5.1.30)
- Reinstall VBox using Admin option
- Uninstall VBox, delete completely .VirtualBox folder, reboot the machine, then reinstall VBox as: user and admin
- Delete all the Devices using the GUI and create the device using VBoxManage hostonlyif create

",Diego Resendi
17046,"host only network lost after resuming from sleep (H: win10, G:winserver2012)",VirtualBox 5.1.26,Windows,2017-08-30T23:51:01Z,2017-08-30T23:51:01Z,2017-08-30T23:51:01Z,"Before host goes to sleep, connection works fine. After resuming from sleep, I can no longer ping the guest from the host (""Request timed out""). Occasionally, stoping vbox, resetting the interface on the windows side, then restarting vbox fixes connectivity. In other times, only a full host restart allowed me to recover.

before sleep: 
>netsh i i sh add 9

Configuration for interface ""VirtualBox Host-Only Network #3""
    DHCP enabled:                         No
    IP Address:                           192.168.214.1
    Subnet Prefix:                        192.168.214.0/24 (mask 255.255.255.0)
    InterfaceMetric:                      25

>vboxmanage list hostonlyifs
Name:            VirtualBox Host-Only Ethernet Adapter #3
GUID:            539037ce-b029-4212-858f-1b368320c5e5
DHCP:            Disabled
IPAddress:       192.168.214.1
NetworkMask:     255.255.255.0
IPV6Address:     fe80:0000:0000:0000:4571:268b:9d7d:c79b
IPV6NetworkMaskPrefixLength: 64
HardwareAddress: 0a:00:27:00:00:09
MediumType:      Ethernet
Status:          Up
VBoxNetworkName: HostInterfaceNetworking-VirtualBox Host-Only Ethernet Adapter #3

after resume:
>netsh i i sh add 9

Configuration for interface ""VirtualBox Host-Only Network #3""
    DHCP enabled:                         No
    IP Address:                           169.254.199.155
    Subnet Prefix:                        169.254.0.0/16 (mask 255.255.0.0)
    InterfaceMetric:                      25

(vboxmanage's report is unchanged)",somersby
16857,VBoxNetAdp.kext conflict with tap.kext on macOS,VirtualBox 5.1.22,other,2017-06-27T01:12:07Z,2017-09-28T08:34:20Z,2017-09-28T08:34:20Z,"I have both tuntaposx and virtualbox installed on my macOS 10.12.5
I found I can't access any SMB share from my macOS host to any remote host. After some investigation, I can confirm remove any of these two software will fix the smb access problem.
I posted a topic on vbox forums. [https://forums.virtualbox.org/viewtopic.php?f=8&t=83587]

There's a similar bug report about tuntaposx on [https://sourceforge.net/p/tuntaposx/bugs/25/], but  hasn't mention vbox.

I don't known which side can fix this problem, so I report it here.",yaocl
16925,virtio-net slower than Intel PRO/1000 Desktop,VirtualBox 5.1.22,Windows,2017-07-20T15:07:13Z,2017-07-24T09:32:36Z,2017-07-24T09:32:36Z,"Confirmed on version 5.1.24.

Host: Windows 10[[BR]]
VM: Debian 9 with Guest Additions

Host-only NIC with Intel PRO/1000 Desktop
 * iperf3 
  * Host => VM : 2.68 Gbps
  * Host <= VM : 1.20 Gbps

Host-only NIC with virtio-net
 * iperf3
  * Host => VM : 2.11 Gbps
  * Host <= VM : 0.96 Gbps",cantonese
16833,Installation of 5.x Prevents Host Machine Networking,VirtualBox 5.1.22,Windows,2017-06-16T05:34:38Z,2017-06-22T15:47:40Z,2017-06-22T15:47:40Z,"I've used Virtual box for years, once it moved to 5.x I have not been able to use it due to the summary subject.   The physical machine is an i7 with Win7 x64 all the latest updates.  Contains VirtualPC, VMWare Player and VirtualBox.  The 4.3.40 works fine.  The last time I installed 5.1.22, it uninstalled 4.3.40, installed 5.1.22.  Everything worked fine for a couple days (the computer was left running or sleep mode).   On the reboot, the same thing happens, no networking on the host system, no connecting to domain controller, etc..  If you go to the control panel / network and sharing, it just has a circle hourglass going in circles and says ""Identifying..."" for the Connection: Local Area Connection and Access was ""No Network Access"".  So I went to adapter settings, right clicked on the ""VirtualBox Host-Only Network"" and clicked disable.  As soon as that was disabled, the local area network connected and everything was working again.  This is repeatable, last attempt was back in 2016.  Still a problem today.",dfatvb
16699,"createHostOnlyNetworkInterface() returning iProgress, iProgress instead of iProgress,IHostNetworkInterface",VirtualBox 5.1.20,Windows,2017-04-26T11:16:31Z,2017-04-26T11:16:31Z,2017-04-26T11:16:31Z,"Hello everybody. I'm using Virtualbox 5.1.20 on Windows 10 x64. I'm using the python SDK (version 5.1.20) to bind irtualbox functions via XPCOM. Python version in use is the 2.7 32bit.

PROBLEM:
Function createHostOnlyNetworkInterface() returns iProgress twice instead of returning on iProgress and an IHostNetworkInterface.

Have a look at the attached screenshot, which is pretty eloquent.
",Alberto Geniola
16554,"VirtualBox on Windows 10 leaks hostonlyifs, turning them into bridgedifs which cannot be removed",VirtualBox 5.1.14,Windows,2017-03-12T09:34:39Z,2017-03-12T09:34:39Z,2017-03-12T09:34:39Z,"It has happened twice now on my machine. The first time I lost hostonlyif 1 through 5 after an Vbox upgrade - searched a while for a solution, but gave up and created new ones ""VirtualBox Host-Only Ethernet Adapter #6"" through #12. That was more than 6 months ago.

Last week I noticed that my host only interfaces were gone again. Not sure on which upgrade, but I was on a 5.0 version. Upgraded to the latest, and some cleanup and reboots, and the problem is still there. Did not try an uninstall and reinstall because that didn't help the last time.

The current state is as follows:

I can create and delete host only interfaces, but the starting number is ""VirtualBox Host-Only Ethernet Adapter #13""
""VBoxManage.exe list -l bridgedifs"" returns a list with all my lost host only interfaces - but I cannot find a command to delete the bridged interfaces.
I can find these in the windows registry by searching the GUID, and also by name in Computer/HKEY_LOCAL_MACHINE/SYSTEM/Setup/Upgrade/NetworkDriveBackup/Control/Class but hesitate to mess with the registry manually, because there are too many references to clean up by hand. Searched for a powershell utility that could clean and free them up, but didn't find one.
Looking for help. Partial output of ""VBoxManage.exe list -l bridgedifs"" looks like this - as you can see by the name they used to all be host only ifs:

PS C:\WINDOWS\system32> VBoxManage.exe list -l bridgedifs

Name: VirtualBox Host-Only Ethernet Adapter #8 GUID: ef9a148d-dbbd-4eac-a072-bae5f0aae49b DHCP: Disabled IPAddress: 0.0.0.0 NetworkMask: 0.0.0.0 IPV6Address: IPV6NetworkMaskPrefixLength: 0 HardwareAddress: 00:00:00:00:00:00 MediumType: Ethernet Status: Down VBoxNetworkName: HostInterfaceNetworking-VirtualBox Host-Only Ethernet Adapter #8

Name: VirtualBox Host-Only Ethernet Adapter #3 GUID: 873d770d-328c-4af6-a0e8-900433a03cf6 DHCP: Disabled IPAddress: 0.0.0.0 NetworkMask: 0.0.0.0 IPV6Address: IPV6NetworkMaskPrefixLength: 0 HardwareAddress: 00:00:00:00:00:00 MediumType: Ethernet Status: Down VBoxNetworkName: HostInterfaceNetworking-VirtualBox Host-Only Ethernet Adapter #3

Name: Microsoft Virtual WiFi Miniport Adapter GUID: a35fb3ad-bb85-4bfc-b9c1-05ce81d512cb DHCP: Disabled IPAddress: 0.0.0.0 NetworkMask: 0.0.0.0 IPV6Address: IPV6NetworkMaskPrefixLength: 0 HardwareAddress: 00:00:00:00:00:00 MediumType: Ethernet Status: Down VBoxNetworkName: HostInterfaceNetworking-Microsoft Virtual WiFi Miniport Adapter

Name: VirtualBox Host-Only Ethernet Adapter #10 GUID: 1e88234f-d548-4b03-a2c2-b7c73f1016b1 DHCP: Disabled IPAddress: 0.0.0.0 NetworkMask: 0.0.0.0 IPV6Address: IPV6NetworkMaskPrefixLength: 0 HardwareAddress: 00:00:00:00:00:00 MediumType: Ethernet Status: Down VBoxNetworkName: HostInterfaceNetworking-VirtualBox Host-Only Ethernet Adapter #10

Name: VirtualBox Host-Only Ethernet Adapter #6 GUID: fed303cd-386b-4f60-8419-1c71b53fa90a DHCP: Disabled IPAddress: 0.0.0.0 NetworkMask: 0.0.0.0 IPV6Address: IPV6NetworkMaskPrefixLength: 0 HardwareAddress: 00:00:00:00:00:00 MediumType: Ethernet Status: Down VBoxNetworkName: HostInterfaceNetworking-VirtualBox Host-Only Ethernet Adapter #6

Name: VirtualBox Host-Only Ethernet Adapter #2 GUID: f6d1349b-82f4-4ce2-ae42-e7fb19f7fdf4 DHCP: Disabled IPAddress: 0.0.0.0 NetworkMask: 0.0.0.0 IPV6Address: IPV6NetworkMaskPrefixLength: 0 HardwareAddress: 00:00:00:00:00:00 MediumType: Ethernet Status: Down VBoxNetworkName: HostInterfaceNetworking-VirtualBox Host-Only Ethernet Adapter #2

",rezroo
14676,NDIS6 Network Driver breaking Local Area Connection on Sleep Resume,VirtualBox 5.0.6,Windows,2015-10-06T19:31:42Z,2015-10-07T03:11:35Z,2015-10-07T03:11:35Z,"There appears to be a problem with the NDIS6 driver handling power state changes. 

Since updating to VirtualBox 5.0.x, my Local Area Connection reports ""Network cable unplugged"" after waking up from sleep. 

This issues does NOT occur if i uncheck the VirtualBox NDIS6 Bridged Network Driver on the connection. 

Workaround 1: Disable the Virutalbox VirtualBox NDIS6 Bridged Network Driver on the connection

Workaround 2: disable and re-enable the interface every resume. 
 
Workaround 3: Configure the Network Adapter Hardware power management to disable ""Allow this computer to turn off this device to save power."" 

Disabling power management on the interface not only prevents the issue from occuring, but also returns it to service after a sleep/resume cycle without having to disable and re-enable the interace. 


I think this issues could be related to some other host<->guest networking problems commonly reported which I also run into. 

My Hardware: Dell Precision M4800. Intel Ethernet Connection I217-LM. Driver version 12.12.50.7205. Connected via docking station. 

I'm trying to find a way to get into debugging the driver, but could use some guidance. 
",GabeF
14630,Duplicate host-only Interface name on Windows 10,VirtualBox 5.0.4,Windows,2015-09-24T11:48:15Z,2015-11-20T19:46:16Z,2015-11-20T19:46:16Z,"Hi guys, 

There's an anoying bug on '''Windows 10'''.

When creating host-only interfaces, sometimes, a popup appears saying:
 Cannot rename this connection. A connection with the name you specified already exists. Specify a different name.

This blocks the interface creation.

When clicking the ""OK"" button, VBoxManage resume the operation and create an interface with a name like 'VirtualBox Host-Only Ethernet Adapter #X'
Eventualy, VBoxManage command ends, saying:
 Interface 'VirtualBox Host-Only Ethernet Adapter' was successfully created
'''Notice that it is not the actual name of the interface.'''

To reproduce the issue, just run {{{VBoxManage.exe hostonlyif create}}} a couple of times.

Tested on Windows 10, with VBox 5.0.4 and latest test build (5.0.5)",srats
14631,Host-only interface IP changes on Windows 10,VirtualBox 5.0.4,Windows,2015-09-24T12:50:56Z,2015-09-24T12:50:56Z,2015-09-24T12:50:56Z,"When using host only network interfaces on Windows 10, the interface IP address changes and the interface is not working anymore.



'''Reproduction (easy way)'''
[[BR]][[BR]]
1 - Remove any existing host-only interfaces and dhcp servers.[[BR]]
2 - Run the following commands:[[BR]]
{{{vboxmanage.exe hostonlyif create}}}[[BR]]
Check the assigned IP and netmask and reuse them in the following command:[[BR]]
{{{vboxmanage.exe hostonlyif ipconfig ""VirtualBox Host-Only Ethernet Adapter"" --ip 192.168.56.1 --netmask 255.255.255.0}}}[[BR]]
{{{vboxmanage.exe dhcpserver remove --ifname ""VirtualBox Host-Only Ethernet Adapter""}}}[[BR]]
{{{vboxmanage.exe dhcpserver add --ifname ""VirtualBox Host-Only Ethernet Adapter"" --ip 192.168.56.100 --netmask 255.255.255.0 --lowerip 192.168.56.101 --upperip 192.168.56.254 --enable}}}[[BR]]
Notice that, at this point, the host-only interface appears to be ""Automatically configured"" in VirtualBox parameters (see the tooltip when hovering the interface with the mouse).[[BR]]
3 - Open Windows 10 network settings (Control Panel\Network and Internet\Network Connections)[[BR]]
4 - Notice that the newly created network interfaces uses DHCP configurations instead of manually configured settings.[[BR]]




'''Reproduction (hard way)'''
[[BR]][[BR]]
1 - Remove any existing host-only interfaces and dhcp servers.[[BR]]
2 - Run the following commands:[[BR]]
{{{vboxmanage.exe hostonlyif create}}}[[BR]]
Check the assigned IP and netmask and reuse them in the following command:[[BR]]
{{{vboxmanage.exe hostonlyif ipconfig ""VirtualBox Host-Only Ethernet Adapter"" --ip 192.168.56.1 --netmask 255.255.255.0}}}[[BR]]
{{{vboxmanage.exe dhcpserver remove --ifname ""VirtualBox Host-Only Ethernet Adapter""}}}[[BR]]
{{{vboxmanage.exe dhcpserver add --ifname ""VirtualBox Host-Only Ethernet Adapter"" --ip 192.168.56.100 --netmask 255.255.255.0 --lowerip 192.168.56.101 --upperip 192.168.56.254 --enable}}}[[BR]]
Notice that, at this point, the host-only interface appears to be ""Automatically configured"" in VirtualBox parameters (see the tooltip when hovering the interface with the mouse).[[BR]]
3 - Create a Linux guest (such as Ubuntu 15.04), and attach it's first network adapter to the host-only interface.[[BR]]
4 - Run the guest (I chose to run in live mode to avoid to install the OS). It usually gets the first ip available, 192.168.56.101 in our case[[BR]]
5 - Ping the host interface from the guest: ping 192.168.56.1[[BR]]
6 - Check the host interface IP: it has changed to 192.168.56.102 and the host-only interface does not work anymore.[[BR]]




Tested on VirtualBox 5.0.4 and latest testing 5.0.5.[[BR]]
Tested with Linux guests (Android, Ubuntu).[[BR]]
Reproduce on Windows 10 host.[[BR]]
Can't reproduce on Linux (Ubuntu, Fedora, Debian), Mac OS (10.8, 10.9 and 10.10), Windows 7 and Windows 8.1 hosts.[[BR]]",srats
14582,Hostonlyif not fully initialized after create returns successful,VirtualBox 5.0.4,Windows,2015-09-13T18:31:40Z,2015-09-14T04:14:39Z,2015-09-14T04:14:39Z,"When creating a new hostonlyif it appears that the adapter is not fully initialized when create returns success

Host OS - Windows 10 Build 10240
Virtual 5.0.4 - release and 5.0.5 102614

Example (note the garbage netmask returned)

{{{
vboxmanage hostonlyif create && vboxmanage list hostonlyifs
0%...10%...20%...30%...40%...50%...60%...70%...80%...90%...100%
Interface 'VirtualBox Host-Only Ethernet Adapter #3' was successfully created
Name:            VirtualBox Host-Only Ethernet Adapter #3
GUID:            336f5edf-a838-43a1-a55f-7955e605ee59
DHCP:            Enabled
IPAddress:       192.168.56.1
NetworkMask:     15.0.0.0
IPV6Address:     fe80:0000:0000:0000:384b:5e06:3257:bdb1
IPV6NetworkMaskPrefixLength: 64
HardwareAddress: 0a:00:27:00:00:00
MediumType:      Ethernet
Status:          Up
VBoxNetworkName: HostInterfaceNetworking-VirtualBox Host-Only Ethernet Adapter #3

}}}

Here's the same example with ipconfig

{{{
vboxmanage hostonlyif create && ipconfig
0%...10%...20%...30%...40%...50%...60%...70%...80%...90%...100%
Interface 'VirtualBox Host-Only Ethernet Adapter #3' was successfully created

Windows IP Configuration

Ethernet adapter VirtualBox Host-Only Network #3:

   Connection-specific DNS Suffix  . :
   Link-local IPv6 Address . . . . . : fe80::8d8e:d529:1359:8373%22
   Default Gateway . . . . . . . . . :

}}}

If we wait ~5 seconds after creation and use list hostonlyifs we get the correct information

{{{
vboxmanage hostonlyif create && timeout 5 && vboxmanage list hostonlyifs
0%...10%...20%...30%...40%...50%...60%...70%...80%...90%...100%
Interface 'VirtualBox Host-Only Ethernet Adapter #3' was successfully created

Waiting for 0 seconds, press a key to continue ...
Name:            VirtualBox Host-Only Ethernet Adapter #3
GUID:            c0b80be6-b9d2-499e-855b-b7043f26eec5
DHCP:            Enabled
IPAddress:       192.168.56.1
NetworkMask:     255.255.255.0
IPV6Address:     fe80:0000:0000:0000:a541:cd37:5679:1f0c
IPV6NetworkMaskPrefixLength: 64
HardwareAddress: 0a:00:27:00:00:00
MediumType:      Ethernet
Status:          Up
VBoxNetworkName: HostInterfaceNetworking-VirtualBox Host-Only Ethernet Adapter #3

}}}

This is big problem for tools like docker-machine,etc.
",ronwilliams
14560,Regression - networking broken after upgrade to 5.0.0 and also subsequent updates,VirtualBox 5.0.4,Windows,2015-09-09T09:18:54Z,2015-09-10T19:01:26Z,2015-09-10T19:01:26Z,"This worked with 4.3.x, but the problem started with upgrade to 5.0.0 from 4.3.28, but continues with every minor update - after installation, start-up of every virtual machine reports:

  Cannot connect to the network interface '\DEVICE\{C5EF3C32-2A5B-4649-B646-5A5D3A3BB319}'. The virtual network card will appear to work but the guest will not be able to connect. Please choose a different network in the network settings.

The problem is with !VirtualBox Host-Only Ethernet Adapter.

I tried to restart computer after update, but still the same problem.

Removing and re-adding !VirtualBox Host-Only Ethernet Adapter from !VirtualBox menu does not help.

The Device Manager with ""Show hidden devices"" option enabled shows that ""!VirtualBox Host-Only Ethernet Adapter - Deterministic Network Enhancer Miniport"" has exclamation mark with detail ""This device is not working properly because Windows cannot load the drivers required for this device. (Code 31)"".

Please note that I am using 192.168.150.0/24 network for !VirtualBox Host-Only adapter (IP 192.168.150.2, mask 255.255.255.0, DHCP 192.168.150.3, dynamic address from 192.168.150.100 to 192.168.150.199), because ''the default address 192.168.56.0/24 is my regular network''.

When I uninstall and install !VirtualBox, the ""!VirtualBox Host-Only Ethernet Adapter - Deterministic Network Enhancer Miniport"" device still reports the same problem. I need to uninstall !VirtualBox first, reboot and install !VirtualBox afterwards in order to get the networking up-and-running again (after changing the IP and DHCP of the Host-Only adapter from !VirtualBox menu).

This is reproducible with every update, starting from 5.0.0.

I am using Windows 7.

Do you need more info from me?",oldium
15534,VBoxManage hostonlyif ipconfig vboxnet1 --dhcp leads to error,VirtualBox 5.0.22,Linux,2016-06-19T20:56:24Z,2016-07-13T19:51:07Z,2016-07-13T19:51:07Z,"Host type: Debian jessie amd64

Trying to configure vboxnet1 to use dhcp after creating it leads to the following error:

{{{
VBoxManage: error: Code NS_ERROR_NOT_IMPLEMENTED (0x80004001) - Not implemented (extended info not available)
VBoxManage: error: Context: ""EnableDynamicIPConfig()"" at line 210 of file VBoxManageHostonly.cpp 
}}}

Steps to reproduce:
* create hostonlyif with ''VBoxManage hostonlyif create''
* call ''VBoxManage hostonlyif ipconfig vboxnet1 --dhcp''  (replace vboxnet1 by the name you get from V''BoxManage list hostonlyifs'' after creating it.

Using the VBoxNetworkName: ( HostInterfaceNetworking-vboxnet1 ) instead of vboxnet1 did not change anything.

",manschenk
15447,Win7 BSOD if DHCP server is On for Host-Only Ethernet Adapter,VirtualBox 5.0.20,Windows,2016-05-26T13:22:57Z,2016-05-26T13:22:57Z,2016-05-26T13:22:57Z,"Host is Win7 Sp1, guest seems to be irrelevant: Linux 2.6, Ubuntu, Win7 - all fail with BSOD.
The BSOD happens only if I use Host-Only Adapter and check ""DHCP Server -> Enable Server"". Without the DHCP it works.
I've also tried with the legacy driver: VirtualBox-installer.exe -msiparams NETWORKTYPE=NDIS5 - same thing.
Attaching VBox.log and the picture of BSOD, though can't attach minidump because that is not saved for some reason.",wentwog
15434,Host only adapter is not working after host wake up,VirtualBox 5.0.20,Windows,2016-05-19T17:43:05Z,2016-05-19T17:43:05Z,2016-05-19T17:43:05Z,"hi,

I have configured host only adapter for host-guest communication (Samba). But when host (windows 7) wakes up from sleep, host adapter stops working. I tried few things on guest and host but nothing worked. Please provide some tips...

thanks,
Sai ",Sai
14484,Host-only adapter fails after sleep-wake transition,VirtualBox 5.0.2,Windows,2015-08-21T22:57:02Z,2018-11-25T15:46:20Z,2018-11-25T15:46:20Z,"In 5.0.2, Window 7 host, Debian 8 guest, the host-only adapter only works after a full restart of host and guest.  Once you put the host to sleep and wake it back up again, the host-only adapter is broken.  Here is what ping from the guest gives:

root@byted> ping 192.168.56.1
PING 192.168.56.1 (192.168.56.1) 56(84) bytes of data.
From 192.168.56.101 icmp_seq=1 Destination Host Unreachable

where 192.168.56.101 is the guest IP and 192.168.56.1 is the adapter IP.  There is a similar break in ping of guest IP from host.

jpm
 ",Jeff Morgenthaler
15053,Genymotion Virtual Box Host Adapter not found,VirtualBox 5.0.14,Windows,2016-01-20T18:52:27Z,2016-01-28T10:43:45Z,2016-01-28T10:43:45Z,"Hello, i'm using last version 5.0.14 on Windows XP SP3 togheter with Genymotion. 
I write here because there is a virtualbox error and exactely :
The host network interface with the given name could not be found.

I've tried to delete all interface and when i open genymotion it recreate correctly virtual host adapter...

Thanks for helping",Dario Cdj
15019,Unable to create Host-Only Network in Windows 10,VirtualBox 5.0.12,Windows,2016-01-09T14:28:44Z,2018-01-19T22:32:40Z,2018-01-19T22:32:40Z,"I was unable to create host-only network in Windows 10 Home Single Language using {{{VBoxManage hostonlyif create}}} with following output:

{{{
0%...
Progress state: E_FAIL
VBoxManage.exe: error: Failed to create the host-only adapter
VBoxManage.exe: error: Querying NetCfgInstanceId failed (0x00000002)
VBoxManage.exe: error: Details: code E_FAIL (0x80004005), component HostNetworkInterfaceWrap, interface IHostNetworkInterface
VBoxManage.exe: error: Context: ""enum RTEXITCODE __cdecl handleCreate(struct HandlerArg *)"" at line 71 of file VBoxManageHostonly.cpp
}}}
",rkurniawan
14832,Unable to use Host-Only adapters on Windows 10 Threshold 2,VirtualBox 5.0.10,Windows,2015-11-16T01:38:09Z,2020-10-30T19:55:25Z,2020-10-30T19:55:25Z,"I installed the new Windows 10 update ""threshold 2"" via Windows Update, and VirtualBox is no longer able to use Host Only adapters.  While it creates them, changes their IPs, and deletes them with no trouble, the following error message comes up when I try to run any VM with a Host Only interface attached:

{{{
Failed to open a session for the virtual machine Ubuntu Test.

Failed to open/create the internal network 'HostInterfaceNetworking-VirtualBox Host-Only Ethernet Adapter' (VERR_INTNET_FLT_IF_NOT_FOUND).

Failed to attach the network LUN (VERR_INTNET_FLT_IF_NOT_FOUND).

Result Code: E_FAIL (0x80004005)
Component: ConsoleWrap
Interface: IConsole {872da645-4a9b-1727-bee2-5585105b9eed}
}}}

This worked with no trouble before the Windows Update, and all other adapter types still work perfectly.

I originally had this issue with VirtualBox 5.0.1, so I uninstalled that one and installed 5.0.10, and I still have the issue.

Log file attached.",kohenkatz
14855,Linux: Link local IPv6 address is the only one returned for host-only interfaces,VirtualBox 5.0.10,Linux,2015-11-21T22:08:52Z,2018-04-19T07:50:45Z,2018-04-19T07:50:45Z,"When configuring IPv6 on Linux, the interface may have a Link Local Address (fe::) in addition to the address configured through VirtualBox. VirtualBox retrieves the addresses from {{{/proc/net/if_inet6}}}. Here is an example of what these entries look like:
{{{
$ cat /proc/net/if_inet6 
00000000000000000000000000000001 01 80 10 80       lo
fd22dfff102810700000000000000000 06 40 00 80 vboxnet3
fe80000000000000020acdfffe20a291 02 40 20 80     eth0
fe80000000000000080027fffe000003 06 40 20 80 vboxnet3
}}}

Note the order of the addresses. When VirtualBox parses the file, the code assumes there would only be one entry for an interface (and does not terminate early), i.e. (this is NetIf-linux.cpp):
{{{#!c
173             for (;;)
174             {
[...]
182                 if (n == EOF)
183                     break;
184                 if (n != 9 || uLength > 128)
185                 {
[...]
188                     break;
189                 }
190                 if (!strcmp(Req.ifr_name, szName))
191                 {
192                     pInfo->IPv6Address.au32[0] = htonl(IPv6Address.au32[0]);
193                     pInfo->IPv6Address.au32[1] = htonl(IPv6Address.au32[1]);
194                     pInfo->IPv6Address.au32[2] = htonl(IPv6Address.au32[2]);
195                     pInfo->IPv6Address.au32[3] = htonl(IPv6Address.au32[3]);
196                     ASMBitSetRange(&pInfo->IPv6NetMask, 0, uLength);
197                 }
198             }
199             fclose(fp);
200         }
}}}

For the above example, the last, Link-Local entry wins. Since VirtualBox does not handle multiple addresses per interface, it should at least ignore the Link-Local automatically created addresses. Unfortunately, this means that it would be impossible to tell which address to pick if a user configures a different link-local address.

I attached a proposed patch to resolve this.",timuralp
14040,Windows host-only adapter creation fails due to slow background processing,VirtualBox 5.0.0,Windows,2015-04-10T02:11:16Z,2018-09-03T15:36:47Z,2018-09-03T15:36:47Z,"I was debugging why Xamarin Android Player could not prepare a VM for me and determined the failure to be in the host-only adapter creation, isolating the problem to this:

{{{
C:\Program Files\Oracle\VirtualBox\>VBoxManage.exe hostonlyif create
0%...
Progress state: E_FAIL
VBoxManage.exe: error: Failed to create the host-only adapter
VBoxManage.exe: error: Code E_FAIL (0x80004005) - Unspecified error (extended info not available)
VBoxManage.exe: error: Context: ""int __cdecl handleCreate(struct HandlerArg *,int,int *)"" at line 66 of file VBoxManageHostonly.cpp
}}}

After some time spent in the debugger, I've found the real error to be `CO_E_CLASSSTRING` (Invalid class string), naturally returned by some `CLSIDFromString()` API call. Interestingly enough, the input GUID string contained garbage only.

Further debugging revealed a data race in `VBoxNetCfgWinCreateHostOnlyNetworkInterface()`. By the time `RegQueryValueExW(..., ""NetCfgInstanceId"", ...)` is called, the network device might still not be fully constructed by another process and this registry value might not be present yet. Because the result of this operation is effectively ignored, the program silently continues and the function fails only later due to the GUID being invalid.

A proof from Process Monitor - it took the system ~0.4 seconds more to write the value:
{{{
03:11:01.9426053	VBoxSVC.exe	15024	RegQueryValue	HKLM\System\CurrentControlSet\Control\Class\{4D36E972-E325-11CE-BFC1-08002BE10318}\0018\NetCfgInstanceId	NAME NOT FOUND	Length: 144
03:11:02.3592881	svchost.exe	1140	RegSetValue	HKLM\System\CurrentControlSet\Control\Class\{4D36E972-E325-11CE-BFC1-08002BE10318}\0018\NetCfgInstanceId	SUCCESS	Type: REG_SZ, Length: 78, Data: {F4CCBF3A-4C8B-4FE7-A659-725C3DF52E69}
}}}

Waiting in the debugger for a while before the `RegQueryValueExW()` call helped and I was able to create host-only network adapters fine.

Setting as priority minor because:
* it happened on a pre-release OS (Windows 10 preview build 10052)
* it happened on a pre-release VirtualBox (5.0.0_BETA1 r99371).

On the other hand, I submitted a ticket anyway because:
* the race is still a bug and can possibly crash the program, it might have been working with a little bit of luck only
* it seems the relevant VBox code has not been changed for the current beta
* I hear there was some refactoring done in Windows 10 regarding network adapters, this might show up later for more people",Jiri Hruska
12459,Host-only adapter interface resets IP address back to default.,VirtualBox 4.3.4,Windows,2013-12-09T15:16:51Z,2016-02-10T13:49:02Z,2016-02-10T13:49:02Z,"There is an old defect #8796 that describes this same problem for an older version of Virtual Box.  I don't want this issue to get lost under an old defect so I've created this new one since this was not an issue with the last 2 versions prior to 4.3.4.

Starting with my upgrade to v4.3.4, every couple of days I have to reset my host-only adapter's interface IP back to my user configured one of 192.168.56.1.  It keeps resetting to 169.254.x.x, but only after a few days and I have not been able to identify any trigger.

Windows 7-64-bit with a hosted Windows 2008 R2 server.  The previous version did not have this problem so hopefully this will help to identify the cause.

The reset of the DHCP settings for the host-only adapter remains intact, it's only the interface's IP address.
",GCPeters
13323,Stop pre-populating a DHCP server on fresh installs?,VirtualBox 4.3.14,all,2014-08-26T21:30:41Z,2014-08-26T21:30:41Z,2014-08-26T21:30:41Z,"Hello there good VBoxers! :)

Vagrant core maintainer here. Working on an issue that comes up pretty regularly for folks in Vagrant-land:

https://github.com/mitchellh/vagrant/issues/3083

A fresh install of VirtualBox adds a default dhcpserver into its config.

https://www.virtualbox.org/browser/vbox/trunk/src/VBox/Main/xml/Settings.cpp?rev=52312#L1520

This dhcpserver ends up messing up Vagrant's interface <-> dhcpserver accounting and causes any first-time user with a DHCP-using interface in their Vagrantfile to get a cryptic error message.

We've considered writing code to detect and remove this default config, but it seems the simplest solution would just be to have VirtualBox avoid the default config and leave dhcpservers blank for fresh installs. Since there's no vboxnet0 by default it seems like this is less surprising behavior than having a dhcpserver that references a nonexistent interface in its name.

Looking forward to your thoughts - thanks for your time!

Paul / phinze",phinze
11496,Vboxmanage and host-only interfaces,VirtualBox 4.2.6,Windows,2013-02-16T08:28:58Z,2017-03-12T09:28:34Z,2017-03-12T09:28:34Z,"Original findings and history can be found here -> https://forums.virtualbox.org/viewtopic.php?f=6&t=54119
[[BR]]

Under Windows, when trying to use host-only adapter commands on vboxmanage, they fail intermittently and return this:
{{{
VBoxManage.exe: error: Failed to create the VirtualBox object!
VBoxManage.exe: error: Code CO_E_SERVER_EXEC_FAILURE (0x80080005) - Server execution failed (extended info not available)
VBoxManage.exe: error: Most likely, the VirtualBox COM server is not running or failed to start.
}}}

Taken from the forum post :
{{{
C:\Program Files\Oracle\VirtualBox>VBoxManage hostonlyif remove ""VirtualBox Host-Only Ethernet Adapter""
0%...10%...20%...30%...40%...50%...60%...70%...80%...90%...100%

C:\Program Files\Oracle\VirtualBox>VBoxManage hostonlyif create
0%...10%...20%...30%...40%...50%...60%...70%...80%...90%...100%
Interface 'VirtualBox Host-Only Ethernet Adapter' was successfully created

C:\Program Files\Oracle\VirtualBox>VBoxManage list -l hostonlyifs
Name:            VirtualBox Host-Only Ethernet Adapter
GUID:            58abe14a-3f99-40cf-9cdb-c1cb61be1373
DHCP:            Disabled
IPAddress:       192.168.74.1
NetworkMask:     255.255.255.0
IPV6Address:     fe80:0000:0000:0000:34a4:84d0:99c9:97fa
IPV6NetworkMaskPrefixLength: 64
HardwareAddress: 08:00:27:00:a0:1d
MediumType:      Ethernet
Status:          Up
VBoxNetworkName: HostInterfaceNetworking-VirtualBox Host-Only Ethernet Adapter


C:\Program Files\Oracle\VirtualBox>VBoxManage hostonlyif ipconfig ""VirtualBox Host-Only Ethernet Adapter"" --ip 172.17.101

C:\Program Files\Oracle\VirtualBox>VBoxManage list -l hostonlyifs
Name:            VirtualBox Host-Only Ethernet Adapter
GUID:            58abe14a-3f99-40cf-9cdb-c1cb61be1373
DHCP:            Disabled
IPAddress:       172.17.101.143
NetworkMask:     255.255.0.0
IPV6Address:     fe80:0000:0000:0000:34a4:84d0:99c9:97fa
IPV6NetworkMaskPrefixLength: 64
HardwareAddress: 08:00:27:00:a0:1d
MediumType:      Ethernet
Status:          Up
VBoxNetworkName: HostInterfaceNetworking-VirtualBox Host-Only Ethernet Adapter


C:\Program Files\Oracle\VirtualBox>VBoxManage hostonlyif remove ""VirtualBox Host-Only Ethernet Adapter""
0%...10%...20%...30%...40%...50%...60%...70%...80%...90%...100%

C:\Program Files\Oracle\VirtualBox>VBoxManage hostonlyif create
0%...10%...20%...30%...40%...50%...60%...70%...80%...90%...100%
Interface 'VirtualBox Host-Only Ethernet Adapter' was successfully created

C:\Program Files\Oracle\VirtualBox>VBoxManage list -l hostonlyifs
VBoxManage.exe: error: Failed to create the VirtualBox object!
VBoxManage.exe: error: Code CO_E_SERVER_EXEC_FAILURE (0x80080005) - Server execution failed (extended info not available)
VBoxManage.exe: error: Most likely, the VirtualBox COM server is not running or failed to start.
}}}

{{{
c:\Program Files\Oracle\VirtualBox>Vboxmanage hostonlyif remove ""VirtualBox Host-Only Ethernet Adapter""
0%...10%...20%...30%...40%...50%...60%...70%...80%...90%...100%

c:\Program Files\Oracle\VirtualBox>VBoxManage hostonlyif create
0%...10%...20%...30%...40%...50%...60%...70%...80%...90%...100%
Interface 'VirtualBox Host-Only Ethernet Adapter' was successfully created

c:\Program Files\Oracle\VirtualBox>VBoxManage list -l hostonlyifs
Name:            VirtualBox Host-Only Ethernet Adapter
GUID:            a5f0012b-7729-4d31-8d4a-744f67e13797
DHCP:            Disabled
IPAddress:       192.168.123.1
NetworkMask:     255.255.255.0
IPV6Address:     fe80:0000:0000:0000:dc5b:cdf6:ea70:c8a2
IPV6NetworkMaskPrefixLength: 64
HardwareAddress: 08:00:27:00:94:7b
MediumType:      Ethernet
Status:          Up
VBoxNetworkName: HostInterfaceNetworking-VirtualBox Host-Only Ethernet Adapter


c:\Program Files\Oracle\VirtualBox>VBoxManage hostonlyif ipconfig ""VirtualBox Host-Only Ethernet Adapter"" --ip 172.17.101.143 --netmask 255.255.0.0

c:\Program Files\Oracle\VirtualBox>VBoxManage list -l hostonlyifs
VBoxManage.exe: error: Failed to create the VirtualBox object!
VBoxManage.exe: error: Code CO_E_SERVER_EXEC_FAILURE (0x80080005) - Server execution failed (extended info not available)
VBoxManage.exe: error: Most likely, the VirtualBox COM server is not running or failed to start.

c:\Program Files\Oracle\VirtualBox>ipconfig

Windows IP Configuration
--snip--
Ethernet adapter VirtualBox Host-Only Network:

   Connection-specific DNS Suffix  . :
   Link-local IPv6 Address . . . . . : fe80::dc5b:cdf6:ea70:c8a2%25
   IPv4 Address. . . . . . . . . . . : 172.17.101.143
   Subnet Mask . . . . . . . . . . . : 255.255.0.0
   Default Gateway . . . . . . . . . :
--snip--
}}}

Again, this problem is very intermittent.

4.2.4 & 4.2.6 currently broken.",Max D
13948,Host only interfaces in linux host are being deleted after system reboot.,VirtualBox 4.2.24,all,2015-03-10T06:52:39Z,2015-03-11T09:00:11Z,2015-03-11T09:00:11Z,"I am using virtualbox verion 4.2.26. I create some hostonly interfaces(vboxnetxx) to communicate from host to guest. When the system is rebooted all these hostonly interfaces are being removed (even though the virtual machines exist) and I am not able to communicate with my machines.
I observed that all the info in virtualbox.xml file is being removed.
Please let me know if it is a desired functionality or a bug.",PRANEETH MANNEM
11663,Host-only adapter slows down DNS resolution tremendously,VirtualBox 4.2.10,Windows,2013-04-01T20:32:55Z,2015-08-13T16:45:38Z,2015-08-13T16:45:38Z,"I have tried VB 4.2.10 and 4.1.24 with the same result.

I recently compiled libcurl myself for a custom client. DNS resolution was awefully slow, around 5 to 10 seconds. After a [http://curl.haxx.se/mail/lib-2013-04/0007.html post] to the mailing list. I have figured out that when I disable the Host-only adapter, resolution screams again.

With host-only disabled:

{{{
D:\workspace-4.2\curlsimple\Debug>curlsimple.exe http://www.virtualbox.org
Provided URL: http://www.virtualbox.org
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
100   247  100   247    0     0    606      0 --:--:-- --:--:-- --:--:--   631
Name lookup time: 0.016000 s
Connect time: 0.187000 s
Pretransfer time: 0.016000 s
start transfer time: 0.188000 s
Total time: 0.407000 s
}}}

With host-only enabled:

{{{
D:\workspace-4.2\curlsimple\Debug>curlsimple.exe http://www.virtualbox.org
Provided URL: http://www.virtualbox.org
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
100   247  100   247    0     0     47      0  0:00:05  0:00:05 --:--:--    57
Name lookup time: 4.844000 s
Connect time: 0.188000 s
Pretransfer time: 0.000000 s
start transfer time: 0.187000 s
Total time: 5.219000 s
}}}

There must be something intercepting and blocking DNS resolution for some reason.

I am on Windows XP SP3, compiled libcurl 7.29.0 with mingw/gcc 4.7.2.",Michael-O
11005,Unable to ping guest from host in host-only network; ping6 works,VirtualBox 4.2.0,Mac OS X,2012-09-30T18:15:27Z,2015-08-13T17:29:28Z,2015-08-13T17:29:28Z,"An environment with a VM that has 2 types of networks: 1 NAT, 1 Host-Only [[BR]]
NAT works fine for world access but for internal access to the host, the IPv4 is not working even though IPv6 works fine [[BR]]

The host is running MacOSX 10.7.5 [[BR]]
The Guest is an Ubuntu 11.10 [[BR]]

Host virtual switches
{{{
vboxnet0: flags=8842<BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1500
	ether 0a:00:27:00:00:00
vboxnet1: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1500 
	ether 0a:00:27:00:00:01
	inet 10.100.100.1 netmask 0xffffff00 broadcast 10.100.100.255
	inet6 fe80::800:27ff:fe00:1%vboxnet1 prefixlen 64 scopeid 0x9  
	inet6 2000:aaaa::1 prefixlen 64
}}}
Ping6 test from host to guest
{{{
nightwatch:~ ricky$ ping6 2000:aaaa::2
PING6(56=40+8+8 bytes) 2000:aaaa::1 --> 2000:aaaa::2
16 bytes from 2000:aaaa::2, icmp_seq=0 hlim=64 time=155.398 ms
16 bytes from 2000:aaaa::2, icmp_seq=1 hlim=64 time=0.715 ms
16 bytes from 2000:aaaa::2, icmp_seq=2 hlim=64 time=1.023 ms
16 bytes from 2000:aaaa::2, icmp_seq=3 hlim=64 time=0.840 ms
16 bytes from 2000:aaaa::2, icmp_seq=4 hlim=64 time=0.929 ms
16 bytes from 2000:aaaa::2, icmp_seq=5 hlim=64 time=0.875 ms 
16 bytes from 2000:aaaa::2, icmp_seq=6 hlim=255 time=0.909 ms
16 bytes from 2000:aaaa::2, icmp_seq=7 hlim=255 time=0.873 ms
16 bytes from 2000:aaaa::2, icmp_seq=8 hlim=255 time=0.864 ms
16 bytes from 2000:aaaa::2, icmp_seq=9 hlim=255 time=0.739 ms
16 bytes from 2000:aaaa::2, icmp_seq=10 hlim=255 time=0.756 ms
16 bytes from 2000:aaaa::2, icmp_seq=11 hlim=255 time=1.067 ms
^C
--- 2000:aaaa::2 ping6 statistics ---
12 packets transmitted, 12 packets received, 0.0% packet loss
round-trip min/avg/max/std-dev = 0.715/13.749/155.398/42.709 ms
}}}
Ping Test from Host to Guest
{{{
nightwatch:~ ricky$ ping 10.100.100.2
PING 10.100.100.2 (10.100.100.2): 56 data bytes
Request timeout for icmp_seq 0
Request timeout for icmp_seq 1
^C
--- 10.100.100.2 ping statistics ---
3 packets transmitted, 0 packets received, 100.0% packet loss
nightwatch:~ ricky$ 
}}}
Guest Network Configuration
{{{
ricky@bunker:~$ ifconfig
eth0      Link encap:Ethernet  HWaddr 08:00:27:41:4f:1b
          inet addr:10.0.2.15  Bcast:10.0.2.255  Mask:255.255.255.0
          inet6 addr: fe80::a00:27ff:fe41:4f1b/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:2 errors:0 dropped:0 overruns:0 frame:0
          TX packets:29 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          RX bytes:1180 (1.1 KB)  TX bytes:2240 (2.2 KB)
eth1      Link encap:Ethernet  HWaddr 08:00:27:9d:08:1d
          inet addr:10.100.100.2  Bcast:0.0.0.0  Mask:255.255.255.0
          inet6 addr: fe80::a00:27ff:fe9d:81d/64 Scope:Link
          inet6 addr: 2000:aaaa::2/64 Scope:Global
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:168 errors:0 dropped:0 overruns:0 frame:0
          TX packets:238 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:20887 (20.8 KB)  TX bytes:23841 (23.8 KB)
lo        Link encap:Local Loopback
          inet addr:127.0.0.1  Mask:255.0.0.0
          inet6 addr: ::1/128 Scope:Host
          UP LOOPBACK RUNNING  MTU:16436  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)
pimreg    Link encap:UNSPEC  HWaddr 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00
          UP RUNNING NOARP  MTU:1472  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)
}}}
Ping6 Test from guest to Host
{{{
ricky@bunker:~$ ping6 2000:aaaa::1
PING 2000:aaaa::1(2000:aaaa::1) 56 data bytes
64 bytes from 2000:aaaa::1: icmp_seq=1 ttl=64 time=0.317 ms
64 bytes from 2000:aaaa::1: icmp_seq=2 ttl=64 time=0.518 ms
^C
 2000:aaaa::1 ping statistics
2 packets transmitted, 2 received, 0% packet loss, time 1001ms
rtt min/avg/max/mdev = 0.317/0.417/0.518/0.102 ms
ricky@bunker:~$ ^C
}}}",Rick
10317,Windows 8 Host: No network adapters after resume from sleep,VirtualBox 4.1.8,Windows,2012-03-12T06:14:51Z,2017-01-26T05:07:15Z,2017-01-26T05:07:15Z,"I am running Oracle VirtualBox 4.1.8 r75467 on a Thinkpad T510.  When I put my computer to sleep, the only way to get functioning NIC's on my host after resume is to go into device manager, uninstall the NIC and then scan for hardware changes to re-install the NIC.  I disabled the VirtualBox Bridged Network Driver on each NIC and I no longer have this problem.",Andrew
9688,Private host network problem => Fixed in SVN,VirtualBox 4.1.4,Windows,2011-10-04T13:44:08Z,2016-07-01T09:26:13Z,2016-07-01T09:26:13Z,"Since I have pass to the last version 4.1.4 I have a problem :

The Private host network function for the partage in network don't work.

This functionnaly don't work since i have restart the computer.

I use Windows 7 and a VM with ubuntu 10.10.

I have solve my problem with re-install the version 4.0.12.

Sorry for my english.

Regards.",alex57
10908,vboxnet host side MAC address should be configurable,VirtualBox 4.1.22,Mac OS X,2012-09-10T16:07:42Z,2015-05-19T16:45:30Z,2015-05-19T16:45:30Z,"Host side MAC address  of hostonlyifs, vboxnetX, are statically assigned 0a:00:27:00:00:X, where 0 <= X <= 127, which is good for the what it was designed for.

However, in certain applications of the virtualbox, these MAC addresses are announced to the external network as station behind L2 bridges. IEEE802.11s mesh networking protocol is an example of such application. In such cases, likelihood of MAC address collision is extremely large under the current assignment scheme. It should be fixed so that lower 3 octets could be configurable (just like the guest side of the interface).",shinoda
10811,MAC addresses filtered by VBox bridging,VirtualBox 4.1.18,Linux,2012-08-07T02:59:11Z,2019-09-12T16:25:43Z,2019-09-12T16:25:43Z,"I am attempting to run an OpenVPN server in a Ubuntu 12.04 (server) guest machine running on a Ubuntu 12.04 (server) host via VBoxHeadless.  This OpenVPN server needs to run as a layer 2 VPN (tap) which means it will place clients onto the local LAN with their own MAC addresses visible, and these clients need to be capable of two-way communication at layer 2.  I have been using the bridged network adapter for the VM.

When run from within the VM, I can connect clients to this server and ping/log into the server's IP, (guest machine) but I cannot access the Host's IP or anything else on the LAN from the client.  If I set up the OpenVPN server identically on the host, (Which is the same OS and otherwise identical setup) it works fine.  OpenVPN requires setting up a bridge internally on the server for this kind of layer 2 tap VPN, and putting the ethernet interface into promiscuous mode.  I've tried attaching the VM bridged adapter to the physical eth0 interface of the host and also to a bridged adapter on the host that was then bridged to the eth0 interface while eth0 was in promiscuous mode (similar to the setup on the guest)

I have found two other references to this problem, one with a Linux host, the other with Windows.  The Windows one was ticket #8965.  Both references indicate that this bug was a regression between versions 4.0.4 and 4.0.6.  Since I'm using Ubuntu 12.04 and VBox 4.1.18, downgrading to VBox 4.0.4 to confirm this would be painful.

Looking at the changelog of 4.0.6, I suspect that I've found the culprit:
""Host-Only & Bridged & Internal Networking: fix for processing promiscuous mode requests by VMs, defaulting to switch behaviour ""

Not sure what is meant by ""switch behavior"" but a switch is nothing more than a many-port bridge, which will broadcast frames to all ports but the one it came in on if the MAC is not in the MAC table, will learn the source MAC of any frame and put it in the MAC table for the port it came in on, and will unicast learned MACs to the ports on which the MAC table says they reside.  This may be somewhat inconsistent with being able to specify a MAC for the bridged adapter of the guest (which I have also done in this case)  If the switch portion is not flooding unlearned frames out to the guest machine virtual ports and also learning new MAC entries from frames sent by those ports, then the behavior may be efficient, but it will also be incorrect for Guests with their interfaces in promiscuous mode.

This bug is closely related to #8965 and this version with the Linux host type is also referenced here: https://forums.virtualbox.org/viewtopic.php?f=7&t=42335&p=203067&hilit=openvpn#p203067
",Raltar
10802,Host only interfaces should be down when not in use,VirtualBox 4.1.18,Mac OS X,2012-08-04T10:08:57Z,2012-08-05T01:42:25Z,2012-08-05T01:42:25Z,"I noticed that host side interface (i.e. vboxnet*) stay ""UP"" even when VMs referring to the interfaces. They even stay ""UP"" when the virtual box manager is not present. It is nice, and probably semantically correct that vboxnet* interfaces are brought down when they are not referenced, or at least when the virtual box manager is not running.
",shinoda
8796,Host-only adapter interface lost it's manual configured ipv4 address,VirtualBox 4.0.6,Windows,2011-04-26T23:01:51Z,2017-01-06T04:00:56Z,2017-01-06T04:00:56Z,"I have a host-only interface created by 2.x long time ago. After installation of 4.0.6, I find I have to re-configure the ip address of host-only interface after every reboot.
The ip address is manually configured by vbox manager gui, and then I add gateway and dns server in the ipv4 properties。 After reboot，the configuration in the ipv4 properties seems not changed, but in the vbox manager gui, the ip address will be something like ""169.254.4.67"", and the ipconfig.exe command will show the same address.",kidault
8769,VLAN tagged packets mangled on bridged adapter,VirtualBox 4.0.6,Linux,2011-04-22T22:05:14Z,2013-01-14T13:43:24Z,2013-01-14T13:43:24Z,"A guest that is bridged to a physical adapter on which VLAN tagged packets (ethertype 0x8100) are received, the packets arrive in the guest without the VLAN tag.

I will attach a Wireshark packet decode of a frame as seen from the host and the guest for review.",Kevin Otte
8731,Cannot use bond0 on Mac OS X 10.6.7 and some other errors...,VirtualBox 4.0.4,Mac OS X,2011-04-16T16:13:51Z,2011-05-17T18:45:46Z,2011-05-17T18:45:46Z,"When I created a LACP link on a Mac OS X server 10.6.7 , I can't use it as an interface with VirtualBox. It would complain something about 

My guest is Ubuntu 10.04 64-bit. I also noticed that I saw what seemed like disk errors during the bootup of the guest..

attached are the log files.",John Huong
9166,vboxnet0 doesn't count traffic correctly (Linux host),VirtualBox 4.0.10,Linux,2011-07-07T18:17:47Z,2015-04-28T04:17:29Z,2015-04-28T04:17:29Z,"On a Linux box with VirtualBox 4.0.10 installed and with a Windows XP virtual machine with default settings.

'''ifconfig vboxnet0''' does not show the reality :

{{{
[root@fedora15 ~]# ifconfig vboxnet0
vboxnet0  Link encap:Ethernet  HWaddr 0A:00:27:00:00:00
          inet adr:192.168.56.1  Bcast:192.168.56.255  Masque:255.255.255.0
          adr inet6: fe80::800:27ff:fe00:0/64 Scope:Lien
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:1193 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 lg file transmission:1000
          RX bytes:0 (0.0 b)  TX bytes:274935 (268.4 KiB)
}}}

I've transferred much more than 268.4 KiB and obviously received some data.

Problem can also be seen with ""tcpdump"" which shows traffic only in one direction and ""bwm-ng"" which doesn't show any traffic at all.

This ticket is related to this post http://forums.virtualbox.org/viewtopic.php?f=7&t=38499 and to a conversation I've had on IRC where I've been told to fill in a bug report.

The Linux host is a Fedora 15 up to date (07/07/2011).
Windows VM is also up to date.
",a_i_
7094,VirtualBox kills network connectivity if VLAN tagging enabled on Realtek NIC,VirtualBox 3.2.6,Windows,2010-06-30T23:46:16Z,2015-10-15T07:56:42Z,2015-10-15T07:56:42Z,"If VLAN tagging is enabled on the Realtek network card of a system with VirtualBox installed, and the ""VirtualBox Bridged Network Driver"" is bound to that network card (the default behavior), no network access is possible.  The only remedy is to either disable VLAN tagging or unbind the ""VirtualBox Bridged Network Driver"" and reboot the system.  The former is no remedy, because we use VLAN tagging (to the desktop) in our environment.  The latter remedy obviously means no network access for VirtualBox.  It would be nice if this issue could be fixed, as Microsoft HyperV does not suffer from this problem, and I'd much rather use VirtualBox.
{{{
Steps to reproduce:

1. Install the appropriate full Realtek NIC driver from http://www.realtek.com
/downloads/downloadsView.aspx?Langid=1&PNid=13&PFid=5&Level=5&Conn=4&DownTypeID=3&GetDown=false
2. Install VirtualBox on a system with a ""Realtek PCIe GBE Family Controller""
3. Open the Network Connection Control Panel
4. Right-click ""local Area Connection"" and choose ""Properties""
5. Click Configure
6. Click Advanced
7. Under the ""Propery:"" list, select ""Priority & VLAN"" then, under the ""Value:"" list, select ""Priority & VLAN Enabled""
8. Click Start --> All Programs --> Realtek --> Diagnostic Utility --> Realtek Ethernet Diagnostic Utility
9. Select ""Realtek PCIe GBE Family Controller"" from the list on the left
10 Click ""VLAN"" (from the middle column)
11. Click ""Add"" and enter a VLAN ID (for a VLAN that actually exists on your network) and press <ENTER>
12. Confirm adding of the VLAN and close the Realtek utility
13. Check to see if you still have network connectivity.  If you do, reboot.
14. You should not longer have network connectivity.
15. Open ""local Area Connection Properties""
16. Uncheck ""VirtualBox Bridged Network Driver"" and click ""OK"".  Reboot
17. Now you should have network connectivity.

This problem is happening on a system with the following characteristics;

- Windows 7 64-bit
- Realtek Realtek PCIe Gigabit Etherenet NIC
- Virtual Box 3.2.x
}}}",viro
6994,Raise maximum number of Host-Only networks,VirtualBox 3.2.4,other,2010-06-14T11:31:08Z,2010-06-16T22:32:56Z,2010-06-16T22:32:56Z,"The current limit of 8 is plenty for any reasonable application, but there are a lot of unreasonable applications out there.  In my case, I need at least 60 Host-Only networks.  I was able to achieve this by editing the VB OSE source code, but it would be nice if this was an official enhancement.",UglyPercy
6995,Permit names to be specified for Host-Only adapters,VirtualBox 3.2.4,other,2010-06-14T11:34:49Z,2010-06-14T11:34:49Z,2010-06-14T11:34:49Z,"As opposed to the current fixed scheme of ""vboxnet0"", etc..  This would make it possible to encode various information in the name of the adapter, e.g. ""HOSTONLY_2_3"" might be recognized as interface 3 of VM 2.  This would enable one to easily collect per-VM statistics, etc..",UglyPercy
7897,Only one IP of multi-homed guest is visible,VirtualBox 3.2.12,Linux,2010-12-23T21:06:05Z,2010-12-24T08:03:51Z,2010-12-24T08:03:51Z,"I have a Windows guest that is multihomed (multiple IPs to single NIC).  The host's NIC is bridged so traffic should be passed for both IPs.  However, from the outside network, I can only ping the first IP address assigned to the guest NIC.  Inside the guest, I can ping the first and second IP addresses assigned to the guest NIC.  This is why I believe this is a bug in the host interface bridging code.

BTW, thanks for making bridged adapter support much simpler in VirtualBox 3.1 on Linux...it was a huge PITA before :-)

The vbox.log is attached.",Ken Yee
7843,"VBox host-only network is reported as ""Unidentified Network"" and Public on Windows7 hosts",VirtualBox 3.2.12,Windows,2010-12-14T01:28:54Z,2010-12-14T01:28:54Z,2010-12-14T01:28:54Z,"I am configuring virtual machines that are using the host-only network interface to connect to the host machine.

My host OS is Windows 7 and its firewall operates by classifying which network adapters and networks are public vs. work/home.  Based on this classification, the firewall determines which interfaces allow service connections (e.g. cifs, http, etc.) and which interfaces do not.

The host-only network interface cannot be modified to change the network name nor network access type in the Windows ""Network and Sharing Center""  If I click on the network type (Work, home, public) of any other adapter, a dialog comes up that allows me to change the type and name.  If I click on the bench of the vbox host-only iface, then I get an immutable dialog that shows me a read-only textfield and no capability to change the network type.

Please fix this.  I do not want to install 3rd party firewall software, nor do I want to needlessly expose my box to public-network elements when I need VM guests to connect to my host.  A host-only network is arguably more ""private"" than a ""public network""",Perry
6519,Network bridge does not work with multiple mac addresses on the guest side,VirtualBox 3.1.6,Linux,2010-04-10T00:41:23Z,2011-02-19T18:34:59Z,2011-02-19T18:34:59Z,"The Bridged network mode seems to be unable to deal with multiple MAC addresses being used to send packets from a guest. This situation occurs when a network bridge is configured inside a guest system.

It looks like the virtualbox network bridge can only keep track of one MAC address for which it accepts incoming packets for the guest; that mac address is most likely set to the source address of the last outgoing packet from the guest. This results in major packetloss for both the guest and systems on the other side of the guest's network bridge.

In most cases, the described behaviour is close to how a normal NIC would behave. However, if the NIC is in Promiscuous mode (which is the case for network bridges), the NIC should present all packets it receives to the guest, without filtering.

It may not be feasible to present all received packets to the guest for performance reasons; however if the guest explicitly enables promiscuous mode it is requesting to receive all such packets, and usually needs this behaviour.

A reasonable alternative to accepting *all* packets would be to enlarge the MAC address buffer, but this would require a far more complex network switch implementation.",Ivo Smits
6547,"Cancelling ""Add host-only network"" causes ""Unknown device"" to be created.",VirtualBox 3.1.6,Windows,2010-04-18T12:06:27Z,2010-04-19T10:08:34Z,2010-04-19T10:08:34Z,"How to duplicate:

 * Click File->Preferences...
 * Select Network page
 * Click the ""Add host-only network"" button
 * When the ""Hardware Installation"" dialog for ""!VirtualBox Host-Only Ethernet Adaptor"" appears, click the ""STOP Installation"" button.
 * If you then look at the Windows Device Manager, under Network Adaptors, there is an ""Unknown device"" entry that cannot be uninstalled.
 * When Windows is rebooted, it starts the ""Found New Hardware Wizard"" for the unknown device called ""Net"".  It keeps doing this every time Windows is rebooted.

!VirtualBox should really detect that the installation of the network driver was stopped by the user, and clean-up the Unknown device.

Tested on Windows XP SP3 (32-bit) host.

A related ticket is #4257.",gonk23
6323,Can't get IP Forwarding to work with Host-only adapter,VirtualBox 3.0.6,Linux,2010-03-04T07:48:08Z,2011-01-26T12:41:53Z,2011-01-26T12:41:53Z,"Hello, 

I'm developing a software to demonstrate how Man in the middle works using arp cache poisoning. I can't get ip forwarding to work with Host-only adapter! 

I was previously using a bridged network on tun/tap devices that I was creating myself. My network was designed like this : 

[*]1 bridge br0

[*]2 tun/tap interfaces tap0 and tap1


Then I add the tap0 and tap1 to the bridge and configure my 2 VMs to use bridged network on tap0 and tap1.
With this configuration, ip-forwading works perfectly fine!  My bridge br0 can play the role of the attacker and forward ip between my first and second VM.

'''Now I'm trying to use host-only adapter''', so that i could use later in my program the ''VBoxManage hostonly ipconfig'' command line. In the configuration I want to be, my 1st VM wants to talk to my 2nd VM but its arp cache has been corrupted so that packets are sent to the host (host-only interface). My problem is packets aren't forwarded by the host, and they normally should be.

I'm enabling ip forwarding on the host-only adapter  (vboxnet0), as I was doing before with my bridge br0 : 

{{{
echo 1 > /proc/sys/net/ipv4/conf/*/forwarding 
echo 0 > /proc/sys/net/ipv4/conf/*/send_redirects
}}}

Unfortunately, even though each machine in this configuration can communicate with one another, the vboxnet0 interface doesn't forward ip packets. Shouldn't host only interface behave like a normal networking interface?

Thank you, 

Laurent Sebag",grattemedi
5130,"Bridging eth0 needs ""link"" in order to work",VirtualBox 3.0.6,Linux,2009-10-06T12:30:03Z,2011-01-26T12:41:31Z,2011-01-26T12:41:31Z,"Ran into problem when trying to bridge virtual Ubuntu 9.10 with host Fedora 11 using the distributions VBox-packages. Using NIC eth0 (Thinkpad T61)

In order to get the bridge to work I had to plug in a TP-cable in the host to get ""link"". When cable removed the bridge stop working.

kernel: 2.6.30.8-64-fc11.i586
VBox 3.0.6

I don't have a problem with the issue as there is a easy workaround, but one have to be aware of it.",Niklas Andersson
4876,A duplicate name exists on the network - Windows Error,VirtualBox 3.0.4,Windows,2009-08-29T19:48:01Z,2011-02-20T22:58:44Z,2011-02-20T22:58:44Z,"VirtualBox Guest has problems with DHCP leases managed by ASUS Wireless Router RT-N11 (host connected by cable).

Guest does the DHCP has grabs an IP address although it is not accessible by the network name, only by IP address.

See images attached.",XoK
4562,[feature-request] 'Default Gateway' parameter in DHCP server for host-only networks,VirtualBox 3.0.2,other,2009-07-17T21:46:03Z,2011-05-09T05:20:44Z,2011-05-09T05:20:44Z,"Please add the 'Default Gateway' parameter in DHCP server for host-only networks.
Otherwise the TCP/IP configuration in guests which are use the VBox DHCP server is imperfect -- some of them cannot be configured to use any default gateway without to turn off using dhcp.",Michael
5515,Builtin DHCP server does not pick up setting update once started,VirtualBox 3.0.12,Windows,2009-11-20T10:25:21Z,2020-09-10T08:52:41Z,2020-09-10T08:52:41Z,"I have several hosts that I want to connect with each other without access to the outside world. So all hosts use host-only networking. One of the hosts provides PXE and DHCP, so I went to File -> Preferences -> Network and edited the settings for the host-only networking. In the tab of the DHCP Server I disabled the DHCP server. Then I started my management server (fixed IP address in the proper range), configured DHCP with a range outside the default range for host-only and started one of the client hosts. PXE went well and the OS was installed. When the client host requested an IP-address, it was served with an address from the builtin DHCP server although I disabled this server. Stopping all clients and restarting VirtualBox did not solve this. After a reboot of the host system, the DHCP server was truly disabled and the client was served with an address from my management server.",SiemKorteweg
4134,Host Only Networking: Route Connections,VirtualBox 2.2.4,Linux,2009-05-30T12:49:28Z,2010-05-31T06:50:17Z,2010-05-31T06:50:17Z,"To make host-only networking more user-friendly add the folwing configuration options to
File -> Global Settings -> Networking -> HostOnly Networking Connection -> Change.

Add a additional tab to the existing ""DHCP Settings"" and ""Adapter"" tabs with the following checkboxes:

[ ] Routing
   [ ] Regular Routing
       (use the current default route to forward connections)
   [ ] NAT
       (hide the the hosts of the host-only-network behind the host-machine)
        e.g.:
        iptables -t nat -A POSTROUTING -o ${IFNAME} -j MASQUERADE
        echo 1 >/proc/sys/net/ipv4/ip_forward

[ ] DNS Forwarding
    Activate a proxy dns listening on the gateway ip of the host-only-network
    which forwards all requests to the currently(!) configured dns-servers in /etc/resolv.conf
    Maybe you can reuse ""dnsmasq"".

Keep in mind that virtualbox is used often on laptops - therefore the networking settings are changeing
i.e. if you are at home (using wlan) or at work (using ethernet).
",Marc Schoechlin
3866,Host-only interface interferes with the current adapter,VirtualBox 2.2.2,Windows,2009-04-29T03:21:22Z,2015-05-22T10:11:14Z,2015-05-22T10:11:14Z,"When the host-only interface is installed, it '''suddenly''' screws up the connection for the physical adapter. The adapter says it is identifying the network when it is connected to it already.",Frank
3236,hostif networking doesn't work when link is down,VirtualBox 2.1.2,Linux,2009-01-30T17:15:04Z,2010-05-03T17:44:31Z,2010-05-03T17:44:31Z,"I route traffic from eth0 to wlan0, and use hostif eth0 for VirtualBox. If no devices are physically connected to eth0 (and turned on), the kernel reports 'eth0: link down', and virtualbox networking doesn't work. When a devices is on and connected to eth0, the kernel reports 'eth0: link up', and virtualbox networking starts working. If I disconnect the device from eth0 it stops working again.

I could just use wlan0 hostif instead, but then it's difficult to filter the traffic, run my own DHCP server, etc. Also I already forward eth0 to wlan0 for physical devices, and it makes sense to use the same setup for virtualbox.",Bryce Allen
2760,Feature request: direct tun/tap support not available since 2.1.0,VirtualBox 2.1.0,Linux,2008-12-17T19:17:21Z,2015-05-19T17:36:20Z,2015-05-19T17:36:20Z,"It was very nice that virtualbox supported the direct usage of tun/tap interfaces and NOT used another driver which means one more possible point of failure or incompatibility. That was a major advantage compared to other virtualisation systems (vmware for example). Now there is possibly a ""double bridge"" (on in the ""filter driver"" and one in the working and very stable kernel mainline bridge code) which means double work, possibly worse performance.

Why reinvent the wheel? Please readd direct tap support again!
",M. Schinkel
