﻿ticket,summary,version,host,created,modified,_changetime,_description,_reporter
21039,Guest Windows firewall disable does disable internet on Windows Host,VirtualBox 6.1.16,Windows,2022-07-27T17:32:47Z,1970-01-01T00:00:00Z,1970-01-01T00:00:00Z,"* Host/Guest: Windows 7 x64

I am trying to use shared MAC address on both Host and Guest, because ISP does block internet access by the MAC.

In that case if set Bridged network mode and try to disable the Windows 7 x64 firewall on the Guest, then the internet would be disabled on the Windows 7 x64 Host.",andry81
3368,vlan interface support in os x version,VirtualBox 2.1.4,Mac OS X,2009-02-18T00:01:23Z,2009-07-16T20:54:48Z,2009-07-16T20:54:48Z,"In os x leopard (10.5) it is possible to add vlan interfaces as follows:

-Click on system preferences----->network
-Click on the ""cog"" icon at the botom of the interfaces list and select ""manage virtual interfaces.
-Add additional tagged interface as per needed ;)

Once created, these interfaces show up to OS X as if they were additional physical interfaces, but do not show up as usable host interfaces in virtualbox.  If it could be possible to use these interfaces in virtualbox it would make an enormous different to my ability to use virtualbox on an OS X host as a server virtualization solution in my production environment.  Without it I am limited to only being able to have virtual machines on as many subnets as I have physical NICs.  

From reading through other posts etc, it seems as if this functionality may already be present in the windows version?

Thanks for all you hard work!  virtualbox is fantastic!

-Neil",Neil Broadbent
5349,traffic get answered on the wrong VLAN,VirtualBox 3.0.10,Windows,2009-10-30T18:44:54Z,2009-10-30T18:44:54Z,2009-10-30T18:44:54Z,"debian running in 3.0.10 virtualbox on windows, stacked vlan configured on eth2.400.4[[BR]]

second debian running in 3.0.10 virtualbox on windows, stacked vlan configured on eth2.400.4[[BR]]

you will notice on the tcpdump trace that requests are received in VLAN 400/VLAN4 (this is QinQ) but the response is sent on VLAN 4 which is not even configured on the box.

tcpdump [[BR]]

tcpdump -i eth2[[BR]]

tcpdump: verbose output suppressed, use -v or -vv for full protocol decode[[BR]]

listening on eth2, link-type EN10MB (Ethernet), capture size 96 bytes[[BR]]

15:33:47.584076 vlan 400, p 0, vlan 4, p 0, arp who-has 10.0.1.1 tell 10.0.1.2[[BR]]

15:33:47.614299 vlan 4, p 0, arp reply 10.0.1.1 is-at 08:00:27:f2:cd:a5 (oui Unknown)[[BR]]

15:33:48.566620 vlan 400, p 0, vlan 4, p 0, arp who-has 10.0.1.1 tell 10.0.1.2[[BR]]

15:33:48.566983 vlan 4, p 0, arp reply 10.0.1.1 is-at 08:00:27:f2:cd:a5 (oui Unknown)[[BR]]

15:33:49.549445 vlan 400, p 0, vlan 4, p 0, arp who-has 10.0.1.1 tell 10.0.1.2[[BR]]
[[BR]]
[[BR]]


setup:[[BR]]

apt-get install vlan[[BR]]

modprobe 8021q[[BR]]

vconfig add eth3 400[[BR]]

ifconfig eth3.400 up[[BR]]

vconfig add eth3.400 4[[BR]]

ifconfig eth3.400.4 up[[BR]]


",erik
5452,Auto detect active network interface,VirtualBox 3.0.10,other,2009-11-12T12:54:32Z,2009-11-12T12:54:32Z,2009-11-12T12:54:32Z,"If you have two network interfaces (wireless and wired), would be good that VirtualBox can detected which is currently active.
You can add a checkbox to Settings -> Network -> Name with the option ""Autodetect (On/Off)"".

I commend you for your great work.
Regards. ",fgm81
5624,PXE does not work with virtio,VirtualBox 3.1.0,Linux,2009-12-01T15:48:04Z,2009-12-01T18:53:54Z,2009-12-01T18:53:54Z,"Hello,

If virtio-net is used, PXE does not work. It fails with the error:

Unknown Ethernet controller! Aborting PXE boot...

The workarround is to revert to the old nic (intel/pcnet)",Luiz Angelo Daros de Luca
5652,Bridge network driver breaks host network DHCP,VirtualBox 3.1.0,Windows,2009-12-03T05:04:16Z,2009-12-03T05:06:41Z,2009-12-03T05:06:41Z,"Installing VirtualBox with the bridge network driver installed prevents the host machine from getting DHCP responses.  However, this issue only comes up after I reboot the host computer.  Here are the steps:

1.  Install VirtualBox.  Install completes successfully.  VMs run properly and can access the network.  Host networking works properly.  I can release my DHCP lease and acquire a new one successfully.

2.  Reboot the host computer.  Host is now unable to get DHCP responses and thus the IPv4 stack is not configured properly.  Interestingly, IPv6 is working properly.  The host is able to automatically configure its IPv6 address.

3.  Uninstall VirtualBox.  As soon as VB is uninstalled, the host gets the DHCP response and IPv4 works again.

I've had this issue since VB 3.0.10 at least.  I did not have the issue in 3.0.2.  I didn't install any versions between them.

Host is running Windows 7 Ultimate 64-bit.  It is an upgrade from Vista Ultimate 64-bit.  I had the same issue in Vista as well.  Several guests including Gentoo Linux and FreeBSD.  Although it doesn't appear to be a guest issue.

If I don't install the Bridge Network driver, I don't see the DHCP problem.  I did have Juniper Networks VPN installed.  I un-installed it, but it didn't help the problem.  I don't know if the un-install left any lingering drivers behind though.

I see from the DHCP server logs that the server is getting the DHCP query and is sending a response.  But the Windows box is clearly not getting the response.  Including 'ipconfig' output.",Ryan Moore
5489,high-bandwidth multicast traffic,VirtualBox 3.0.10,Linux,2009-11-17T16:30:27Z,2009-12-04T11:00:18Z,2009-12-04T11:00:18Z,"Hi!

When I generate a lot of multicast traffic (500mbps) from some host on the network to a virtual machine with a virtual e1000 (over the software network bridge), the network on my virtual machine hangs after a couple of seconds. All hosts (virtual and non-virtual) are running Debian Lenny. 
The physical host gives kernel stack traces in its kernel ring buffer that seem to be related. 

The physical host is a four-core Intel Core2 which can handle the multicast traffic in the host os. The virtual host is a four-core as well, with a virtual e1000. 

I will attach the kernel ring buffer log. ",Stefaan
6418,Microsoft NetworkLoadBalance unicast mode can't work on VirtualBox3.1.4(Linux version),VirtualBox 3.1.4,Linux,2010-03-25T03:14:41Z,2010-03-26T02:25:15Z,2010-03-26T02:25:15Z,"I use VB-3.1.4 to test the WIN2003 Network Load Balance, but I find it can't work on unicast mode, while the multi-cast mode can work fine. I tested the WIN2003 with the same configuration for unicast mode on vmware, and it works. I search the bug report for it, but there is no help. Is there some bugs on VB?

BTW: I use virtual box with non-root account.
",dwei
6514,Host only interfaces and DHCP servers show strange behavior,VirtualBox 3.1.6,Linux,2010-04-09T09:45:04Z,2010-04-09T10:00:59Z,2010-04-09T10:00:59Z,"I am using the PHP web api to create a few host only interfaces and dhcp servers for them. 

When I set them up properly the guest (Win XP) has no issues getting an IP from the dhcp server. However, any changes to the dhcp server configuration while the machine is running have no effect (I haven't tried using the cableConnected feature of the guest network adapter, but I disable/enable the connection from the guest so that should work). Those changes only appear after I stop and start the virtual machine, so maybe I am missing a neccessary step (note: restarting the guest w/o stopping the vm does not work either). 

An odd thing is that under no circumstances does the state of the dhcp server make any difference. Disabling the server by using the IDHCPServer::stop() function does not seem to stop the server. Or it could be that this is supposed to do something completely different, but I can't really tell since there is almost no information about it in the API docs.

Another issue I have is when trying to enable dynamic configuration on the host only interface. As far as I can understand enabling that will allow a dhcp server to give an address to the interface. But what I get when I call 
{{{
IHostNetworkInterface::enableDynamicIpConfig()
}}}
is this:

{{{
Fatal error: Uncaught SoapFault exception: [SOAP-ENV:Client] VirtualBox error: (0x0) in <...the stack trace..>
}}}
I get the same error when I try to call IHostNetworkInterface::dhcpRediscover(). All this could have something to do with the fact that there is no dhcp server that could handle the address allocation for these interfaces but there is nothing in the docs that explains how to add such s server.

Attempting to do all this using the CLI also got me nowhere because there is no info about the ''VBoxManage hostonlyif'' subcommand.

Am I missing something or is there something wrong here?",Sm0k1n
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
3990,VLAN support,VirtualBox 2.2.2,other,2009-05-11T14:02:13Z,2010-04-23T13:21:44Z,2010-04-23T13:21:44Z,"Hi,

It would be great that, Internal Networking mode at least, supports VLANs. This would avoid creating as many IntNets as needed (V)LANs wich, with a maximum number of 8, can be rapidly limiting.

You can look at the following post for a scenario.

http://forums.virtualbox.org/viewtopic.php?p=75416

Thank you for this great piece of software

Bests",Tarax
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
6576,Suggestion for improving the usermanual: Hostonly connection  should mention routing.,VirtualBox 3.1.6,Linux,2010-04-22T15:09:46Z,2010-05-04T14:14:20Z,2010-05-04T14:14:20Z,"I used virtualbox before version 2.0, and now I need it in a production case.

The guest will need to provide services to the outside world, and I need control through firewall/forwarding rules as to which ones it will be providing. Moreover, I cannot freely chose IP addresses and things like that (there is a shortage, you know. :-) ). 

Anyway, back in the old days I configured it in a way that the manual mentioned: ""difficult"", but for me it was a snap: IP routing is easy for me. So I now wanted to use something similar. The list of options for the guest network card is now larger than what I remember from the old days. So I read the section on networking, and couldn't find the option I  wanted. 

I tried a random few, and ended up with ""host only"", which I think should mention the option of using routing from the guest to the outside world. This would've made my experience with the new version a lot easier: I could've selected the right option right away. ",Roger Wolff
4934,Cannot start VM bridged to a VLANs when another VM bridged to another VLAN is already running,VirtualBox 3.0.4,Windows,2009-09-09T08:12:04Z,2010-05-24T12:31:28Z,2010-05-24T12:31:28Z,"Cannot start VM bridged to a VLANs when another VM bridged to another VLAN is already running.

Windows Vista Business 64bit host SP2

I have 3 VLANs on an Intel PRO/1000 MT Desktop Adapter lan card.
I have installed the Intel Proset drivers for the NIC v14.3
They enable me to have each VLAN with its own virtual NIC in the form of for example: Intel(R) PRO/1000 MT Desktop Adapter - VLAN : VLAN2018 (The only way to use VLAN in Windows I know of)
If I start a virtual machine bridged to one of the Virtual VLAN NICs it is OK, everything is working
I can also start more virtual machines bridged to the same Virtual VLAN NIC
But the problem is when I try to start a virtual machine bridged to a different Virtual VLAN NIC,
 while those VMs bridged to first Virtual VLAN NIC are still running.

I get a crash with message: VERR_INTNET_INCOMPATIBLE_TRUNK

I tried Virtual Box version 2.2.4-47978 and also latest beta 3.0.6_BETA1-51790 still the same
The only difference is that 2.2.4 locks up hard after a couple of VLAN crashes and I need to reboot my host.

For example:
start VM1 bridged to VLAN1 - OK
start VM2 bridged to VLAN1 - OK
start VM3 bridged to VLAN2 - CRASH!!!

Other example:
start VM1 bridged to VLAN1 - OK
start VM2 bridged to VLAN1 - OK
stop VM1 and VM2
start VM3 bridged to VLAN2 - OK
",Boris
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
6992,Add protections again DHCP rogue activity,VirtualBox 3.2.4,other,2010-06-14T11:27:50Z,2010-06-14T11:27:50Z,2010-06-14T11:27:50Z,"With certain guest OS setups, it is very easy for the VB DHCP servers to turn into rogues, answering DHCP requests from other physical computers on a LAN (potentially many on a huge LAN).  This is a very unpleasant phenomenon, potentially career-ending for the engineer in some environments.  

If there is any way so, by default, restrict VB DHCP servers such that not only would they only serve requests seen on Host-Only interfaces, but would ''only'' serve requests actually generated by interfaces associated with local guest VM's, it would be very helpful (seems like a quick MAC address check would be 99% of the solution).  That way, even confusing setups involving accidental guest OS bridging (e.g. Linux ""brctl"") between Host-Only and Bridged/NAT adapters would not cause LAN disasters.",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
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
7246,VLAN support for virtual adapters,VirtualBox 3.2.6,other,2010-07-28T17:00:47Z,2010-07-28T17:23:02Z,2010-07-28T17:23:02Z,In VMWare ESX you can add new NIC to virtual machine and give that virtual adapter it's own VLAN directly without configuring it in that virtual machine. This kind of feature should be in Virtual Box too.,raspi
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
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
6495,VBox DHCP Server does not respect client identifier,VirtualBox 3.1.6,other,2010-04-05T20:54:36Z,2011-01-11T19:19:37Z,2011-01-11T19:19:37Z,"VBox's build-in DHCP server does not respect the DHCP 'client identifier' option. Only the DHCP 'chaddr' field (typically the MAC address) is respected. 

Problem is that this is a violation of the DHCP protocol. (RFC 2131).
Below is an extract from the RFC where I've highlighted in bold what I think VBox does not implement:

    ""A DHCP server needs to use some unique identifier to associate a
    client with its lease. The client MAY choose to explicitly provide
    the identifier through the 'client identifier' option. If the client
    supplies a 'client identifier', the client MUST use the same 'client
    identifier' in all subsequent messages, and '''the server MUST use that
    identifier to identify the client'''. If the client does not provide a
    'client identifier' option, the server MUST use the contents of the
    'chaddr' field to identify the client. It is crucial for a DHCP
    client to use an identifier unique within the subnet to which the
    client is attached in the 'client identifier' option. Use of
    'chaddr' as the client's unique identifier may cause unexpected
    results, as that identifier may be associated with a hardware
    interface that could be moved to a new client. Some sites may choose
    to use a manufacturer's serial number as the 'client identifier', to
    avoid unexpected changes in a clients network address due to transfer
    of hardware interfaces among computers. Sites may also choose to use
    a DNS name as the 'client identifier', causing address leases to be
    associated with the DNS name rather than a specific hardware box.""


The current functionality of VBox's DHCP server creates problems for DHCP clients that for one reason or another sends a 'client identifier' as part of the DHCP negotiation and expects it to be respected over the 'chaddr' field.

My suspicion: VBox's DHCP server in its use of data structures seems to implement the BOOTP protocol rather than the DHCP protocol. (DHCP was invented as a successor to BOOTP in 1993). 


== How to implement: ==


Internally the DHCP Server should work with a unique lease identifier defined as follows (pseudo code):


{{{
If (! IsNull(DHCP-ClientIdentifier) )
  DhcpUniqueLeaseId = DHCP-ClientIdentifier
Else
  DhcpUniqueLeaseId = DHCP-chaddr
}}}



",lmanman2
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
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
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
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
8877,Ethernet frame larger than 1500 do no pass through bridged ethernet connection,VirtualBox 4.0.6,other,2011-05-11T18:53:35Z,2011-05-11T18:53:35Z,2011-05-11T18:53:35Z,Large ethernet frame (9000 bytes) are dropped when going through a virtual ethernet adapter even when the guest and host are configured for jumbo frame support.,Louis-Philippe Lessard
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
9147,"After upgrading to 4.0.10 from 4.0.8 on windows 7 host network connection is permenantly lost, icon replaced by vurtualbox adapter icon",VirtualBox 4.0.10,Windows,2011-07-02T15:11:58Z,2011-07-15T11:50:15Z,2011-07-15T11:50:15Z,Running Windows 7 on a Toshiba L755D latop with 6GB of RAM.  Upgraded from 4.0.8 to 4.0.10.  After the install could not connect to the internet from windows (via wireless).  The standard wireless network icon in the systems tray was replaced by an icon which was reported as virtualbox adapter.  Opened networking settings to try and connect manually to the wireless but the virtualbox adapter could not be removed or disabled and the normal wireless connection was disabled and would not re-enable.  Uninstalled 4.0.10 and regressed to 4.0.8.,setheridge
9970,DHCP gateway option,VirtualBox 4.1.6,other,2011-11-29T17:23:24Z,2011-11-29T17:23:24Z,2011-11-29T17:23:24Z,"(OSX Lion / 4.1.6)

If would be useful if the built-in DHCP server on Host-only Networking could allow you to set a DHCP Gateway option. This would allow you easy to point guests at another VM as a way out of the network.

(Workaround: run a DHCP server in another VM on the same Host-only Network segment)",Brian Candler
9971,Persistent DHCP database,VirtualBox 4.1.6,other,2011-11-29T17:26:26Z,2011-11-29T17:26:26Z,2011-11-29T17:26:26Z,"(OSX Lion, VBox 4.1.6)

It would be useful if the VBox DHCP server for Host-only Networking keep a persistent database of MAC address to IP address assignments, so that when you start the VMs later they get the same IP addresses, independent of the order you start them in.

(Workaround: run a DHCP server in another VM)
",Brian Candler
9972,Connection sharing for host-only networking,VirtualBox 4.1.6,Mac OS X,2011-11-29T17:37:22Z,2011-12-09T16:34:25Z,2011-12-09T16:34:25Z,"VBox under OSX offers these networking choices:

* Host-only networking, where the guests can see each other and the host, but cannot reach the Internet

* NAT, where the guest can make outbound connections to the Internet, but is not reachable from other guests or the hosts (except by means of port forwarding)

This means that if you want guests to form a local network but also be able to download updates from the Internet you need to configure them with two NICs, one of each type. Or else you can set up another VM as a gateway running IP masquerading, but to use this you need to set an explicit default gateway on each of the other guests.

It would be very useful if Host-only networking could allow outbound connections via the Host using NAT. For Linux this would probably just require an iptables rule. In the case of OSX, I think the cleanest way to do this would be to expose the vboxnet interfaces in the Internet Sharing settings (System Preferences > Internet and Wireless > Sharing > Internet Sharing). It would also be necessary to return a gateway in the DHCP response (see #9970)
",Brian Candler
10212,Problem with DNS lookups (NAT),VirtualBox 4.1.8,other,2012-02-04T17:43:53Z,2012-02-04T18:04:02Z,2012-02-04T18:04:02Z,"NAT network adapter

Running the following shell script on a Debian VM causes DNS lookups to timeout after ~15s of execution

Script:
{{{
while [ 1 ]; do nslookup google.pl; done
}}}

The error is:
{{{
;; connection timed out; no servers could be reached
}}}

It doesn't occur with bridged adapter.
It occurs on all network adapter types (i.e. Intel, PCnet, virtio-net) available in VirtualBox.

Tested on:

Windows 7 host - VirtualBox 4.1.6, 4.1.8

Debian host - VirtualBox 4.1.4
",DragMZ
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
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
11017,Outdated SMBIOS version,VirtualBox 4.2.0,other,2012-10-03T12:25:20Z,2013-06-04T07:19:12Z,2013-06-04T07:19:12Z,"Currently (Version 4.2.0), SMBIOS Version 2.5 is provided, the currently available specification (from 2011) is 2.7.1. Versions < 2.6 cause problems when used with the new consistent network interface naming of RHEL/CentOS 6/Fedora based on biosdevname since information about network devices is missing (types 9 and 41 of SMBIOS specification).",29erpete
12174,Configure internal DHCP server to pass arbitrary domains,VirtualBox 4.2.18,other,2013-10-10T12:32:39Z,2013-10-10T13:25:31Z,2013-10-10T13:25:31Z,"Hi, 

virtualbox uses it's own internal DHCP server if the network interface type of a VM is set to 'NAT'. 

Unfortunaly I was unable to make VB's DHCP to offer any domain name. Although VBoxManage supports a --natdnspassdomain option, this can just turn domain passing on and off, and did not have any effect. I did not find a hint in the manual, where VB takes the domain from it is supposed to pass through. 

Would be quite useful if VB would allow to just configure which domain name is to be passed by the internal DHCP server to the VM. So one could set any random default domain. 

regards
",DerHadmut
13169,[feature-request] Network: Promiscuous mode for NAT,VirtualBox 4.3.12,all,2014-07-06T10:28:06Z,2014-07-16T13:52:52Z,2014-07-16T13:52:52Z,"Hi,

I have 2 VMs with SSH servers on my host. I use user-space NAT. Host has IP: 192.168.4.82

I would like to be able to make a NAT route from a different host IP, like 192.168.4.201 and x.x.4.202 for those 2 VMs. I would be nice if VirtualBox NAT router could enter into ""promiscuous mode"" and allow the host listening on custom addresses (similar to what WinPCAP/libpcap and Wireshark do).

Today I have to use non-standard ports for this. Like:  

VM1:

Rule 1 | TCP | [blank host IP] | host port = 1001 | [blank guest IP] | Guest Port = 22

VM2:

Rule 1 | TCP | [blank host IP] | host port = 1002 | [blank guest IP] | Guest Port = 22

I would like to achieve this:

VM1:

Rule 1 | TCP | 192.168.4.201 | host port = 22 | [blank guest IP] | Guest Port = 22

VM2:

Rule 1 | TCP | 192.168.4.202 | host port = 22 | [blank guest IP] | Guest Port = 22

-Alexey Eromenko ""Technologov"", 6.July.2014",Technologov
8564,WiFi network adapter,VirtualBox 4.0.4,Windows,2011-03-14T23:26:21Z,2014-08-15T23:28:14Z,2014-08-15T23:28:14Z,"Currently there are only wired network adapters available. A wireless adapter should be available too.

Some WiFi networks need a certificate to gain access. This certificate may (sometimes) only be installed IF a WiFi network is present and active on the (guest) server.

To allow for the VM guest to gain full access to a certificate controlled WiFi network, even thou the VM host does not, the VM guests need a network adapter of type WiFi.

",dum
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
13433,For pyTivo with Python 2.7.8 the network traffic is being modified somehow on the Host,VirtualBox 4.3.16,Windows,2014-09-25T03:43:57Z,2014-10-11T19:01:30Z,2014-10-11T19:01:30Z,"I've been using pyTivo and VirtualBox on the same host for a long time. It worked fine until I upgraded from 4.3.12 to 4.3.16. There were no errors produced, but my TiVo could not access pyTivo. I downgraded back to 4.3.12 and pyTivo started working again. Not really sure what log files I could produce to demonstrate the problem. I do not see any errors in any of the Windows log files and pyTivo shows no problems. I can only surmise that it is some sort of networking issue. However I can still access the web address for the program, http://pytivohost:9032, from another computer. Only my TiVo cannot access it.

I'm running Windows 7 Home Premium 64-bit with 16GB of RAM. Not particularly relevant, but my guests are also Windows 7 64-bit. The problem exists whether any guests are running or not.",Steven Wilson
12063,Using Windows 8.1 RTM and Virtualbox 4.2.16 with bridge networking component installed results in shutdown and sleep problems,VirtualBox 4.2.16,Windows,2013-09-03T07:29:07Z,2014-11-29T22:11:23Z,2014-11-29T22:11:23Z,"Using Windows 8.1 RTM single language (English, activated with serial provided with PC) and Virtualbox 4.2.16 with bridge networking component installed results in shutdown and sleep problems. The display becomes dim and HDD spins down (on notebook) but the power led is on and coolers continue to work.
Changing drivers for network cards, video, motherboard, etc doesn't help.
Reinstalling Virtualbox with bridge networking switched off (NAT is on) helps to completely resolve the issue.
Devices used: HP envy 4 touchsmart, Acer iconia tab w700.",Immunologist
12369,NAT Network -  DHCP problem: no DNS,VirtualBox 4.3.2,Windows,2013-11-17T23:47:23Z,2014-12-02T12:33:10Z,2014-12-02T12:33:10Z,"Postby petardo » 17. Nov 2013, 03:20
I am using the ""NAT NETWORK"" Network Adapter.
I have found a DHCP SERVER problem:
IF
- DHCP SERVER is enabled in the file / preferences / network / nat network section,
- and NAT NETWORK is selected as natwork adapter for the guest
==> NO DNS values get forwarded to the guest",petardo
13678,Networking Still Works After Not Installing,VirtualBox 4.3.20,other,2014-12-10T08:36:05Z,2014-12-10T11:15:37Z,2014-12-10T11:15:37Z,"During installation it's possible to opt out of installing VirtalBox's networking features. However, despite this, it's still possible for VMs to connect to the host's network via NAT under the networking tab within its settings.

For the purposes in which the VM is to be used, I don't want it to be possible for the user to connect to the network/internet in any shape or form. I have tried this on both the stable, and the test version of VirtualBox (4.3.21).",Pearson.S2
13743,NAT: port forwarding issues / collision,VirtualBox 4.3.18,other,2015-01-07T11:28:33Z,2015-01-07T11:28:33Z,2015-01-07T11:28:33Z,"Host: Windows 7, Core i7, VBox 4.3.18

Guests: Linux, RHEL6 (CLI-only)

Setup localhost + 2 web servers VMs.

VM1: NAT host@1443 -> guest:443 (default 10.0.2.15 IP)

VM2: NAT host@2443 -> guest:443 (default 10.0.2.15 IP)

I connect by typing in local web browser:
https://localhost:1443

When I connect via HTTPS to first VM, it's okay, but when I connect to
second VM, the first one disconnects (connection timeout), and then I
get access to 2nd VM, and after I try to reconnect to 1st VM, 2nd VM
immediately disconnects, so there is some collision between NAT engine
on both VMs.

No way to connect to both VMs, from localhost web browser.

Not sure why this happens, as SLIRP NAT module is supposed to be
user-space, per-VM process.

I also ensured, that MAC addresses were different in 2 VMs.

--

-Alexey Eromenko ""Technologov"", 07.Jan.2015",Technologov
13832,VirtualBox 4.3.22 Breaks Physical Network Card Config,VirtualBox 4.3.22,Windows,2015-02-13T18:11:52Z,2015-02-13T18:11:52Z,2015-02-13T18:11:52Z,"

I'm having the same problem with VirtualBox 4.3.22 for Windows on Windows 7 Pro 64 Bit patched as of today. After virtual box install it disabled eth0 (first NIC) and I have no networking at all. From the command line it looks like the bridged network is being assigned to the physcial interface and that breaks connectivity.

I had to log in as Admin and disable and reenable both interfaces for it to sort of work. Not it keeps putting the card off line and online. Not sure how this bug reared its ugly head so often but it has.
",evit
11183,Nonexistent host networking interface,VirtualBox 4.2.4,Windows,2012-11-09T11:15:50Z,2015-02-23T08:06:03Z,2015-02-23T08:06:03Z,"The following error message is displayed when restoring a VM from a Saved state:


{{{
Failed to open a session for the virtual machine [VM NAME].

Nonexistent host networking interface, name 'Atheros AR8131 PCI-E Gigabit Ethernet Controller (NDIS 6.20) #2' (VERR_INTERNAL_ERROR).

Result Code: E_FAIL (0x80004005)
Component: Console
Interface: IConsole {db7ab4ca-2a3f-4183-9243-c1208da92392}
}}}


This occurs when the following is performed:

1. VM is running fine, and in Bridged networking mode connected to the LAN network interface. This interface is connected to a wireless router
2. The VM state is saved
3. Host is put to sleep
4. Wireless router is unplugged
5. Host is woken up
6. A different network device, in this case a network hub is plugged into the LAN
7. The VM is started again, and the error appears

The workaround is to delete the savestate and start the VM again.

For interest, the VM is Windows 2012 with 8GB RAM, 2 CPUs and apart from Shared Folders there is nothing fancy configured.

This behaviour does occur for all OSs and configurations.

I would assume this has something to do with when a network interface is disabled and enabled again, it adds ""#2"", ""#3"" next to it. Note, though that no setting in the Host (in Windows 7) shows that the network interface has been renamed, this appears to be the internal NIC name.",georgeby
13733,VBoxNetFlt.sys v4.3.20 BSOD “DRIVER_POWER_STATE_FAILURE” when hibernate/shutdown WIN7,VirtualBox 4.3.20,Windows,2015-01-05T09:01:24Z,2015-03-01T11:01:59Z,2015-03-01T11:01:59Z,"I randomly (but often) get a BSOD ({{{DRIVER_POWER_STATE_FAILURE}}}) when I hibernate or shutdown my laptop (Windows 7 Home Premium).

I first get a black screen during about 10 minutes then I get the following BSOD.

I already got this issue randomly with previous versions of VirtualBox and I thought it was fixed when reinstalling a new version…

analyze -v output:
{{{
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

DRIVER_POWER_STATE_FAILURE (9f)
A driver has failed to complete a power IRP within a specific time.
Arguments:
Arg1: 0000000000000003, A device object has been blocking an Irp for too long a time
Arg2: fffffa8005572700, Physical Device Object of the stack
Arg3: fffff80000b9c518, nt!TRIAGE_9F_POWER on Win7 and higher, otherwise the Functional Device Object of the stack
Arg4: fffffa800feaa0a0, The blocked IRP

Debugging Details:
------------------


DRVPOWERSTATE_SUBCODE:  3

IMAGE_NAME:  ntkrnlmp

DEBUG_FLR_IMAGE_TIMESTAMP:  0

MODULE_NAME: ntkrnlmp

FAULTING_MODULE: fffff88010200000 VBoxNetFlt

IRP_ADDRESS: fffffa800feaa0a0

DEVICE_OBJECT: fffffa8007771050

DRIVER_OBJECT: fffffa8007756e70

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  WIN7_DRIVER_FAULT

BUGCHECK_STR:  0x9F

PROCESS_NAME:  System

CURRENT_IRQL:  2

ANALYSIS_VERSION: 6.3.9600.17029 (debuggers(dbg).140219-1702) amd64fre

DPC_STACK_BASE:  FFFFF80000BA2FB0

STACK_TEXT:  
fffff800`00b9c4c8 fffff800`0354c8d2 : 00000000`0000009f 00000000`00000003 fffffa80`05572700 fffff800`00b9c518 : nt!KeBugCheckEx
fffff800`00b9c4d0 fffff800`034e785c : fffff800`00b9c600 fffff800`00b9c600 00000000`00000000 00000000`00000001 : nt! ?? ::FNODOBFM::`string'+0x33af0
fffff800`00b9c570 fffff800`034e76f6 : fffffa80`0e88fc58 fffffa80`0e88fc58 00000000`00000000 00000000`00000000 : nt!KiProcessTimerDpcTable+0x6c
fffff800`00b9c5e0 fffff800`034e75de : 000001b6`a883467f fffff800`00b9cc58 00000000`00b847c0 fffff800`0365ba88 : nt!KiProcessExpiredTimerList+0xc6
fffff800`00b9cc30 fffff800`034e73c7 : 00000060`dc5662c2 00000060`00b847c0 00000060`dc56620f 00000000`000000c0 : nt!KiTimerExpiration+0x1be
fffff800`00b9ccd0 fffff800`034d48ca : fffff800`03657e80 fffff800`03665cc0 00000000`00000001 fffff880`00000000 : nt!KiRetireDpcList+0x277
fffff800`00b9cd80 00000000`00000000 : fffff800`00b9d000 fffff800`00b97000 fffff800`00b9cd40 00000000`00000000 : nt!KiIdleLoop+0x5a


STACK_COMMAND:  kb

FOLLOWUP_NAME:  MachineOwner

IMAGE_VERSION:  

FAILURE_BUCKET_ID:  X64_0x9F_3_POWER_DOWN_IMAGE_ntkrnlmp

BUCKET_ID:  X64_0x9F_3_POWER_DOWN_IMAGE_ntkrnlmp

ANALYSIS_SOURCE:  KM

FAILURE_ID_HASH_STRING:  km:x64_0x9f_3_power_down_image_ntkrnlmp

FAILURE_ID_HASH:  {11a584ac-cfbe-b229-0d33-15c5fd69f706}

Followup: MachineOwner
---------

0: kd> lmvm VBoxNetFlt
start             end                 module name
fffff880`10200000 fffff880`1022b000   VBoxNetFlt T (no symbols)           
    Loaded symbol image file: VBoxNetFlt.sys
    Image path: \SystemRoot\system32\DRIVERS\VBoxNetFlt.sys
    Image name: VBoxNetFlt.sys
    Timestamp:        Mon Nov 24 12:06:09 2014 (54731121)
    CheckSum:         000271EA
    ImageSize:        0002B000
    Translations:     0000.04b0 0000.04e4 0409.04b0 0409.04e4
}}}
",lorcan
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
13947,bridged networking broken for Windows 8.1 guest,VirtualBox 4.3.24,Linux,2015-03-09T21:20:21Z,2015-03-12T14:13:44Z,2015-03-12T14:13:44Z,"The windows 8.1 guest diagnostics don't see a problem with the bridged connection, but web browsers are unable to connect to any URL. If the adapter (Intel Pro 1000 desktop) is set to NAT in the Linux host then the connection is ok (browsers are able to connect). This problem also existed for version 4.3.18. Windows 7 guests do not have this problem.",nbi
14027,VMs with bridged network do not start,VirtualBox 4.3.26,other,2015-04-05T23:46:40Z,2015-04-09T09:06:05Z,2015-04-09T09:06:05Z,"I have created a forum thread that did not draw enough attention: https://forums.virtualbox.org/viewtopic.php?f=6&t=64797&p=317689#p317689

But the problem still exists.

It's a clear installation of a virtualbox 4.3.26 on my machine. I had 4.3.18 before, which was uninstalled before I installed and the whole laptop was rebooted.
And yes this time I installed 4.3.26 USING run-as-admin item (which did not change anything)

",zerkms
14049,VirtualBox NAT implementation tcp keep-alive problem,VirtualBox 4.3.10,Windows,2015-04-14T21:59:14Z,2015-04-15T13:25:24Z,2015-04-15T13:25:24Z,"Guests behind VirtualBox NAT have problem using TCP keepalive.
When connection with remote is lost (i.e. even host OS reports no connection), VirtualBox NAT implementation continues to reply to guest OS keepalive requests, hence guest cannot detect TCP connection loss.[[BR]]

Encountered on:
Host OS: Windows 7 Professional 64
VirtualBox 4.3.10
Guest OS: Ubuntu 12.04 32

The same problem was reported by two users on the forum: https://forums.virtualbox.org/viewtopic.php?f=7&t=52384
",Aegis
14050,Bugcheck (BSOD) 0x0000009f (0x00000003) on wakeup with InstantGo,VirtualBox 4.3.26,Windows,2015-04-15T19:43:46Z,2015-04-15T19:43:46Z,2015-04-15T19:43:46Z,"Hi, 
After installing the latest stable x86 version on a Z3735 tablet with Windows 8.1,
I experience recurring bluescreens/reboots when the machine is trying to wake up. Since this Atom class CPU is setup with InstantGo/Connected standby, I suspect that this may be the root cause.

The bugcheck and event log entries point to a problem reinitializing the virtual network adapter on wakeup.

I tried uninstalling Virtualbox and after that,the crashes did not appear anymore.

Device: Pipo W5
CPU: Intel Z3735
RAM: 2 GB
OS: Windows 8.1 x86

",andersl
14061,VBoxManage CLI Support for configuring DNS server settings of the VirtualBox Host-Only Network adapters,VirtualBox 4.3.26,all,2015-04-20T16:47:10Z,2015-04-20T16:51:28Z,2015-04-20T16:51:28Z,"Currently, when I create a VirtualBox Host-Only Network adapter, the DNS settings are essentially empty. (See {{{VirtualBox Host-Only Network #3}}} below). For Windows hosts, one would have to manually follow the steps [http://windows.microsoft.com/en-us/windows/change-tcp-ip-settings#1TC=windows-7 described here] in order to configure this adapter to point to a DNS server (See {{{VirtualBox Host-Only Network #2}}}).

Functionality should be added to the network provisioning portion of the VBoxManage CLI which facilitates creating a network adapter with a DNS server. Without this functionality, the automatic provisioning of nameservers inside VirtualBox guest machines is not possible.

{{{
Ethernet adapter VirtualBox Host-Only Network #2:

   Connection-specific DNS Suffix  . :
   Description . . . . . . . . . . . : VirtualBox Host-Only Ethernet Adapter #2
   Physical Address. . . . . . . . . : 08-00-27-00-98-93
   DHCP Enabled. . . . . . . . . . . : No
   Autoconfiguration Enabled . . . . : Yes
   IPv4 Address. . . . . . . . . . . : 192.168.99.1(Preferred)
   Subnet Mask . . . . . . . . . . . : 255.255.255.0
   Default Gateway . . . . . . . . . :
   DNS Servers . . . . . . . . . . . : 192.168.99.103
   NetBIOS over Tcpip. . . . . . . . : Enabled
}}}

{{{
Ethernet adapter VirtualBox Host-Only Network #3:

   Connection-specific DNS Suffix  . :
   Description . . . . . . . . . . . : VirtualBox Host-Only Ethernet Adapter #3
   Physical Address. . . . . . . . . : 08-00-27-00-68-27
   DHCP Enabled. . . . . . . . . . . : No
   Autoconfiguration Enabled . . . . : Yes
   IPv4 Address. . . . . . . . . . . : 192.168.86.1(Preferred)
   Subnet Mask . . . . . . . . . . . : 255.255.255.0
   Default Gateway . . . . . . . . . :
   NetBIOS over Tcpip. . . . . . . . : Enabled
}}}",PhilG
13104,Network issues on OS X 10.10 Yosemite,VirtualBox 4.3.12,Mac OS X,2014-06-06T15:33:43Z,2015-04-21T05:39:58Z,2015-04-21T05:39:58Z,"I'm having trouble with guest network connectivity with Virtualbox 4.3.12r93733 running on OS X 10.10 Yosemite build 14A238x. There seem to be two issues with a Ubuntu Trusty VM i created using vagrant:

- Network connections (e.g. ssh sessions) to the VM keep hanging for 1-2min. When typing in ssh sometimes the shell is unresponsive for a couple of minutes.
- Network connections from the VM to the internet fail often (~50% ping drop), also this problem happens: http://stackoverflow.com/questions/24060099/docker-failed-to-pull-images-from-registry

I've tried: Restarting host / guest, recreating the VM, playing around with network settings (although I don't know much about that).

Let me know if you need any more details, I'm happy to help anyway I can.",lclemente
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_
13744,Windows 7 guest can't connect to the Internet - host Wifi/guest bridged network adapter,VirtualBox 4.3.20,Linux,2015-01-07T12:50:18Z,2015-04-28T05:00:39Z,2015-04-28T05:00:39Z,"Virtualbox: 4.3.20
Hosts: Ubuntu 14.04, 14.10, 15.04
Guest: Windows 7 Pro; network adapter: Tested all, including Virtio
VM Network connection: Bridged

I have a Windows 7 guest (VM) installed in VirtualBox host running Ubuntu 14.04. Other users have experienced this in hosts running Ubuntu 14.10 and 15.04 too. 

This is on a laptop so I have two networking adapters. 

The VM's internet access works fine if I activate the ethernet adapter on the host, regardless of the VM's NAT or Bridged connection type. 

When the host's active Internet connection is Wireless then the VM's internet access only works in NAT mode.  In bridged mode, the guest obtains an IP address, but can’t connect to the Internet.

I need to use the Bridged connection type in order to participate in the LAN's native IP network, not a host's NAT network. Thanks for any help in advance.

Similar bug tickets:
#12408
#11254
",Pedro Serrano
13785,OS X Guest with Bridged Networking cannot obtain DHCP lease - guest actively DHCPDECLINEs due to host activity,VirtualBox 4.3.20,other,2015-01-25T12:38:06Z,2015-04-28T05:04:29Z,2015-04-28T05:04:29Z,"Host: OS X Yosemite 10.10.1
VirtualBox: 4.3.20
Guest: CentOS 6.4

I have configured an OS X VirtualBox guest with a primary interface as NAT, a private network secondary, and a tertiary interface as Bridge Networking with DHCP. I have bridged to my Airport Wi-Fi adapter.

When the machine boots it nearly always fails to obtain an IP address for the bridged interface. In rare cases it will actually succeed. Retrying it will eventually work though rarely (run it 100 times in a loop maybe.)

Running dhclient -v eth2 shows the guest is declining the IP offer when it fails:
{{{
[root@localhost ~]# dhclient -v eth2
Internet Systems Consortium DHCP Client 4.1.1-P1
Copyright 2004-2010 Internet Systems Consortium.
All rights reserved.
For info, please visit https://www.isc.org/software/dhcp/

Listening on LPF/eth2/HI:DD:EN:HI:DD:EN
Sending on   LPF/eth2/HI:DD:EN:HI:DD:EN
Sending on   Socket/fallback
DHCPDISCOVER on eth2 to 255.255.255.255 port 67 interval 5 (xid=0x2bc89bf5)
DHCPOFFER from 192.168.0.1
DHCPREQUEST on eth2 to 255.255.255.255 port 67 (xid=0x2bc89bf5)
DHCPACK from 192.168.0.1 (xid=0x2bc89bf5)
DHCPDECLINE on eth2 to 255.255.255.255 port 67 (xid=0x2bc89bf5)
}}}
This seems to be because it sees the IP as already existing - though it doesn't. I modified /sbin/dhclient-script to show the arping output like this:
{{{
        arping -D -c2 -I ${interface} ${new_ip_address}
        RC=$?
        echo ""Exit: $RC""
        [ $RC -ne 0 ] && exit_with_hooks 1
}}}
Interestingly, if I didn't exit and let it run its own arping afterwards - it would always succeed. More on that shortly.

Output is below:
{{{
[root@localhost ~]# dhclient -v eth2
Internet Systems Consortium DHCP Client 4.1.1-P1
Copyright 2004-2010 Internet Systems Consortium.
All rights reserved.
For info, please visit https://www.isc.org/software/dhcp/

Listening on LPF/eth2/HI:DD:EN:HI:DD:EN
Sending on   LPF/eth2/HI:DD:EN:HI:DD:EN
Sending on   Socket/fallback
DHCPDISCOVER on eth2 to 255.255.255.255 port 67 interval 5 (xid=0x2bc89bf5)
DHCPOFFER from 192.168.0.1
DHCPREQUEST on eth2 to 255.255.255.255 port 67 (xid=0x2bc89bf5)
DHCPACK from 192.168.0.1 (xid=0x2bc89bf5)
ARPING 192.168.0.149 from 0.0.0.0 eth2
Broadcast request from 192.168.0.149 [HI:DD:EN:HI:DD:EN] for 192.168.0.1 [00:00:00:00:00:00] 1.163ms
Sent 1 probes (1 broadcast(s))
Received 1 response(s) (1 request(s), 1 broadcast(s))
Exit: 1
DHCPDECLINE on eth2 to 255.255.255.255 port 67 (xid=0x2bc89bf5)
}}}
Arping detects a broadcast request coming from the IP it just allocated... the Mac address there is the HOST's MAC address. So something on the host sends this request from the allocated IP, and arping here catches it and fails duplicate address detection, meaning dhclient declines the address.

Weirdly, if I precede the dhclient-script arp check with a sleep 2 instead of the debug lines above - it never works. Replace it with just a single arping command, it works every time. Seems something is happening on the host in response to the FIRST arp check. So the first fails, and the second arp check succeeds (though normally there is only one check - it's just in my debugging I stumbled on it.)

Any ideas what is causing this request from the host? Is it a VirtualBox thing or a OS X thing? Any possible fix?",Jason Woods
14127,No bridged network adapter is currently selected,VirtualBox 4.3.26,Windows,2015-05-17T02:22:10Z,2015-05-17T06:51:23Z,2015-05-17T06:51:23Z,"Windows 7, 64 bit., VirtualBox 4.3.26.

When adding a bridged network adapter to any virtual machine while running virtual box as normal user, the selection for network interfaces is empty. It also states: ""No bridged network adapter is currently selected"":

[[Image(bridge-empty.png)]]

When I run VirtualBox as admin, it works as expected.

The VirtualBox networking driver is setup and installed properly and is enabled for all network interfaces. Example shown here:

[[Image(vbox_driver_interface.png)]]

I found some references to exactly this kind of issue but it seems that the problem is something different in my case because all the workarounds did not work, including:

* Reinstallation of VirtualBox, rebooting, ...
* Delete HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Network\Config, reboot, re-install VirtualBox
* Set a higher value to HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Network\MaxNumFilters (I Use 0x20), reboot, reinstall etc.

",divB
14129,No Internet Connection under Host Only / NAT: DHCP,VirtualBox 4.3.28,Mac OS X,2015-05-17T15:47:11Z,2015-05-17T18:08:32Z,2015-05-17T18:08:32Z,"Hello Guys,

I am currently using VirtualBox 4.3.28 r100309 on Mac OS X Yosemite 10.10.3. My guest OS is Ubuntu Server 14.04.2.

I setup two network interfaces: Adapter 1 ""NAT"" and Adapter 2 ""Host-only"". Thus, the machine should have access to the internet (NAT) and I should have access to the virtual machine from my Mac without port forwarding (Host-only).

In the previous versions of VirtualBox I had not that problem, but right now I cannot access to internet through my guest machine. If I set just one network interface using the Bridged Adapter I can access to internet in my guest machine, but I want to use an static ip due to I do not want my ip address changes everytime I change my network in the host machine, like when I change the wifi for example.

Can someone help me please?",vihuvac
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
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
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
13149,VirtualBox installation on Windows 8.1 with InstantGo issues,VirtualBox 4.3.12,Windows,2014-06-27T21:01:19Z,2015-06-05T19:31:52Z,2015-06-05T19:31:52Z,"When you install Oracle VirtualBox x64 (latest version) on a Surface Pro 3 that supports InstantGo, when the computer goes to sleep, most of the time when the computer awakes, the base Surface wireless device won't load on the host system. I've been able to reproduce the problem by doing a factory reset on my Surface Pro 3 and installing it. The problem manifests itself immediately after the VirtualBox installation. This is a major problem, because without the wireless driver, the computer can no longer connect to the Internet or access network resources on both the host system and guest OS.",JHumenik
14189,Port forwarding silently fails when source ports are privileged,VirtualBox 4.3.28,Linux,2015-06-09T21:21:38Z,2015-06-09T23:38:27Z,2015-06-09T23:38:27Z,"I just spent a really unproductive hour or so trying to work out why I was getting ""Connection refused"" from a test LDAP server in a VM.

Then I resorted to trying to forward the port using SSH. The SSH client reminded me that privileged ports cannot be forwarded unless you're root. (Oh yeah, Unix. Privileged ports. I remember now.)

So my suggestion is:

 - The VirtualBox GUI should warn the user about this.

 - There should be an error displayed if port forwarding fails because the port is privileged.

The documentation at https://www.virtualbox.org/manual/ch06.html mentions the limitation, but it states that the VM will refuse to start in such a situation. That doesn't appear to be true -- I tried restarting the VM and didn't get a useful error message.",meta
14213,NAT networking stops responding blocks all I/O on that interface for Ubuntu/Debian x64 guests,VirtualBox 4.3.28,Windows,2015-06-19T18:21:50Z,2015-06-19T23:06:42Z,2015-06-19T23:06:42Z,"= Summary =
I can reproduce almost 100% this fault, which seems to affect Virtualbox versions 4.3.x in both Windows 8.1 and Windows 10 using ubuntu 14.04.2 or debian Jessie guests.

I attached a script, which pings a well known site once a second that you can run to show the precise moment at which networking stops responding. You may use this script or any tool you like for this. For the purposes of the bug description I will assume you are using the embedded script.

= Repro steps to detect fault =

1. Make sure you have a standard NAT based single interface ubuntu guest running.
2. Log-in to guest.
3. Install either google chrome (triggers fault immediately) or chromium-browser (ubuntu) or chromium (debian jessie) which trigger very often but not 100% of the time. Install google-chrome using the following snippet:

{{{
wget -q -O - https://dl-ssl.google.com/linux/linux_signing_key.pub | sudo apt-key add - 
echo ""deb http://dl.google.com/linux/chrome/deb/ stable main"" | sudo tee /etc/apt/sources.list.d/google-chrome.list
sudo apt-get -yqq update
sudo apt-get install -yqq google-chrome-stable
}}}


4. Start embedded script to monitor network, access.
{{{
Expected result: It should be possible to ping well known address, the
 result should be something along these lines:
...
1 packets transmitted, 1 received, 0% packet loss, time 0ms
...
}}}

5. Start chromium browser from UI and try to access google.com or any address.

{{{
Result: Scripts start showing that network access is broken. Lines like
the following one show in script after a small delay where everything is
frozen:
...
1 packets transmitted, 0 received, 100% packet loss, time 0ms
...

Result 2: Virtualbox process in Windows becomes unresponsive and unstable,
cannot be easily stopped, may turn windows blank as hung processes show.

}}}
 
{{{
Expected result: Network access should work normally, no disruptions.
}}}

= Script to trigger fault =

For repro steps I used:
{{{
./net_tester.sh -x
}}}

{{{
$ cat net_tester.sh 
#!/bin/bash

function usage()
{

  cat <<eof

Usage: $(basename $0) [-x] [-h] [output log file]

The purpose of this script is to check network reliability of Virtualbox

Options:

-x, --external  Uses the google DNS to ping instead of NAT gateway address.
-h, --help      This message.

eof
  exit 1
}

#
# Change the following line to the address of the NAT gateway.
#
ping_address=10.0.0.2
out_file=out.log

while [ ""$1"" != """" ]
do
  case ""$1"" in
  -h|--help) usage ;;
  -x|--external) ping_address=8.8.8.8 ;;
  *) out_file=$1 ;;
  esac
  shift
done

while :
do
  date
  ping -c 1 ${ping_address}
  sleep 1
done | tee ${out_file}

}}}

",Coffee_fan
13866,Provide useful output when host interface for bridge is no longer available,VirtualBox 4.3.22,other,2015-02-20T02:09:39Z,2015-06-22T23:25:16Z,2015-06-22T23:25:16Z,"If a VM has been setup to use eth1 of the host, the host shutdown, the interface exchanged and rebooted, then `VBoxManage startvm ""[name]"" --type headless` results in 

    Waiting for VM ""Ubuntu-12.04.5-i386"" to power on...
    VBoxManage: error: Failed to open/create the internal network 'HostInterfaceNetworking-eth1' (VERR_INTNET_FLT_IF_NOT_FOUND).
    VBoxManage: error: Failed to attach the network LUN (VERR_INTNET_FLT_IF_NOT_FOUND)
    VBoxManage: error: Details: code NS_ERROR_FAILURE (0x80004005), component Console, interface IConsole

which could easily replaced with an understandable and helpful error message.",krichter
14197,can not install bridged interfaces on W7-64 Pro,VirtualBox 4.3.28,Windows,2015-06-16T00:53:20Z,2015-06-28T00:38:11Z,2015-06-28T00:38:11Z,"Documented in this thread:

https://forums.virtualbox.org/viewtopic.php?f=6&t=68293&sid=bf442681877c87e603508a1aa2a0fb11

Hi there....readers digest. Dell replaced my M4800 laptop due to many different issues. The original is dual quad core intel core i7-4800MQ @ 2.7 Ghz, 8gb ram, 512mb hybrid drive, dual video processors Intel HD4600 and nVidia. Intel is default. Intel I217-LM ethernet adapter. Virtualbox installed normally but never got to run anything yet. 

new laptop is still a M4800 dual quad core I7-4810MQ @ 2.8 Ghz, 32gb ram, 512MB SSD + 512MB SATA drive. NVidia Quadro  K1100M is the other graphics processor. Same ethernet adapter.

I've attached a log from a failed attempt to install full product.

I need the bridged adapter.

Please help. If you need anything else, please let me know.

Thanks leon

",Leon Zetekoff
14212,(ipv6) multicast NS are not delivered to the guest,VirtualBox 4.3.28,Windows,2015-06-19T11:56:51Z,2015-07-16T13:48:05Z,2015-07-16T13:48:05Z,"It seems that the guest doesn't receive (ipv6) multicast neighbor
solicitations from the router.",Maarten Hoes
13546,Support virtual Wi-Fi adapters with at least UDP tunneling,VirtualBox 4.3.18,all,2014-10-24T13:03:06Z,2015-07-25T12:05:57Z,2015-07-25T12:05:57Z,"I know requests for a virtual Wi-Fi adapter have been made before
(see[https://www.virtualbox.org/ticket/8564 #8564]),
but my reasons for wanting one are very different from that ticket.

Rather than bridge mode,
I'm asking for a virtual Wi-Fi adapter that can use at least UDP tunneling. Just that mode. No bridging necessary.

This mode alone will allow tools like [http://www.gns3.com/ GNS3]
to emulate Wi-Fi networks, which would in turn
revolutionize network professionals' training.

Ideally, whether an adapter is Wi-Fi or not should be readable by APIs,
since there are slight differences in the rules for them that GNS3
would need to apply (namely,
that multiple devices can connect to one Wi-Fi adapter,
whereas there can be only one ""cable"" for each Ethernet adapter).",boen_robot
14331,PXE boot fails on NAT network,VirtualBox 5.0.0,all,2015-07-27T12:01:55Z,2015-07-27T15:26:39Z,2015-07-27T15:26:39Z,"Hello,
I created guest(Linux/Red Hat 64-bit). Set NAT network for this guest.
I set external tftp server and file:
{{{
alexey@rualty-mac:~$ VBoxManage modifyvm ""test4"" --nattftpserver1 192.168.2.2
alexey@rualty-mac:~$ VBoxManage modifyvm ""test4"" --nattftpfile1 pxelinux.0
}}}
According to tcpdump guest successfully download pxelinux.0 form server, but couldn't get  config file.
Server several times retried to send file to the guest (see attach pxe-nat-doesnot-work.txt).
While PXE boot through bridged network works fine (see attach pxe-bridged-works.txt) 
",Alexey Tyapkin
14274,BSoD in VBoxNetLwf with d1,VirtualBox 5.0.0,Windows,2015-07-14T06:07:13Z,2015-07-31T11:58:40Z,2015-07-31T11:58:40Z,"'''Version:'''[[BR]]

VirtualBox 5.0.0-101573[[BR]]

'''Network Adapters:'''[[BR]]

RealTek Semiconductor RTL8168/8111 PCI-E Gigabit Ethernet NIC[[BR]]

VirtualBox Host-Only Ethernet Adapter[[BR]]

'''Minidump'''[[BR]]
{{{
0: kd> !analyze -v
*******************************************************************************
*                                                                             *
*                        Bugcheck Analysis                                    *
*                                                                             *
*******************************************************************************

DRIVER_IRQL_NOT_LESS_OR_EQUAL (d1)
An attempt was made to access a pageable (or completely invalid) address at an
interrupt request level (IRQL) that is too high.  This is usually
caused by drivers using improper addresses.
If kernel debugger is available get stack backtrace.
Arguments:
Arg1: fffff880079c2007, memory referenced
Arg2: 0000000000000002, IRQL
Arg3: 0000000000000000, value 0 = read operation, 1 = write operation
Arg4: fffff880042ab2a4, address which referenced memory

Debugging Details:
------------------

DBGHELP: C:\WinDDK\7600.16385.1\Debuggers\nsiproxy.sys - file not found
DBGHELP: C:\Windows\System32\drivers\nsiproxy.sys - OK
DBGHELP: C:\Windows\System32\drivers\nsiproxy.sys found
DBGENG:  C:\Windows\System32\drivers\nsiproxy.sys - Mapped image memory
DBGHELP: C:\WinDDK\7600.16385.1\Debuggers\mssmbios.sys - file not found
DBGHELP: C:\Windows\System32\drivers\mssmbios.sys - OK
DBGHELP: C:\Windows\System32\drivers\mssmbios.sys found
DBGENG:  C:\Windows\System32\drivers\mssmbios.sys - Mapped image memory
SYMSRV:  mssmbios.pdb from http://msdl.microsoft.com/download/symbols: 50755 bytes - copied         
DBGHELP: mssmbios - public symbols  
         f:\localsymbols\mssmbios.pdb\9ECFB21A2AD64292AB8AF8AB1B194C2E1\mssmbios.pdb
DBGHELP: C:\WinDDK\7600.16385.1\Debuggers\VBoxNetLwf.sys - file not found
DBGHELP: C:\Windows\System32\drivers\VBoxNetLwf.sys - OK
DBGHELP: C:\Windows\System32\drivers\VBoxNetLwf.sys found
DBGENG:  C:\Windows\System32\drivers\VBoxNetLwf.sys - Mapped image memory
SYMSRV:  f:\localsymbols\VBoxNetLwf.pdb\7E00272F27A1406CADE9A553C591E1CB1\VBoxNetLwf.pdb not found
SYMSRV:  http://msdl.microsoft.com/download/symbols/VBoxNetLwf.pdb/7E00272F27A1406CADE9A553C591E1CB1/VBoxNetLwf.pdb not found
DBGHELP: VBoxNetLwf.pdb - file not found
DBGHELP: F:\tinderbox\win-rel\out\win.amd64\release\obj\VBoxNetLwf\VBoxNetLwf.pdb - file not found
*** ERROR: Symbol file could not be found.  Defaulted to export symbols for VBoxNetLwf.sys - 
DBGHELP: VBoxNetLwf - export symbols
DBGHELP: C:\WinDDK\7600.16385.1\Debuggers\VBoxNetAdp6.sys - file not found
DBGHELP: C:\Windows\System32\drivers\VBoxNetAdp6.sys - OK
DBGHELP: C:\Windows\System32\drivers\VBoxNetAdp6.sys found
DBGENG:  C:\Windows\System32\drivers\VBoxNetAdp6.sys - Mapped image memory
DBGHELP: C:\WinDDK\7600.16385.1\Debuggers\ndis.sys - file not found
DBGHELP: C:\Windows\System32\drivers\ndis.sys - OK
DBGHELP: C:\Windows\System32\drivers\ndis.sys found
DBGENG:  C:\Windows\System32\drivers\ndis.sys - Mapped image memory
SYMSRV:  ndis.pdb from http://msdl.microsoft.com/download/symbols: 420783 bytes - copied         
DBGHELP: ndis - public symbols  
         f:\localsymbols\ndis.pdb\7F2704456B8949D6BD0D97D90F00DB912\ndis.pdb
DBGHELP: C:\WinDDK\7600.16385.1\Debuggers\Rt64win7.sys - file not found
DBGHELP: C:\Windows\System32\drivers\Rt64win7.sys - OK
DBGHELP: C:\Windows\System32\drivers\Rt64win7.sys found
DBGENG:  C:\Windows\System32\drivers\Rt64win7.sys - Mapped image memory
SYMSRV:  f:\localsymbols\rt64win7.pdb\CA0B16D985A346649CC5D6735331FF111\rt64win7.pdb not found
SYMSRV:  http://msdl.microsoft.com/download/symbols/rt64win7.pdb/CA0B16D985A346649CC5D6735331FF111/rt64win7.pdb not found
DBGHELP: rt64win7.pdb - file not found
DBGHELP: d:\svn\ndis_6\driver\src\src\sysw7x64\objfre_win7_amd64\amd64\rt64win7.pdb - file not found
*** ERROR: Module load completed but symbols could not be loaded for Rt64win7.sys
DBGHELP: Rt64win7 - no symbols loaded
DBGHELP: C:\WinDDK\7600.16385.1\Debuggers\TDI.SYS - file not found
DBGHELP: C:\Windows\System32\drivers\tdi.sys - OK
DBGHELP: C:\Windows\System32\drivers\tdi.sys found
DBGENG:  C:\Windows\System32\drivers\tdi.sys - Mapped image memory
DBGHELP: C:\WinDDK\7600.16385.1\Debuggers\afd.sys - file not found
DBGHELP: C:\Windows\System32\drivers\afd.sys - OK
DBGHELP: C:\Windows\System32\drivers\afd.sys found
DBGENG:  C:\Windows\System32\drivers\afd.sys - Mapped image memory
DBGHELP: C:\WinDDK\7600.16385.1\Debuggers\WDFLDR.SYS - file not found
DBGHELP: C:\Windows\System32\drivers\WdfLdr.sys - OK
DBGHELP: C:\Windows\System32\drivers\WdfLdr.sys found
DBGENG:  C:\Windows\System32\drivers\WdfLdr.sys - Mapped image memory
DBGHELP: C:\WinDDK\7600.16385.1\Debuggers\ACPI.sys - file not found
DBGHELP: C:\Windows\System32\drivers\acpi.sys - OK
DBGHELP: C:\Windows\System32\drivers\acpi.sys found
DBGENG:  C:\Windows\System32\drivers\acpi.sys - Mapped image memory
DBGHELP: C:\WinDDK\7600.16385.1\Debuggers\tcpip.sys - file not found
DBGHELP: C:\Windows\System32\drivers\tcpip.sys - OK
DBGHELP: C:\Windows\System32\drivers\tcpip.sys found
DBGENG:  C:\Windows\System32\drivers\tcpip.sys - Mapped image memory
DBGHELP: C:\WinDDK\7600.16385.1\Debuggers\vga.sys - file not found
DBGHELP: C:\Windows\System32\drivers\vga.sys - OK
DBGHELP: C:\Windows\System32\drivers\vga.sys found
DBGENG:  C:\Windows\System32\drivers\vga.sys - Mapped image memory
DBGHELP: C:\WinDDK\7600.16385.1\Debuggers\VIDEOPRT.SYS - file not found
DBGHELP: C:\Windows\System32\drivers\videoprt.sys - OK
DBGHELP: C:\Windows\System32\drivers\videoprt.sys found
DBGENG:  C:\Windows\System32\drivers\videoprt.sys - Mapped image memory
DBGHELP: C:\WinDDK\7600.16385.1\Debuggers\HIDPARSE.SYS - file not found
DBGHELP: C:\Windows\System32\drivers\hidparse.sys - OK
DBGHELP: C:\Windows\System32\drivers\hidparse.sys found
DBGENG:  C:\Windows\System32\drivers\hidparse.sys - Mapped image memory
DBGHELP: C:\WinDDK\7600.16385.1\Debuggers\usbccgp.sys - file not found
DBGHELP: C:\Windows\System32\drivers\usbccgp.sys - OK
DBGHELP: C:\Windows\System32\drivers\usbccgp.sys found
DBGENG:  C:\Windows\System32\drivers\usbccgp.sys - Mapped image memory
DBGHELP: C:\WinDDK\7600.16385.1\Debuggers\usbehci.sys - file not found
DBGHELP: C:\Windows\System32\drivers\usbehci.sys - OK
DBGHELP: C:\Windows\System32\drivers\usbehci.sys found
DBGENG:  C:\Windows\System32\drivers\usbehci.sys - Mapped image memory
DBGHELP: C:\WinDDK\7600.16385.1\Debuggers\USBPORT.SYS - file not found
DBGHELP: C:\Windows\System32\drivers\usbport.sys - OK
DBGHELP: C:\Windows\System32\drivers\usbport.sys found
DBGENG:  C:\Windows\System32\drivers\usbport.sys - Mapped image memory
DBGHELP: C:\WinDDK\7600.16385.1\Debuggers\umbus.sys - file not found
DBGHELP: C:\Windows\System32\drivers\umbus.sys - OK
DBGHELP: C:\Windows\System32\drivers\umbus.sys found
DBGENG:  C:\Windows\System32\drivers\umbus.sys - Mapped image memory
DBGHELP: C:\WinDDK\7600.16385.1\Debuggers\usbhub.sys - file not found
DBGHELP: C:\Windows\System32\drivers\usbhub.sys - OK
DBGHELP: C:\Windows\System32\drivers\usbhub.sys found
DBGENG:  C:\Windows\System32\drivers\usbhub.sys - Mapped image memory
DBGHELP: C:\WinDDK\7600.16385.1\Debuggers\watchdog.sys - file not found
DBGHELP: C:\Windows\System32\drivers\watchdog.sys - OK
DBGHELP: C:\Windows\System32\drivers\watchdog.sys found
DBGENG:  C:\Windows\System32\drivers\watchdog.sys - Mapped image memory
DBGHELP: C:\Windows\System32\win32k.sys - OK
DBGENG:  C:\Windows\System32\win32k.sys - Mapped image memory
DBGHELP: C:\WinDDK\7600.16385.1\Debuggers\srv.sys - file not found
DBGHELP: C:\Windows\System32\drivers\srv.sys - OK
DBGHELP: C:\Windows\System32\drivers\srv.sys found
DBGENG:  C:\Windows\System32\drivers\srv.sys - Mapped image memory
DBGHELP: C:\WinDDK\7600.16385.1\Debuggers\fltmgr.sys - file not found
DBGHELP: C:\Windows\System32\drivers\fltMgr.sys - OK
DBGHELP: C:\Windows\System32\drivers\fltMgr.sys found
DBGENG:  C:\Windows\System32\drivers\fltMgr.sys - Mapped image memory
DBGHELP: C:\WinDDK\7600.16385.1\Debuggers\Ntfs.sys - file not found
DBGHELP: C:\Windows\System32\drivers\ntfs.sys - OK
DBGHELP: C:\Windows\System32\drivers\ntfs.sys found
DBGENG:  C:\Windows\System32\drivers\ntfs.sys - Mapped image memory

READ_ADDRESS:  fffff880079c2007 

CURRENT_IRQL:  2

FAULTING_IP: 
VBoxNetLwf+32a4
fffff880`042ab2a4 0fb64201        movzx   eax,byte ptr [rdx+1]

CUSTOMER_CRASH_COUNT:  1

DEFAULT_BUCKET_ID:  VISTA_DRIVER_FAULT

BUGCHECK_STR:  0xD1

PROCESS_NAME:  System

TRAP_FRAME:  fffff880079c1460 -- (.trap 0xfffff880079c1460)
NOTE: The trap frame does not contain all registers.
Some register values may be zeroed or incorrect.
rax=0000000000000000 rbx=0000000000000000 rcx=fffff880042ab2a4
rdx=fffff880079c2006 rsi=0000000000000000 rdi=0000000000000000
rip=fffff880042ab2a4 rsp=fffff880079c15f0 rbp=fffff880042be4d8
 r8=0000000000000000  r9=fffff880042a8000 r10=0000000000000000
r11=fffff880079c1610 r12=0000000000000000 r13=0000000000000000
r14=0000000000000000 r15=0000000000000000
iopl=0         nv up ei ng nz na pe nc
VBoxNetLwf+0x32a4:
fffff880`042ab2a4 0fb64201        movzx   eax,byte ptr [rdx+1] ds:4256:fffff880`079c2007=??
Resetting default scope

LAST_CONTROL_TRANSFER:  from fffff80002c7fe69 to fffff80002c808c0

STACK_TEXT:  
fffff880`079c1318 fffff800`02c7fe69 : 00000000`0000000a fffff880`079c2007 00000000`00000002 00000000`00000000 : nt!KeBugCheckEx
fffff880`079c1320 fffff800`02c7eae0 : fffff880`03572180 fffffa80`12a47b50 00000000`00000206 fffffa80`1c73f7a0 : nt!KiBugCheckDispatch+0x69
fffff880`079c1460 fffff880`042ab2a4 : fffffa80`1e81af50 00000000`000007ff fffffa80`1e81af50 fffffa80`1c73f670 : nt!KiPageFault+0x260
fffff880`079c15f0 fffff880`042ab72e : fffffa80`1ca55740 00000000`00000000 fffff880`042be4d8 fffffa80`1dbbb0e0 : VBoxNetLwf+0x32a4
fffff880`079c1690 fffff880`042abb78 : 00000000`00000000 00000000`00000000 fffffa80`1ca55740 fffff880`00000000 : VBoxNetLwf+0x372e
fffff880`079c1700 fffff880`01aac0a7 : 00000000`00000000 fffffa80`1c3491a0 00000000`00000000 00000000`00000000 : VBoxNetLwf+0x3b78
fffff880`079c1780 fffff880`05846cf4 : fffffa80`1c6ad000 fffffa80`1c6ad000 00000000`00000000 fffffa80`1c73f670 : ndis! ?? ::FNODOBFM::`string'+0xcd8f
fffff880`079c17d0 fffff880`058319c4 : fffffa80`1c349100 fffff880`05832c01 fffff880`0000000a fffff880`079c1a60 : Rt64win7+0x1bcf4
fffff880`079c19f0 fffff880`01b14542 : fffff880`00000000 fffffa80`1c3491a0 fffffa80`1c3491a0 fffffa80`00000000 : Rt64win7+0x69c4
fffff880`079c1a60 fffff880`01a9d56d : 00000000`00000002 00000000`0000000a 00000000`00000000 00000000`00000000 : ndis!ndisMiniportDpc+0xe2
fffff880`079c1ad0 fffff880`01ac3b7d : 00000000`00000002 00000000`00000002 00000000`00000000 fffffa80`1ca4ed78 : ndis!ndisQueuedMiniportDpcWorkItem+0xcd
fffff880`079c1b70 fffff800`02f1a456 : 00000000`27c49c63 fffffa80`3fae6b50 00000000`00000080 fffffa80`3fae6b50 : ndis!ndisReceiveWorkerThread+0x1bd
fffff880`079c1c00 fffff800`02c722c6 : fffff880`03500180 fffffa80`3fae6b50 fffffa80`1d67f6c0 00000000`ffffffff : nt!PspSystemThreadStartup+0x5a
fffff880`079c1c40 00000000`00000000 : fffff880`079c2000 fffff880`079bc000 fffff880`079c18c0 00000000`00000000 : nt!KiStartSystemThread+0x16


STACK_COMMAND:  kb

FOLLOWUP_IP: 
VBoxNetLwf+32a4
fffff880`042ab2a4 0fb64201        movzx   eax,byte ptr [rdx+1]

SYMBOL_STACK_INDEX:  3

SYMBOL_NAME:  VBoxNetLwf+32a4

FOLLOWUP_NAME:  MachineOwner

MODULE_NAME: VBoxNetLwf

IMAGE_NAME:  VBoxNetLwf.sys

DEBUG_FLR_IMAGE_TIMESTAMP:  559e4840

FAILURE_BUCKET_ID:  X64_0xD1_VBoxNetLwf+32a4

BUCKET_ID:  X64_0xD1_VBoxNetLwf+32a4

Followup: MachineOwner
---------
}}}",bookevg
14395,"vbox 5 host firewall blocks bridged networking, used to work in 4.3.20",VirtualBox 5.0.0,Windows,2015-08-05T14:37:58Z,2015-08-09T06:33:20Z,2015-08-09T06:33:20Z,"I migrated from vbox 4.3.20 on a w7/64 host to vbox 5 & later to 5.01

I run Bitdefender Internet security on my host

VM's (w7) that used to work with bridged networking under vbox 4.3.20 no longer can access internet. Disabling the Bitdefender host firewall solves the issue. accessing local web resources on the intranet such as a NAS management webpage does work. So it looks like the new network adapter of 5.x is causing the issue

NAT does work with the host firewall enabled.",Frank Bevers
9860,VirtualBox Bridged Networking Service Is not installed with Virtual Box 4.1.6,VirtualBox 4.1.6,Windows,2011-11-06T02:36:15Z,2015-08-13T16:29:31Z,2015-08-13T16:29:31Z,"I installed VB 4.1.6. Apparently it install fine. I then created a new virtual machine. I changed the networking settings to use ""Bridged Adapter"" in the Attached To list. However the Name list is empty. The dialog would not save the configuration because ""Invalid settings detected"". Same thing with earlier version of Virtual Box. The ""VirtualBox Host-Only Network"" is fine, but the bridged network adapter was not installed.",Fernando Quintero
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
8866,Guest network not able to reach beyond host's network when host bridged adaptor is using LACP (bonding),VirtualBox 4.0.6,Mac OS X,2011-05-09T14:33:27Z,2015-08-13T17:06:13Z,2015-08-13T17:06:13Z,"We have a Mac OSX host using Snow Leapord. We've bonded two of its network card to create bond0 and it uses LACP.

When the guest uses bond0 as a bridged adaptor it is only able to reach other guests on the same machine and the host itself but can't go beyond that. 
The guest I'm using is Ubuntu 10.04 64-bit.
 ",John Huong
4214,VirtualBox 2.2.4 and bonded host interface with guest bridge networking,VirtualBox 2.2.4,Linux,2009-06-11T08:31:59Z,2015-08-13T17:06:54Z,2015-08-13T17:06:54Z,"My host has two Gigabit NICs. It runs on 64 Bit Ubuntu 8.0.4.2 Server. I have bonded the two interface to become bond0.

I created another guest using 32 Bit Ubuntu 8.0.4.2 Server and configured it to be bridged with bond0.

It seems to work for a while, but halfway through the guest networking stops responding (could not ping to the network gateway or access the Internet from the guest). The host network works well as I was accessing the guest through remote desktop.",John Huong
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
4370,Guest fails to start w/VLAN Interface in OSX,VirtualBox 3.0.2,Mac OS X,2009-07-03T06:20:29Z,2015-08-13T17:37:42Z,2015-08-13T17:37:42Z,"error: Unknown error creating VM (VERR_GENERAL_FAILURE).

how to reproduce:

1. Create VLAN Interface in OSX (Requires Supported Interface)[[BR]]
2. Assign VLAN Interface to Virtual Interface in a new or existing Guest.[[BR]]
3. Start Guest, error is encountered.[[BR]]

Note, this setup works fine in both OpenSolaris & Debian VBox Hosts.",Ryan
14261,Bridge network,VirtualBox 5.0.0,Windows,2015-07-11T09:53:19Z,2015-08-15T01:28:49Z,2015-08-15T01:28:49Z,"Since my upgrade to Virtual Box 5, I have 2 issues :

1/ My Bridged Network does not work anymore, I had to switch to NAT",daredevil
14377,No Network-Adapters found after Windows 10 Installation,VirtualBox 5.0.0,Windows,2015-08-03T10:06:39Z,2015-08-15T10:06:52Z,2015-08-15T10:06:52Z,After Installation of Windows 10 pro upgrade from Windows 7 pro no networkadapters are selectable under the VMs properties Network->Networkbridge and also under Network->Host-only Adapter. The same bug was found after new installation of VirtualBox. ,arcor.de
14414,No DNS server information on DHCP enabled NATNetworks,VirtualBox 5.0.0,Linux,2015-08-07T13:43:58Z,2015-08-17T19:28:16Z,2015-08-17T19:28:16Z,"I've configured a NATNetwork with DHCP enabled:

{{{
NetworkName:    NatNetwork
IP:             10.0.3.1
Network:        10.0.3.0/24
IPv6 Enabled:   No
IPv6 Prefix:    
DHCP Enabled:   Yes
Enabled:        Yes
loopback mappings (ipv4)
        127.0.0.1=2
}}}

It created a DHCP server configuration like this:
{{{
NetworkName:    NatNetwork
IP:             10.0.3.3
NetworkMask:    255.255.255.0
lowerIPAddress: 10.0.3.4
upperIPAddress: 10.0.3.254
Enabled:        Yes
}}}

When the VM is started it requests the IP address to DHCP server. On the DHCP response (DHCP ACK package) there is no DNS information, but there is the Domain Name (DNS suffix).

If I manually configure the DNS in the virtual machine to 10.0.3.1 the name resolution works.
",jacksonfoz
14470,NAT Network failing to provision gateway,VirtualBox 5.0.2,Windows,2015-08-18T18:56:35Z,2015-08-18T21:01:03Z,2015-08-18T21:01:03Z,"Creating a new NAT Network using the GUI WITHOUT DHCP server results in a network with the gateway address at x.y.z.1 however gateway fails to respond to ping and fails to forward traffic upstream.  Stopping and restarting VirtualBox does not resolve gateway non-functionality.

NAT Network created WITH DHCP server responds to ping and forwards traffic upstream.  Removing/disabling the DHCP server does not cause loss of gateway functionality.  Functionality maintained across restart of VirtualBox.",VirtualBryan
14489,My Windows 7 cannot surf the Internet after I upgrade Virtualbox,VirtualBox 5.0.2,Windows,2015-08-24T05:42:11Z,2015-08-24T05:42:11Z,2015-08-24T05:42:11Z,"I used virtualbox 4.3.30 before. And then I upgrade Virtualbox from 4.3.30 to 5.0.2 and 5.0.0. After I upgrade Virtualbox to those newer versions. I cannot connect any website. Finally, I uninstall newer versions and load back 4.3.30 version. It can connect website successfully.",jackzzkao
13002,Slow DNS resolving with enabled natdnsproxy,VirtualBox 4.3.10,other,2014-04-29T15:50:12Z,2015-08-25T08:17:27Z,2015-08-25T08:17:27Z,"Outgoing network connections are very slow with VMs using 3.13+ kernel.

Below you can see the curl connect phase is taking 5+ seconds.  Problem exists reguardless of using virtio or intel adapters.

{{{
vagrant@vagrant-ubuntu-trusty-64:~$ curl -o /dev/null -s -w %{time_connect}:%{time_starttransfer}:%{time_total}\\n https://www.google.com
5.559:5.703:5.706
vagrant@vagrant-ubuntu-trusty-64:~$ uname -a
Linux vagrant-ubuntu-trusty-64 3.13.0-24-generic #46-Ubuntu SMP Thu Apr 10 19:11:08 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux
vagrant@vagrant-ubuntu-trusty-64:~$ lsmod
Module                  Size  Used by
vboxsf                 43786  1
nfsd                  280297  2
auth_rpcgss            59338  1 nfsd
nfs_acl                12837  1 nfsd
nfs                   236636  0
lockd                  93977  2 nfs,nfsd
sunrpc                284404  6 nfs,nfsd,auth_rpcgss,lockd,nfs_acl
fscache                63988  1 nfs
dm_crypt               23177  0
ppdev                  17671  0
psmouse               102222  0
serio_raw              13462  0
parport_pc             32701  0
parport                42348  2 ppdev,parport_pc
vboxguest             248441  2 vboxsf
ahci                   25819  1
libahci                32168  1 ahci
e1000                 145174  0
}}}

Here is my Vagrantfile that allows for simple re-creation of this issue:

{{{
 -*- mode: ruby -*-
# vi: set ft=ruby :

# Vagrantfile API/syntax version. Don't touch unless you know what you're doing!
VAGRANTFILE_API_VERSION = ""2""

Vagrant.configure(VAGRANTFILE_API_VERSION) do |config|
#  config.vm.box = ""ubuntu/trusty64""
  config.vm.box = ""ubuntu-trusty64-20140429""
  config.vm.box_url = ""http://cloud-images.ubuntu.com/vagrant/trusty/20140429/trusty-server-cloudimg-amd64-vagrant-disk1.box""

  config.vm.network :private_network, ip: ""192.168.33.10""
  config.vm.synced_folder "".."", ""/vagrant""

  config.vm.provider :virtualbox do |vb|
     vb.gui = false
     vb.name = ""slowconnection""

     # Use VBoxManage to customize the VM. For example to change memory:
     vb.customize [""modifyvm"", :id, ""--memory"", ""1024""]
  end
end
}}}

nslookup on www.google.com is fast, netperf is fast, download of files are fast once connection is made, mtr is fast (low response times).",rynop
13847,vpnc no response from target after upgrade to 4.3.20 and 4.3.22,VirtualBox 4.3.22,Windows,2015-02-17T14:20:10Z,2015-08-30T23:54:57Z,2015-08-30T23:54:57Z,"Host is Win7, Guest is OEL6.  Have been using vpnc to connect to Cisco VPN for several years.  After upgrade of VirtualBox from 4.3.12 to 4.3.20 it stopped working with ""vpnc: no response from target"". Restarting guest and host did not help. Downgrading to VirtualBox 4.3.12 resolved the issue. Tried upgrading to VirtualBox 4.3.20 again, just in case a driver got hosed during first attempt, but it did not work.  Reverted back to 4.3.12 and having been running that for months now.

Today I tried upgrading to VirtualBox 4.3.22, hoping the issue would be fixed, but it still doesn't work.  I tried the same reboot guest and host after upgrade but no luck.  Reverted back to 4.3.12 and it works fine now.",Dave Musci
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
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
14452,Installing VirtualBox 5.0.2 blocks network on host (Windows 10),VirtualBox 5.0.2,Windows,2015-08-16T01:57:41Z,2015-09-14T12:59:20Z,2015-09-14T12:59:20Z,"I installed VirtualBox 5.0.2 on my host system which runs Windows 10.

It made my network fail.
The tray icons shows no error but trying to access a website does not work.
Restarting host does not help.

There are no errors in windows device manager. Both my network cards and VirtualBox's show.

Unintalling VirtualBox, immediately makes the network work again.

I have tried this on two computers with fresh windows 10 installs.

Both my computers have an intel network card.
One computer with ""Intel(R) Ethernet Connection (2) I218-V"",
and the other with ""Intel(R) Ethernet Connection I217-V"" (this computer also has a ""Killer e2200 Gigabit Ethernet Controller"").

",spacebug
14616,Firefox.com Firefox can't completely Download files,VirtualBox 5.0.4,Windows,2015-09-21T13:46:37Z,2015-09-22T15:26:48Z,2015-09-22T15:26:48Z,"I have been running into what appears to be a bug with !VirtualBox.  

Host OS is Windows7 SP1 x64 with the latest updates.
Guest OS is Centos 7.1 x64 with the latest updates. 

When we use Firefox from www.firefox.com,  it freezes when we try to download a file.

Steps to reproduce:

1.  Start Guest OS
2.  Immediately launch Firefox (38.2.1ESR or the latest 40.x release) and try to download a file (In our case, it is a epub file, http://www.cse.yorku.ca/~jr/epub/w/CV.epub)
3.  Firefox should them freeze

If you close the VM and restart the VM, Firefox should be able to download the file. If you reboot the host and retry the steps above you will reproduce the FF download failure. 


If you look a Wireshark trace during the download you actually see the file start to download, but it seems that it isn't getting fully processed/closed/or TCP session closed. 

Google Chrome/wget  doesn't have this issue. It seems to tied to the FF from firefox.com

I am able to reproduce this with !VirtualBox 5.0.2 and 5.0.4. !VirtualBox 4.3.30 doesn't have this issue.

See the attached log and network captures.",paulg.ca
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
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
10157,Adding vCPUs degrades network performance.,VirtualBox 4.1.8,Linux,2012-01-11T12:28:32Z,2015-10-12T11:19:25Z,2015-10-12T11:19:25Z,"Observed on both Ubuntu 11.04 (2.6 kernel) and Mac OS X 10.6 hosts, both with quad core Intel i7 CPUs. Below is pasted from my forum post: https://forums.virtualbox.org/viewtopic.php?f=7&t=47136. 

I decided to run some network throughput benchmarks (mainly interested in max packets per second), and have noticed a large discrepancy when assigning one CPU to a VM vs 2 or more CPUs. My setup (all 64-bit):
Host: Ubuntu 11.04 2.6.38-13-generic #53-Ubuntu SMP, 3 GHz Intel i7 950 (4 phys cores + HT), 12GB RAM, Ethernet: Intel 82574L Gigabit
Guest: Ubuntu 11.10 3.0.0-12-server kernel, 1GB Ram assigned
VirtualBox version: 4.1.8 

Following are the results of the basic testing I performed using netserver/netperf against a bridged network interface (bridged to above Intel device). The following commands were run on the Guest against its local interface (not the loopback):
netserver -4 (starts an ipv4 tcp/udp server). 
netperf -H <IP_address_of_eth0> -t TCP_CRR (runs a TCP connect/request/response transaction benchmark) 

Single-CPU VM
~17-18k transactions per second

2-CPU VM
~5k TPS

2-CPU VM with eth0 interrupts and netserver/netperf all pinned to the same core
~7k TPS
Confirmed v. low scheduling interrupts during benchmark (watching /proc/interrupts)

2-CPU VM with 2nd core disabled via hotplugging
Disabled the second cpu with: echo '0' > /sys/devices/system/cpu/cpu1/online and confirmed via /proc/interrupts and other system tools.
~8.5k TPS

Also worth noting that on the host system, the same test yields around 26k TPS. netfilter/conntrack is disabled on both host and guest. 

So even with the second cpu disabled I'm seeing around a 50% performance degradation vs the single-cpu VM. The results with more than 2 CPUs were very similar to the 2-CPU scenario. 

I would like to understand why this is the case (I'm certainly no virtualization expert); are additional extensions/emulations loaded when starting a multicore guest?

Update
I repeated the same test on an OS X 10.6 host on similar architecture (quad core intel i7) and the results were the same, also on VBox 4.1.8. 

I decided to extend the test to something CPU bound and ran a Linpack benchmark (single thread), but the results are unaffected by number of vCPUs (which is good). And so I also ran a a disk read benchmark using hdparm, and this was also unaffected, so this seems to be confined to network performance for now.",james little
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
14767,VirtualBox 5.0.8 causes Wireless Networks to Disappear,VirtualBox 5.0.8,Windows,2015-10-30T11:18:18Z,2015-10-30T11:28:25Z,2015-10-30T11:28:25Z,"I installed VirtualBox 5.0.8 under Windows 10 Professional (x64), upgrading my system from 5.0.6.

Now, when I reboot, there is a red ""X"" in my wireless network connections on the login screen.  

When I login to my local desktop (Administrator account or user account with admin privileges) and click the Network Settings icon in the system tray, I get the message that there are no wireless networks.

I have to wait 2-3 minutes before they appear.  Once they do, then Windows 10 connects to them.  Sometimes it takes longer than 2-3 minutes.

I restored my machine to a Windows 10 image I had created prior to installing VirtualBox 5.0.8 and the problem has gone away.
",Master VB Guru
14791,bridged network error on windows 10,VirtualBox 5.0.8,Windows,2015-11-05T08:22:08Z,2015-11-05T08:22:08Z,2015-11-05T08:22:08Z,"I installed VirtualBox 5.08 on windows 10 pro which run in a windows domain. Current user had admin rights.
A host-only adapter could be installed.
When trying to use bridged or host-only networking, the VM(windows 2008 r2 server) refused to start. NAT was ok.
After many tries I activated the local Administrator, logged in locally and the VM started fine with bridged networking.
From now I could start the VM also as domain user.
Maybe this description helps fixing this issue. 
",miro25
14790,Network communication problem in newer versions of VirtualBox. Possible regression.,VirtualBox 5.0.8,other,2015-11-05T06:18:32Z,2015-11-07T23:36:28Z,2015-11-07T23:36:28Z,"I recently found that !VirtualBox could no longer communicate with my printer/scanner (same device). The device is attached via network ethernet cable (NAT).

The operating system of the guest is Linux Mint release 17 (qiana) Mate 64-bit. The driver has worked fine for years. After an update of !Virtualbox somewhere in version 4.x, I was able to send print commands but I could no longer communicate with the scanner.

To help narrow down the problem, I tested the exact same operating system and printer driver with 2 different versions of !VirtualBox:

1. !VirtualBox v. 4.2.32 `r101581`: Scanner works
2. !VirtualBox v. 5.0.6 `r103037`: Scanner fails

Scanning hasn't worked for some time; at least since version 5.0 and possibly a bit before that. I estimate that it broke sometime after 4.3. Comments in !VirtualBox's forum indicate that it's a possible regression because nothing has changed except for the !VirtualBox version. Every time I downgraded or upgraded !VirtualBox, I always installed the corresponding guest additions for that particular version. I tested with version 5.0.8 `r103449` also; the problem persists.

To replicate the problem:
1. Install Linux Mint 17 Mate 64-bit as the guest. The host can be anything. It's a guest problem.
2. Install scanner and printer drivers for Lexmark Pinnacle Pro901. These are the respective files:

http://support.lexmark.com/index?docLocale=en_US&page=content&id=DR21641&locale=EN&userlocale=EN_US

http://support.lexmark.com/index?docLocale=en_US&page=content&id=DR21637&locale=EN&userlocale=EN_US

3. When installing the printer driver, add the printer to the operating system. Let the operating system detect the printer, then use AppSocket/HP JetDirect. The IP of the printer will be automatically detected without having to choose AppSocket/HP JetDirect.

4. There is a cups-insecure-filter error when you try to print. This is easily fixed:
{{{
cd /usr/local/lexmark/v3/bin/
sudo chmod 755 printfilter
}}}
Printing isn't the problem though. I include this just to be thorough.

5. Install any scanning program. gscan2pdf and Simple Scan both work well. On older versions of !VirtualBox (up to about the 4.2 I tested, possibly up to around 4.3), scanning will work just fine. All later versions cut off access to the scanner; the scanning program will say no scanners were detected.

// End of steps for reproducing the problem

A log file has been attached. During the time the log was created, I powered on the virtual machine, successfully tested that a printed document could be sent to the printer, tested the scanner (which failed), and then powered it off. I'll be happy to provide more details that might be relevant.",misterpenguin
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
14428,win 10 host and VB from 5.0 to latest test build = NO bridge networking,VirtualBox 5.0.0,Windows,2015-08-11T13:44:44Z,2015-12-02T08:43:13Z,2015-12-02T08:43:13Z,"hi!

win 10 64 bit host , upgrade from win 8.1,
win xp guest

no way to set network -bridge-

hope someone will be able to find a workaround as for the 
issue of the no sound:
https://www.virtualbox.org/ticket/14361#comment:21

cheers",giusi
14974,Windows 10 /Solaris:Linux or Windows Guest,VirtualBox 5.0.12,Windows,2015-12-24T12:41:32Z,2015-12-24T16:21:13Z,2015-12-24T16:21:13Z,"The guest, whatever version windows, linux or solaris will work for a few weeks then fail, I have to restart the PC change some ethernet adapter property usually I toggle ipv6 enabled and then virtualbox guest starts ok. This cycle repeats

The log that shows the issue seems to reference two c++ files. 

I had put this one the forum, but I placed in the wrong sub-forum, Windows 10 Guest. The moderator suggested this was incorrect and moved to a Solaris guest.
",matdave
11978,Dup ping and not network connectivity while bridged on WIFI,VirtualBox 4.2.16,Linux,2013-07-21T22:49:50Z,2015-12-29T19:30:45Z,2015-12-29T19:30:45Z,"Good day all,
I am running Fedora 19 x64.  Using the same laptop for couple of years now and longer for Virtualbox.  During the last upgrade I started having connectivity issues on some machines.  Further investigation found that only machines that were bridged on the WIFI was affected.  Let me know if you want any configuration files or anything at all.
Thanks, Devon
{{{
[devon@fisc-dcj-rhw ~]$ ping google.com
PING google.com (74.125.229.227) 56(84) bytes of data.
64 bytes from 74.125.229.227: icmp_seq=1 ttl=56 time=15.5 ms
64 bytes from 74.125.229.227: icmp_seq=1 ttl=55 time=15.6 ms (DUP!)
64 bytes from 74.125.229.227: icmp_seq=2 ttl=56 time=18.6 ms
64 bytes from 74.125.229.227: icmp_seq=2 ttl=55 time=18.7 ms (DUP!)
64 bytes from 74.125.229.227: icmp_seq=3 ttl=56 time=17.7 ms
64 bytes from 74.125.229.227: icmp_seq=3 ttl=55 time=17.8 ms (DUP!)
64 bytes from 74.125.229.227: icmp_seq=4 ttl=56 time=83.2 ms
64 bytes from 74.125.229.227: icmp_seq=4 ttl=55 time=83.3 ms (DUP!)
64 bytes from 74.125.229.227: icmp_seq=5 ttl=56 time=103 ms
64 bytes from 74.125.229.227: icmp_seq=5 ttl=55 time=103 ms (DUP!)
}}}",Devon
13967,NatNetwork limits mtu,VirtualBox 4.3.26,Windows,2015-03-18T13:43:20Z,2016-01-05T16:20:19Z,2016-01-05T16:20:19Z,"I have 4.3.26 in win7 running.

My guests are linux (redhat 5,4 5.10, opensuse 13.2, ...)

All are connected to a virtualbox NatNetwork

Inside the guests an openvpn client is started and i see, that huge packets that the openvpn client sents will be dropped. I investigated further and found out, that the highest Packet size leaving the host is 1295 bytes long.

",RobbySherwood
15030,DHCP server on natnetwork doesn't return DNS servers,VirtualBox 5.0.12,Linux,2016-01-12T14:24:23Z,2016-01-12T15:16:39Z,2016-01-12T15:16:39Z,"If I start up a guest VM on old school nat networking I see an option 6 come thru with the DHCP response from the virtualbox DHCP server.

If I do the same on a natnetwork'd guest all but one of the same options arrive in the DHCP response, including 15 for a DNS domain name, but option 6 is consistently missing and obviously this means the DNS server is never configured inside the guest.
If I set it manually in the guest to the IP I configured under ""VBoxManage dhcpserver add"" everything works as expected so networking is certainly working.

This is easily observed with a linux guest by installing and running dhcpdump while running ""dhclient -d""",tommyvn
15076,Wifi connections goes off,VirtualBox 4.3.36,Windows,2016-01-25T18:15:47Z,2016-01-25T21:47:43Z,2016-01-25T21:47:43Z,"If I leave my virtual machine in saved state and turn off my pc and then turn it on after sometime my host os looses wifi connection  ,it shows limited .The only workaround is to switch on the vm ,turn it off and then restart the pc .

This doesn't happen if I turn off the vm instead of leaving it in the saved state
",rishabh
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
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
15147,Guest OS cannot see Host in Bridged Mode,VirtualBox 5.0.14,Windows,2016-02-13T05:45:37Z,2016-02-14T10:37:51Z,2016-02-14T10:37:51Z,"I have Windows 10 as a host system and Centos 6 as a guest system.
I am connection to internet by wireless
The issue is that bridged network adapter does not allow automatic ip configuration. So I have setup static ip to connect and the rare thing is the the guest system (centos) can get access to internet, can ping the gateway but cannot ping the host system, but the host system can ping the guest system.
",kecondezo
15166,Cannot set Host-only connection on OSX El Capitan Host,VirtualBox 5.0.14,Mac OS X,2016-02-22T09:58:40Z,2016-02-24T15:30:28Z,2016-02-24T15:30:28Z,"Hi, guys! I'm really exhausted, I've been searching a solution for my problem, I've seen a lot them: uninstall and reinstall VirtualBox, restarting the Daemons from VirtualBox.sh... but I'm not still unable to set this option. I need this config because I can't reach my IP machine from host and vice versa... I don't if can be due to a bug with OSX El Capitan. Waiting for help or an answer to illuminate me T_T. Thanks!!",Myugen
14946,WiFi problem at user logon,VirtualBox 5.0.12,Windows,2015-12-19T04:48:06Z,2016-03-05T14:18:19Z,2016-03-05T14:18:19Z,"Starting from version 10.0.8, I have a very weird problem with WiFi connection at logon. The connection appears good as normal, but actually it is not and no internet connections can be made.

I have to disconnect and reconnect to get network working. This happens verytime I logon my account - with one exception.

The exception is - Everyday in the morning I power on my computer, it works as normal; but after that during the day, even a cold reboot would not work.

My system is Windows 10 (build 10586).
",Edward Yang
14572,Can't recover the IP when USB2Ethernet adapter is removed and reconnected.,VirtualBox 5.0.0,Windows,2015-09-11T04:27:22Z,2016-03-14T16:19:00Z,2016-03-14T16:19:00Z,"= Heading =
IP address not recovered in bridged mode when USB2Ethernet adapter is removed and reconnected.

== Description ==
I'm running VirtualBox-5.0.0-r101573 64bit version on Windows 7 64bit OS, having guest as CentOSv6. The guestos is configured with two network adapters, 1) Host-Only 2) Bridged. When the guestos is booted afresh with the USB2Ethernet adapter connected, the Bridged network obtains the IP properly, But when the USB2Ethernet adapter is removed and reconnected the guestos is unable to fetch the IP and waits indefinitely.

'''Steps to reproduce'''
1. Boot the guestos with USB2Ethernet connected.
2. IP should acquire properly.
3. Remove the USB2Ethernet adapter from the System.
4. Try to restart the network service in the guestos.
5. Unable to fetch the IP and waits indefinitely.

'''Note''': Not tested on other guestos whether the same problem exists or not.",lokesh
15266,VirtualBox 5.0.16 - Windows 10 Host- Bridged Network,VirtualBox 5.0.16,Windows,2016-03-22T21:05:11Z,2016-03-23T02:58:01Z,2016-03-23T02:58:01Z,"Hello,

I have on Windows 10 Host the !VirtualBox 5.0.16 installed and try a Linux Guest with bridged Network.
On Network tab, i can select the bridged network as interface and then the physical network device from windows.
I am try to install a fresh Linux Ubuntu 14.04 LTS Server. This works fine, but the DHCP Service will not found from Linux. After setting up manual IP-addresses it will not be better. The Interface appears in the Linux system but no ping or other communication will work.

The IP-range is correct, the addresses also. Any idea what is the problem and what can i do?

Thanks Sascha",svalcken
15275,No host-only adapter,VirtualBox 4.3.12,Windows,2016-03-26T06:37:27Z,2016-03-26T06:37:27Z,2016-03-26T06:37:27Z,"I have upgraded from windows7 to windows10 and my host-only adapter disappaered in Windows and virtualbox. 
I use virtualbox 4.3.12
",louis14
15014,"Virtual Machine returns duplicate network packets (host SLES 12, guest Win Server 2008, VirtualBox 5.0.4)",VirtualBox 5.0.4,Linux,2016-01-07T09:17:59Z,2016-04-23T22:04:55Z,2016-04-23T22:04:55Z,"Hello,

the virtual machine with Win Server 2008 and static IP address connected to host machine with SLES 12 via bridged network interface returns duplicate network packets.

First I noticed it when sending ping requests to the virtual machine from another host in the network. The ping returns DUPs. Then I started wireshark on hosting machine and I tested the issue also with netcat: sending simple echo from the virtual machine results to double response received by netcat in my laptop. The wireshark clearly shows that the virtual machine sends back duplicate packets for ICMP, UDP and (testing with SNMP traps) also for TCP protocols.

Would you know whether the higher releases of the virtualbox fix this problem? 

Best rgards
mca0001",mca0001
15367,Cannot remove 4.3.12 Bridged Network Miniport Driver - Bridget Networ not working,VirtualBox 5.0.18,Windows,2016-04-28T13:11:53Z,2016-04-28T13:11:53Z,2016-04-28T13:11:53Z,"Hi,
Bridged Network does not work anymore after updating to any 5.x version. There are still remains of the old 4.3.12 driver in the device manager (with exclamation mark) wich I can't ether uninstall or repair. Uninstalling VBox 5.0.18 rebooting, re-installing has no effect. No new drivers were installed. 

I also tried to remove involved keys from the registry, but I could not delete them for whatever reason. I'm running windows 8.1.
",Elsni
15391,TTL Expired in Base Machine if 2 VM's runnig,VirtualBox 5.0.18,Windows,2016-05-05T09:16:28Z,2016-05-05T15:21:21Z,2016-05-05T15:21:21Z,"Been using Virtual box for Years, but I have notice a problem lately ( last week). Using !VirtualBox 5.0.18 r106667

Each of my VM's have 2 Interfaces , one set as bridged (IPV4 Static) , one set as NAT (DCHP) . The NAT interface is set as Cable Disconnected to Keep VM from internet unless I specifically need it.

Now down to my problem, my network on my base machine seems to have TTL Expire errors when I ping 8.8.8.8 from base machine while I have 2 VM's running as soon as I pause them or switch them off/suspend them the TTL EXPIRE error disappears. I have tried with and without the network interfaces in the VM enabled. This can be seen by the time the XP Splash screen shows on Second machine rather than once XP is fully running. 


Ping to 8.8.8.8 from Base machine as second VM is started
{{{
Reply from 8.8.8.8: bytes=32 time=28ms TTL=58
Reply from 8.8.8.8: bytes=32 time=33ms TTL=58
Reply from 8.8.8.8: bytes=32 time=30ms TTL=58
Reply from 8.8.8.8: bytes=32 time=29ms TTL=58
Reply from 8.8.8.8: bytes=32 time=29ms TTL=58
Reply from 8.8.8.8: bytes=32 time=37ms TTL=58
Reply from 8.8.8.8: bytes=32 time=29ms TTL=58
Reply from 8.8.8.8: bytes=32 time=29ms TTL=58
Reply from 8.8.8.8: bytes=32 time=29ms TTL=58
Reply from 8.8.8.8: bytes=32 time=28ms TTL=58
Reply from 172.16.228.176: TTL expired in transit.
Reply from 172.16.228.176: TTL expired in transit.
Reply from 172.16.228.176: TTL expired in transit.
Reply from 172.16.228.176: TTL expired in transit.
Reply from 172.16.228.176: TTL expired in transit.
Reply from 172.16.228.176: TTL expired in transit.
Reply from 172.16.228.176: TTL expired in transit.
Reply from 172.16.228.176: TTL expired in transit.
Reply from 172.16.228.176: TTL expired in transit.
}}}

Routing Tables from Base Machine
{{{
===========================================================================
Interface List
 28...1a 76 3f 20 74 c1 ......Microsoft Wi-Fi Direct Virtual Adapter
 16...2a 76 3f 20 74 c1 ......Microsoft Wi-Fi Direct Virtual Adapter #2
 31...0a 00 27 00 00 1f ......VirtualBox Host-Only Ethernet Adapter
 12...d4 be d9 84 d1 0b ......Realtek PCIe GBE Family Controller
  8...00 50 56 c0 00 01 ......VMware Virtual Ethernet Adapter for VMnet1
 21...00 50 56 c0 00 08 ......VMware Virtual Ethernet Adapter for VMnet8
 13...b8 76 3f 20 74 c1 ......Dell Wireless 1901 802.11a/b/g/n (2.4GHz and 5GHz)
 23...00 ff 99 5b a6 25 ......TAP-Win32 Adapter V9
 43...00 ff ea 7f 81 0e ......TeamViewer VPN Adapter
  3...b8 76 3f 20 74 c2 ......Bluetooth PAN HelpText
  1...........................Software Loopback Interface 1
===========================================================================

IPv4 Route Table
===========================================================================
Active Routes:
Network Destination        Netmask          Gateway       Interface  Metric
          0.0.0.0          0.0.0.0     172.16.228.1   172.16.228.176     20
          0.0.0.0          0.0.0.0     172.16.228.1   172.16.228.172     25
        127.0.0.0        255.0.0.0         On-link         127.0.0.1    306
        127.0.0.1  255.255.255.255         On-link         127.0.0.1    306
  127.255.255.255  255.255.255.255         On-link         127.0.0.1    306
     172.16.228.0    255.255.255.0         On-link    172.16.228.176    276
     172.16.228.0    255.255.255.0         On-link    172.16.228.172    281
   172.16.228.172  255.255.255.255         On-link    172.16.228.172    281
   172.16.228.176  255.255.255.255         On-link    172.16.228.176    276
   172.16.228.255  255.255.255.255         On-link    172.16.228.176    276
   172.16.228.255  255.255.255.255         On-link    172.16.228.172    281
     192.168.10.0    255.255.255.0         On-link      192.168.10.1    276
     192.168.10.1  255.255.255.255         On-link      192.168.10.1    276
   192.168.10.255  255.255.255.255         On-link      192.168.10.1    276
     192.168.56.0    255.255.255.0         On-link      192.168.56.1    266
     192.168.56.1  255.255.255.255         On-link      192.168.56.1    266
   192.168.56.255  255.255.255.255         On-link      192.168.56.1    266
    192.168.184.0    255.255.255.0         On-link     192.168.184.1    276
    192.168.184.1  255.255.255.255         On-link     192.168.184.1    276
  192.168.184.255  255.255.255.255         On-link     192.168.184.1    276
        224.0.0.0        240.0.0.0         On-link         127.0.0.1    306
        224.0.0.0        240.0.0.0         On-link      192.168.56.1    266
        224.0.0.0        240.0.0.0         On-link    172.16.228.176    276
        224.0.0.0        240.0.0.0         On-link    172.16.228.172    281
        224.0.0.0        240.0.0.0         On-link      192.168.10.1    276
        224.0.0.0        240.0.0.0         On-link     192.168.184.1    276
  255.255.255.255  255.255.255.255         On-link         127.0.0.1    306
  255.255.255.255  255.255.255.255         On-link      192.168.56.1    266
  255.255.255.255  255.255.255.255         On-link    172.16.228.176    276
  255.255.255.255  255.255.255.255         On-link    172.16.228.172    281
  255.255.255.255  255.255.255.255         On-link      192.168.10.1    276
  255.255.255.255  255.255.255.255         On-link     192.168.184.1    276
===========================================================================
Persistent Routes:
  None

IPv6 Route Table
===========================================================================
Active Routes:
 If Metric Network Destination      Gateway
  1    306 ::1/128                  On-link
 31    266 fe80::/64                On-link
 13    281 fe80::/64                On-link
  8    276 fe80::/64                On-link
 21    276 fe80::/64                On-link
 13    281 fe80::558:9d49:604d:8884/128
                                    On-link
 31    266 fe80::5565:d785:2df6:9cb6/128
                                    On-link
  8    276 fe80::88b5:5871:7b28:d87/128
                                    On-link
 21    276 fe80::c9b3:ca08:7e8b:6e66/128
                                    On-link
  1    306 ff00::/8                 On-link
 31    266 ff00::/8                 On-link
 13    281 ff00::/8                 On-link
  8    276 ff00::/8                 On-link
 21    276 ff00::/8                 On-link
===========================================================================
Persistent Routes:
  None
}}}


VM Log ATTACHED",mad4x4
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
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
15449,No way to get DHCP-assigned IP address of natnetwork guest without guest additions,VirtualBox 5.0.20,other,2016-05-26T18:16:06Z,2016-05-26T18:16:06Z,2016-05-26T18:16:06Z,"It should be possible using showvminfo or a similar mechanism to get the IP address assigned to a guest, without requiring the guest to have the guest additions installed.",AxelFontaine
15457,Uninstall does not remove all network registry entries,VirtualBox 5.0.20,other,2016-05-29T19:05:23Z,2016-05-29T19:05:23Z,2016-05-29T19:05:23Z,"When uninstalling Virtual box (see ticket 15404 for why), the registry entries for the network drivers are not removed.  As a result, re-installation doesn't work correctly.  On a clean system, install and uninstall and diff the registry.  ",Curt
13922,Cant install openvpn when virtualbox is installed. Windows10 x64 build9926,VirtualBox 4.3.24,Windows,2015-03-04T22:52:03Z,2016-06-03T14:50:06Z,2016-06-03T14:50:06Z,"Hi, on windows 10 i cant install openvpn only when virtual box is already insalled. It stuck on tap-installer. Without virtualbox install goes fine.",bullet92
14904,Not possible to create Host Only network,VirtualBox 5.0.10,Windows,2015-12-06T14:53:09Z,2016-06-17T07:23:29Z,2016-06-17T07:23:29Z,"when click on add new receive this error :
Querying NetCfgInstanceId failed (0x00000000).

Result Code: 
E_FAIL (0x80004005)
Component: 
HostNetworkInterfaceWrap
Interface: 
IHostNetworkInterface {455f8c45-44a0-a470-ba20-27890b96dba9}

This happens on windows 10 build Version 10.0.10586 Build 10586

Without this, cant use 3rd party software like Genymotion (dont launch enymore)",Sergi
15520,vbox/src/VBox/Devices/Network/slirp/resolv_conf_parser.c:476: bad test ?,VirtualBox 5.0.22,other,2016-06-17T14:19:59Z,2016-06-17T18:38:26Z,2016-06-17T18:38:26Z,"vbox/src/VBox/Devices/Network/slirp/resolv_conf_parser.c:476]: (warning) Logical conjunction always evaluates to false: EXPR == ' ' && EXPR == '\t'.

Source code is

    while (*psz && *psz == ' ' && *psz == '\t')

",dcb
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
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
15404,Windows 10 - Failed to create the host-only adapter,VirtualBox 5.0.20,Windows,2016-05-11T08:55:23Z,2016-07-26T15:19:29Z,2016-07-26T15:19:29Z,"When I'm trying to run my VM using vagrant I'm getting following error:

{{{
There was an error while executing `VBoxManage`, a CLI used by Vagrant
for controlling VirtualBox. The command and stderr is shown below.

Command: [""hostonlyif"", ""create""]

Stderr: 0%...
Progress state: E_INVALIDARG
VBoxManage.exe: error: Failed to create the host-only adapter
VBoxManage.exe: error: Assertion failed: [!aInterfaceName.isEmpty()] at 'F:\tinderbox\win-5.0\src\VBox\Main\src-server\HostNetworkInterfaceImpl.cpp' (74) in long __cdecl HostNetworkInterface::init(class com::Bstr,class com::Bstr,class com::Guid,enum __MIDL___MIDL_itf_VirtualBox_0000_0000_0036).
VBoxManage.exe: error: Please contact the product vendor!
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
}}}

System information:
- VirtualBox 5.0.21r107152
- Vagrant 1.8.1
- Windows 10 Enterprise Insider Preview, Build 14342.rs1_release.160506-1708


",josin
15755,Windows 7 64bit Host - VirtualBox 5.1.2 r108956 The network operation failed,VirtualBox 5.1.2,Windows,2016-08-05T20:58:06Z,2016-08-10T07:31:53Z,2016-08-10T07:31:53Z,"Dear community,
VirtualBox 5.1.2 r108956 failed with Windows 7 64bit Host and Ubuntu as Guest.
As reported for other versions of VirtualBox, ""The network operation failed with the following error: During network request: Connection refused"". I followed all recommendations suggested for older versions of virtualbox but any of them fixed the problem.
Because the network is failing I do not have access to internet when I'm using ubuntu, and it is critical for accessing some of my documents/data.
Let me know if I need to report something else, and how I can report them.
Thanks,
Peris",Peris_D
15895,Windows 7 Lights Out on Linux Mint (Mate) Host,VirtualBox 5.1.4,Linux,2016-09-07T02:50:28Z,2016-09-07T02:50:28Z,2016-09-07T02:50:28Z,"Hi all,

We have been running a Windows 7 VM for quite a while and since the update to 5.1 have an issue with this VM just stopping. No lock up or anything, just a random lights out, this seems to happen when using network services more often than not.

Attached are a couple of logs from when this has happened.

TIA.

",FFH4500
15738,Disabling Windows 10 Guest network adapter hangs VM,VirtualBox 5.1.2,Mac OS X,2016-08-03T14:04:38Z,2016-09-07T12:24:51Z,2016-09-07T12:24:51Z,"VirtualBox 5.1.2 r108956
Mac OS X 10.11.13 host
Windows 10 Pro Guest
Windows Network adapter in Bridged mode
Disabling the adapter in Windows hangs the VM
Worked fine in 5.1.0",twinhats
15940,Failed to open a session while starting a virtual machine,VirtualBox 5.1.6,Mac OS X,2016-09-16T04:48:37Z,2016-09-16T04:54:36Z,2016-09-16T04:54:36Z,"Virtual Box version 5.1.4

Mac OS X El Capitan version 10.11.6 with McAfee Endpoint protection

16GB Ram, Intel Core I7 processor

I installed virtualbox on my Mac & then imported an OVA [Oracle DB developer apps VM, an old version released in 2013].

The VM n/w settings were NAT with port forwarding enabled [localhost port 1700 & guest VM port 1700]. On starting the VM, it failed with the following message -
{{{
Failed to open a session for the virtual machine DevVM.

The VM session was aborted.

Result Code: NS_ERROR_FAILURE (0x80004005)
Component: SessionMachine
Interface: ISession {7844aa05-b02e-4cdd-a04f-ade4a762e6b7}
}}}
Setting the n/w to Nothing or NAT network allows the VM to boot without any issues.

To avoid any suspicion with the old OVA, I downloaded a CentOS minimal OVA from the following location -

https://sourceforge.net/projects/virtualappliances/files/Linux/CentOS/CentOS-6.4-i386-minimal.ova

It too failed with the same error, & changing the n/w settings to Nothing or NAT network worked.

I had disabled the McAfee Endpoint protection in both cases, still there was one process McAfee process running in the background -
{{{
bhushan:~$ kextstat | grep -v com.apple
Index Refs Address            Size       Wired      Name (Version) UUID <Linked Against>
  143    3 0xffffff7f8329f000 0x61000    0x61000    org.virtualbox.kext.VBoxDrv (5.1.4) 63317E7D-29D2-38A1-9B7C-BA930B0E017E <7 5 4 3 1>
  146    0 0xffffff7f83300000 0x8000     0x8000     org.virtualbox.kext.VBoxUSB (5.1.4) 40E1F37A-3BAE-3E82-A8CE-8DEB364664E3 <145 143 39 7 5 4 3 1>
  147    0 0xffffff7f83308000 0x5000     0x5000     org.virtualbox.kext.VBoxNetFlt (5.1.4) 1E11B050-BCCD-31BF-82AC-DACA1E2EB803 <143 7 5 4 3 1>
  148    0 0xffffff7f8330d000 0x6000     0x6000     org.virtualbox.kext.VBoxNetAdp (5.1.4) 1EE6EA19-32FB-3EF4-93B4-E4AF47EF4051 <143 5 4 1>
  149    0 0xffffff7f83313000 0xe000     0xe000     com.McAfee.AVKext (1) 7116ADFA-51F7-3BC3-8206-BEC1C180A1E0 <4 1>
bhushan:~$
}}}
NOTE: Uninstalling McAfee is not an option for me as this is a company provided machine & IT team would not be happy with it.

Logs attached:

VBox.log - for the DevVM [oracle DB VM from 2013]

CentOS-6.4-i386-minimal-2016-09-12-10-52-32.log - for the CentOS VM",Bhushan
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
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
15979,vertio-net causes Cisco AnyConnect instablity,VirtualBox 5.1.6,Windows,2016-09-23T18:21:10Z,2016-09-23T18:21:10Z,2016-09-23T18:21:10Z,"I have been running a Windows (8.1 and 10) guest for several years, using AnyConnect from the guest to VPN into our corporate network.  At some point I transitioned to using the virtio-net driver and it worked well for a long time.  

At some point a few months ago the VPN became very unstable.  I would experience random disconnects, especially during periods of constant VPN utilization (screen sharing, large file transfers, etc).  

When it disconnected, it would reconnect, but would not configure the ip stack properly and I could not pass any traffic without disconnecting and reconnecting.  I lived with this for several months and decided to finally take some time to see if I could find a solution.

Ultimately, going to a virtualized Intel PRO/1000 MT Desktop adapter seemed to fix the problems.  For some reason it appears that recent versions of AnyConnect stopped working well with the virtio-net adapter.

I don't know if this would be an AnyConnect, a VirtualBox, or a VirtIO-net issue, and will not be offended if this gets closed immediately.  However I wanted to be sure it was documented somewhere for anyone else who may experience these issues in the future.",J. Fry
15991,Ethernet connection hangs on guest,VirtualBox 5.1.6,Windows,2016-09-27T08:34:45Z,2016-09-27T11:26:59Z,2016-09-27T11:26:59Z,"Ethernet connection on guest is hanging periodically.
After disconnection/connection back it starts to work again",leonik
15996,MacOS 10.12 Bridge sends bad chksum,VirtualBox 5.1.6,Mac OS X,2016-09-28T06:56:21Z,2016-09-28T15:40:18Z,2016-09-28T15:40:18Z,"Hello,

i have a special configuration and the shinny new macos 10.12. So It could be that macos is the cause of this error too.

I'm running 5.1.6 on 10.12 macos and installed a own bridge on macos with:
{{{
ifconfig bridge0 create
ifconfig bridge0 10.24.1.1/24 up
ifconfig bridge0 inet6 fd00::10:24:1:1/64 up
}}}
than I bind my guest to these bridge0 and on ipv4 all is good but on ipv6 ping's are working
but any tcp or udp doesn't. 
The root cause is that the guest host receives packet with a wrong checksum:
{{{
1	0.000000	fd00::10:24:1:1	fd00::10:24:1:201	TCP	98	53596→22 [SYN, ECN, CWR] Seq=0 Win=65535 [TCP CHECKSUM INCORRECT] Len=0 MSS=1440 WS=32 TSval=497945749 TSecr=0 SACK_PERM=1
}}}
If add another guest to that bridge and try so access my dest from these new (""linux"") guest everything is ok. Like:
{{{
1	0.000000	fd00::10:24:1:149	fd00::10:24:1:201	TCP	94	45678→22 [SYN] Seq=0 Win=28800 Len=0 MSS=1440 SACK_PERM=1 TSval=301306 TSecr=0 WS=128
}}}
I was not able to check the chksum generation if i plugin a real device to the macos bridge.

And i did not have these ipv6 use case days before where i had run 10.11, so this problem might be new or old from virtualbox or macos ...
I decided to report to you out of the fact that you are not manage the bridges on macos like on linux where you add a virtual device to the bridge. This is a kind of odd-:)

Cheers
meno

P.S.
{{{
$ ifconfig bridge0
bridge0: flags=8963<UP,BROADCAST,SMART,RUNNING,PROMISC,SIMPLEX,MULTICAST> mtu 1500
	options=63<RXCSUM,TXCSUM,TSO4,TSO6>
	ether 7a:31:c1:9c:ed:00
	inet 10.24.1.1 netmask 0xffffff00 broadcast 10.24.1.255
	inet6 fe80::7831:c1ff:fe9c:ed00%bridge0 prefixlen 64 scopeid 0x8
	inet6 fd00::10:24:1:1 prefixlen 64
	Configuration:
		id 0:0:0:0:0:0 priority 0 hellotime 0 fwddelay 0
		maxage 0 holdcnt 0 proto stp maxaddr 100 timeout 1200
		root id 0:0:0:0:0:0 priority 0 ifcost 0 port 0
		ipfilter disabled flags 0x2
	Address cache:
	nd6 options=201<PERFORMNUD,DAD>
	media: <unknown type>
	status: inactive
}}}",Meno Abels
16034,Connection lost in guest when restart failed due to lack of memory,VirtualBox 5.0.26,Windows,2016-10-05T14:30:24Z,2016-10-06T12:59:59Z,2016-10-06T12:59:59Z,"Sometimes, at startup, VirtulBox complains about the lack of memory (I didn't write down the exact message) and I have to close the VM and launch it again. Then it works. I don't mean restarting the guest. Just record the state of the machine, close the application and run it again.

This is not a big deal and I assume it is due to a lack of RAM on the host, so nothing VirtualBox can do much about.

The issue is that when I do that, sometimes (maybe each time, I'm not 100% sure this is systematic), I lose the connection.

Rather than restarting the guest, this can be solved by restarting network-manager service:

    systemctl restart network-manager

Not sure what the root-cause is and if VirtualBox is to blame. At least if someone encounters the same issue, a workaround is documented here.

Host: Windows 7
Guest: Linux Debian Jessie

There's nothing specifically related in the VM log.",JerNob
11455,"VirtualBox 4.2.6 , Guest freeze / hangs on network load",VirtualBox 4.2.6,other,2013-02-04T15:28:57Z,2016-10-07T18:06:36Z,2016-10-07T18:06:36Z,"Hi,
   Using VirtualBox 4.2.6 on FreeBSD 8.3 host (64bit), and Debian 7.0 guest with kernel : 3.2.0-4-amd64.

   When doing a large rsync of multi gigabyte file sizes, the Guest completely freezes , 
  - Console is frozen (can't type) 
  - Network is down (ping host unknown)
  
It freezes for about 5 minutes, then the transfer aborts and the machine comes back.

No logs in VBox.log when the condition occurs.
No logs in the Guest messages, kern.log or anything...

I tried all the Network Adapters they all fail at some point from 20 Gigs transferred to 200G.

This happens only with more then 1 CPU, with only one CPU it's stable. (Tested 1, 6 and 12 CPU on Guest) on Host : Xeon(R) CPU E5-2620 

Other possibly useful information : I'm using dm-crypt on the Guest to encrypt incoming traffic, I will test without this to rule it out. 

I also at one time using virt-io had this error log :
virtio_net virtio0: output:id 138 is not a head!

But since it freezes using all the network adapters I assume it's not virtio related...

Any help is appreciated , I will perform any test requested ...


Thank you very much!





 


 ",hexa
15952,virtio slow and have unstable performance when VM have >1 vCPU,VirtualBox 5.1.6,Linux,2016-09-18T19:38:55Z,2016-10-08T10:33:16Z,2016-10-08T10:33:16Z,"
Hi.

I have DL380 G7, with latest CentOS 6. Also, kernel is upgraded to kernel-lt - 3.10.x. Host have 2 NIC's enabled (configured).

I'm using latest VirtualBox 5.1.x.

Test scenario involves two VM's, and both of them are attached to both host NIC's (bridge). In VM's, both vNIC are set as virtio, and vCPU is set to 1. VM's are Centos 6 also.

Everything works ok - i'm getting >140Mbytes/s on all interfaces (eth0<->eth0 and eth1<->eth1 from VM to VM).

Now, on one of those VM's, increase number of vCPU to 2. Things now start to behave erratic.

For a short time, eth0<->eth0 is ok, and then starts to fluctuate widely - from ~100Kb/s to 50Mb/s. At the same time eth1<->eth1 stays >140Mb/s.

In rare occasion, eth0 can work ok, eth1 poorly.

Changing one of interfaces with Intel (so only one vNIC is virtio) makes things work stable - if eth0 was switched to Intel, it is >20Mb/s, while eth1 stays >140Mb/s.

From this, i would conclude that there is some kind of race condition with virtio when VM uses vCPU>1.

Also, i do not know how to debug this furtherer. Please advise.

Regards,

H.",Hrvoje
14593,Please add support to more network cards,VirtualBox 5.0.2,Linux,2015-09-15T19:45:13Z,2016-10-11T03:11:55Z,2016-10-11T03:11:55Z,"Hi!

I'm trying to run Siemens WinAC RTX 2010 on Windows XP SP3 Pro English guest. It installs and works fine, but this software needs some specific network cards to be enabled to work with network. The supported network cards by Siemens WinAC RTX 2010:

Intel Gigabit CT (chip set: Intel I82574L)
Intel 2-Port PCIe (chip set: Intel  I82571EB)
Intel Pro/1000 PL (chip set: Intel 82573L)
Intel Pro/1000 GT (chip set: Intel 82541PI)
Intel Gigabit (chip set:  82571EB) 

But none of these network cards are supported by Virtualbox.

So, Can the Virtualbox development team add support to one or two network cards from this list?",fluisgirardi
16096,"with a socks proxy set in gnome, guest OS randomly freeze black screen",VirtualBox 5.1.6,Windows,2016-10-20T19:42:29Z,2016-10-21T06:22:48Z,2016-10-21T06:22:48Z,"Description of problem:
when a socks proxy is set in gnome, in the guets OS, gnome freezes black screen, randomly without halting the system

Version-Release number of selected component (if applicable):
VitualBox 5.1.6 on Windows7 SP1 64
Fedora 24 4.7.6-200.fc24.x86_64
Gnome ver 3.20.4

Please note:
I'm using VitualBox 5.1.6 on Windows7 SP1 64.
I'm inside a VirtualBox VM where Fedora 24 is my Guest OS.
I installed the VirtualBox Guest Additions ver 5.1.7-110797
I configured the KVM acceleration.
I configured the VM network to Bridged Adapter.
I'm using Snort in Fedora. 

How reproducible:
happens randomly 

Steps to Reproduce:
1. Configure a socks proxy in NetworkManager, in the guest OS

Actual results:
Randomly the screen freeze blank, although the system appears not halted but it is not possible to interact with it


Expected results:


Additional info:
unset the sock proxy all run normally",par7133_2
15874,"VBOX session crashes - aborted - on NAT: DHCP offered IP address. Fixed in the past, reintroduced.",VirtualBox 5.1.4,Linux,2016-09-01T15:02:53Z,2016-10-27T14:05:46Z,2016-10-27T14:05:46Z,"Hallo

Running Windows 7 guest, hosted in VBox 5.1.4 under Fedora 24. Same problem on RHEL6 and RHEL7.

Session of VM randomly crashes without notice, getting status '''ABORTED'''. No obvious errors in neither Windows not Linux logs. In VBox log, after every crash there is this single message as last one:

'''NAT: DHCP offered IP address 10.0.2.15'''

I've seen same problem beeing solved in much older version of VBox: https://www.virtualbox.org/ticket/13874

I guess the error got reintroduced along the VBox evolution.

Could you please check and fix according to previous solution?

Thanks a lot",Flamestring
16139,Invisible network adapter in network settings,VirtualBox 5.1.8,Windows,2016-11-02T09:09:45Z,2016-11-02T09:09:45Z,2016-11-02T09:09:45Z,"Host: Windows 7 Pro 64 bit, Intel Core i5-2400, 8 GB RAM

Guest: All

Problem:
On windows hosts not all network adapters are visible in dropdown list. 
On a computer with two onboard NICs and one PCI NIC only one of the onboard NICs and the PCI NIC is shown in the list. The second onboard NIC is missing in the list. VirtualBox NDIS6 Bridged Networking Driver is installed and activated for all three adapters. ",KilO76
16120,VirtualBox 5.1.8r111374 aborts Debian guest after random period - NAT?,VirtualBox 5.1.8,Linux,2016-10-26T21:56:41Z,2016-11-22T08:28:23Z,2016-11-22T08:28:23Z,"I have a Debian Jessie guest running on a Arch host. After a seemingly random period of time, the guest will transition to the ""aborted"" state. I am yet to observe it happening, I normally notice after I find my VirtualBox guest has disappeared after a few hours. 

I think it's possible that this is associated with an older ticket. Sorry if I have not formatted this ticket correctly, this is my first time doing so.

I will provide any information you require, please ask.



",sam.4325224
16128,"Client loses TCP/UDP connectivity, VirtualBox on host uses 100% CPU",VirtualBox 5.1.8,Linux,2016-10-30T08:24:52Z,2016-11-24T08:00:57Z,2016-11-24T08:00:57Z,"I have a guest debian server running on ubuntu host (both 64 bits). Networking mode was set to NAT and port forwarding was set for guest ports 22 and 80 to control and use this server.

It worked fine during low-load testing, but when it come to production with some load (1-2 requests per seconds from around the world), following issue was discovered:

- It's happening after some time, usually after 2-3 days but last time it happens after 7 hours only.
- CPU usage of VBoxHeadless process on host jumps and stay at 100%, although there is no any load on the guest.
- Guest system continues to work but it cannot nor accept nor create new TCP connections (existing TCP connections, e.g. early opened ssh session, continues to work).
- Outgoing TCP connection from the guest (e.g. wget) fails with error code ""Network is unreachable"". This error code is a clear sign that ""bad thing happened"".
- DNS resolving on guest fails so it seems that UDP is affected too.
- PINGs from guest are working! So I consider that network, routing, etc is OK, and the bug is in NAT code.

Of course there are no any messages in any logs when it happens.

I think that symptoms are quite similar to Bug #15223, but don't know could they have common reason or not. First discovering this issue in 4.3.old, I've upgraded to 4.3.40 and then to 5.1.8, but the issue is still here.

",Roman Trunov
16263,VDE networking support seems not to be present,VirtualBox 5.0.24,Linux,2016-12-03T22:26:40Z,2016-12-03T23:06:23Z,2016-12-03T23:06:23Z,"Hi,

I am trying to use my vbox in conjunction with VDE switch.
Checked in the docs, that it should be compiled with --enable-vde flag to make it effective so that in interface's properties I will be able to choose VDE next to other native options.

I got virtualbox sources for Ubuntu 16.04 and I can see the VDE flag is set to 1 by default. Recompiled it for the formality and installed those packages, still there is no VDE option present.

Can you guys confirm you still support VDE?",maq123
14457,cannot ping host <--> VMs after upgrade to VirtualBox 5.0.x with NDIS6 driver,VirtualBox 5.0.2,Windows,2015-08-16T19:21:34Z,2016-12-13T10:29:47Z,2016-12-13T10:29:47Z,"In reference to this forum post:

https://forums.virtualbox.org/viewtopic.php?f=6&t=69597

after upgrading to VirtualBox 5.0.x I could no longer ping between the host and the VMs (bridged mode), while the VMs could still ping each other, and all (host and VMs) could still ping other computers on the same subnet.  By reverting back to using the NDIS5 driver, all worked properly again, so the issue is related to some bug/defect in the new NDIS6 driver implementation.
",qd01a
16345,fatal error while FreeBSD VM is configuring network interface for IPv6,VirtualBox 5.1.12,other,2017-01-02T00:09:59Z,2017-01-02T00:23:54Z,2017-01-02T00:23:54Z,"fatal error while FreeBSD VM is configuring network interface for IPv6
The network interface is 'bridged' to my real nic.

I'm installing pfSense 2.4beta latest snapshot and configuring a 6to4 or 6rd on the wan nic.

Logs attached.",PiBa-NL
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
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
16383,cannot ping but can ssh and http,VirtualBox 5.1.12,Windows,2017-01-13T06:12:33Z,2017-01-20T02:17:57Z,2017-01-20T02:17:57Z,"Host: Windows 10
Guest: Centos 5
Network: NAT

Why: cannot ping in guest, but can http or ssh.

Debug: 
 1. Use tcpdump in guest and host, will see icmp request is sent to host and host resent this packet to the target, but after got icmp reply, host will try to resent reply to 10.96.1.19, then return ""unreachable network""
 1. Try to capture virtual machine packet by(there is only lo0 and eth0 interface in my guest):
{{{
VBoxManage.exe modifyvm ""redhat32"" --nictrace1 on --nictracefile1 c:\Users\xxxx\netlog.pcap
}}}
 But nothing is logged.
",JacksonZheng
15565,Host adapter showing zero bytes traffic,VirtualBox 5.0.24,Windows,2016-07-04T08:34:02Z,2017-01-25T09:26:28Z,2017-01-25T09:26:28Z,"On Windows 10 x64, I cannot get Microsoft Edge to connect to Virtual Box on the host adapter no matter what I try. (and I have researched this thoroughly on the web)

While trying to get the above working, I noticed that the host adapter shows 0 bytes of traffic, even though traffic is definitely passing through it.

My assumption is that there is something anomalistic with the host adapter on Windows 10, and I am hoping that it is this that is preventing Edge from accessing my guest OS.

For more info on this topic please see here:

https://forums.virtualbox.org/viewtopic.php?f=6&t=76805&sid=03dc09ac43bda2a553c78e31a5b89232&start=15
",oivey
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
16229,Blue screen of the death when you change to Bridged Adapter,VirtualBox 5.1.10,Windows,2016-11-25T08:41:01Z,2017-02-11T08:36:03Z,2017-02-11T08:36:03Z,"All worked fine before update of my network driver. (I updated by KillerSuite_1.1.65.1752_Win7_Win81_Win10).

But after update, when I share internet using Bridge, blue screen of the death for host machine is appeared. If i don't have connection to the internet on host machine (Wi-Fi/Ethernet), all are working fine, but after connection all crash too.   

version of Vbox is 5.1.10 r112026 (Qt5.6.2)
Both(host and guest) have windows 10

Could you please tell, is it problem of Vbox or my driver? What is the best way to resolve it? Rollback driver\create ticket for them or is it Vbox problem? ",AlekseiG
13889,VirtualBox Bridged Networking Driver error,VirtualBox 4.3.22,Windows,2015-02-24T17:13:50Z,2017-02-24T06:32:40Z,2017-02-24T06:32:40Z,"Hi all!

If use Intel mainbord ethernet adapter and like setting VLAN - installed and ENABLED VirtualBox Bridged Networking Driver -, beyond possibility enabled status on for lan adapter.

If disabled VirtualBox Bridged Networking Driver in LAN adapter properties, work anyone.

(guest not running)",Lacus
16521,no NetworkBridge Mode,VirtualBox 5.1.14,Windows,2017-02-28T18:40:31Z,2017-02-28T18:40:31Z,2017-02-28T18:40:31Z,"NAT works fine
NetworkBridge Mode dont work.
It gets an IP-Adress, ping works,
but no trafic, no Website loads, div. ...

last things done:
Update from 5.0.32 to 5.1.14rxxxxxx

Machines:
Ubuntu 16.04,
W10pro
W7pro
Xubuntu
Linux Mint Sarah
WinXP-Pro
ipFire
pfSene
",Bardo
16519,Network bandwidth limit in GUI,VirtualBox 5.1.14,Windows,2017-02-27T15:21:43Z,2017-03-09T15:17:34Z,2017-03-09T15:17:34Z,It would be good if one could adjust the network speed or limitation easily in the GUI. The detour via the VBoxManager is very cumbersome.(https://www.virtualbox.org/manual/ch08.html --> bandwidthctl),LMS23
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
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
16605,Network dropouts in guest since Windows 10 update to 1607 version,VirtualBox 5.1.18,Windows,2017-03-24T15:38:35Z,2017-03-31T10:07:18Z,2017-03-31T10:07:18Z,"I got here following situation. I have a Windows 10 x64 guest on the same OS host. Right now I reduced the amount of installed programs in the guest to the minimum to find the culprit. So right now there is an antivirus (latest Nod32), Firefox and MP3 Player (Xmplay) beside the OS itself. I use the last program for Internet radio since XP days, and there were no problem until now, in and outside the VM. 

Since guest update to the 1607 I can see following behavior: after 15 or 20 minutes of the streaming player starts to buffer at 70-80 % spontaneously around once in a minute, which breaks a streaming experience. One still can listen to the radio, but this is a little bit annoying. This problem only occurs if the Firefox also running in the guest. Something, I don’t know what, but probably some advertisement or data refresh, loads a little amount of the data over and over again once in nearly a minute. I got some network bandwidth pictures which explain the network flow better. But the problem isn’t a bandwidth itself – I can run a bandwidth test, which would use the whole bandwidth and still there would be no buffering. The problem is a timing, because as one can see we have something like 6 or 8 KB/s from the stream constantly, but once in a while the browser adds some 18-20 KB/s to it. So after a while there are some de-synchronization in the flow, which causes the buffering.

This only happens in the guest and only if the browser running with some sites open. If one turns the browser off, there is no buffering. Also, this can’t be reproduced running same player and stream on the host, neither with Firefox also opened on the host with some sites in it, or with Firefox running in the guest, causing the same traffic shape on the host. First of all a thought that this was a new issue with a new VB version, but I tested this with following versions (5.0.30 - 36, 5.1.6, 5.1.10, 12, 14, 16, 18) and the picture is always the same. Changing network adapter from 82540EM to paravirtualized also brings no cure. I tested it with following version of the network adapter drivers (virtio-win-0.1.110, 112, 113, 117, 118, 126, 134), but it always looks the same. There were also no such problems as I updated the host first, before the guest. The clean install of the guest OS from the scratch also doesn’t change anything in this case, but installing the previous version of Windows 10 (1511) in the guest solves the problem. I think, that the problem caused by some TCP/IP optimization in the new Windows version, as described [[https://blogs.technet.microsoft.com/networking/2016/07/18/announcing-new-transport-advancements-in-the-anniversary-update-for-windows-10-and-windows-server-2016/|here]], the Initial Congestion Window 10 probably. If this is important – I hear following [[https://rfe04.akacast.akamaistream.net/7/509/437762/v1/ibb.akacast.akamaistream.net/rfe04?download=1|stream]] for example, but I think any other stream should also do the job. I would like to debug the network stack in the guest, but I don’t know how.

VM is running in the NAT mode. I hope that my description of the issue is clear, in spite of so much text.",boxer01
16577,VirtualBox Networking causing BSOD,VirtualBox 5.1.14,Windows,2017-03-18T10:38:03Z,2017-04-06T11:26:54Z,2017-04-06T11:26:54Z,"After installation of VirtualBox I see very often BSOD with error message DRIVER_IRQL_NOT_LESS_OR_EQUAL caused by nwifi.sys. This actualle makes the computer more or less useless.

I have found out that installing VirtualBox without networking solves the problem (restored backup of computer to point without any virtualbox installed and retried. Also did it again and installed with networking and BSOD is back on first reboot).

Host Dell XPS13, Windows 10 Pro 64bit build 10586.839. It's not affected bu guest OS as the BSOD shows up just by installing VirtualBox so there is some driver issue in the host OS/VirtualBox",TurboJens
16233,Vbox bridge loses outer QinQ tag,VirtualBox 5.1.10,Linux,2016-11-25T20:03:58Z,2017-04-24T16:13:18Z,2017-04-24T16:13:18Z,"Virtualox bridge loses outer QinQ tag if bridged with Linux TAP interface

Steps to reproduce:

 1. Install OS Linux on PC.
 In my case: Ubuntu 14.04.5
 kernel 4.2.0-42-generic X86_64

 2. Install !VirtualBox (in my case ver. 5.1.10 !r112026 (Qt5.6.1)) from [http://download.virtualbox.org/virtualbox/5.1.10/virtualbox-5.1_5.1.10-112026~Ubuntu~trusty_amd64.deb here]

 3. Download and install guest Linux OS.
 In my case Ubuntu 16.04.01 from [http://releases.ubuntu.com/16.04/ubuntu-16.04.1-server-i386.iso here]

 4. On host system create tap interface:
{{{
ip tuntap add dev tap10 mode tap
ip link set dev tap10 up
}}}
 5. In guest VM netwrok settings set network adapter to ""bridge"" mode to interface tap10
{{{
vboxmanage modifyvm TESTVM --nic2 bridged
vboxmanage modifyvm TESTVM --bridgeadapter2 tap10
}}}
	
 All other network settings may be set to default. I tried to change the ""adapter type"" and ""promiscuous mode"". Their change does not change the result. 
	
 6. Create QINQ subinterface on host interface tap10 with inner vlan 2000 and outer vlan 100 and set ip address (type of protocol 802.1q or 802.1ad not important. This change does not change the result):
{{{
ip link add link tap10 tap10.100 type vlan proto 802.1q id 100
ip link set up tap10.100
ip link add link tap10.100 tap10.100.2000 type vlan proto 802.1q id 2000
ip link set up tap10.100.2000
ip addr add 10.11.12.1/24 dev tap10.100.2000
}}}
	
 7. Start up guest VM and determine which interface bridged with tap10
	In my case this is a '''enp0s8'''
 8. Create QINQ subinterface on VM interface which bridged with tap10 with inner vlan 2000 and outer vlan 100 and set ip address (type of protocol 802.1q or 802.1ad not important. This change does not change the result):
{{{
ip link set up enp0s8
ip link add link enp0s8 enp0s8.100 type vlan proto 802.1q id 100
ip link set up enp0s8.100
ip link add link enp0s8.100 enp0s8.100.2000 type vlan proto 802.1q id 2000
ip link set up enp0s8.100.2000
ip addr add 10.11.12.2/24 dev enp0s8.100.2000
}}}
 9. start watch for traffic on host PC on tap10 interface:
{{{
tcpdump -i tap10 -vvv -e
}}}
 for creating pcap file
{{{
tcpdump -i tap10 -vvv -e -w qinqPC.pcap
}}}
	
 10. start watch for traffic in guest VM on ""physical"" interface:
{{{
tcpdump -i enp0s8 -vvv -e
}}}
 for creating pcap file
{{{
tcpdump -i enp0s8 -vvv -e -w qinqVM.pcap
}}}
	
 11. Try to ping 10.11.12.2 from 10.11.12.1 (Host PC => Guest VM)
{{{
ping 10.11.12.2
}}}
	
 12. You should get the following results:[[BR]]
 on physical PC (tap10):
{{{
21:22:06.345997 f6:4e:f0:31:76:45 (oui Unknown) > Broadcast, ethertype 802.1Q (0x8100), length 50: vlan 100, p 0, ethertype 802.1Q, vlan 2000, p 0, ethertype ARP, Ethernet (len 6), IPv4 (len 4), Request who-has 10.11.12.2 tell 10.11.12.1, length 28
21:22:07.346093 f6:4e:f0:31:76:45 (oui Unknown) > Broadcast, ethertype 802.1Q (0x8100), length 50: vlan 100, p 0, ethertype 802.1Q, vlan 2000, p 0, ethertype ARP, Ethernet (len 6), IPv4 (len 4), Request who-has 10.11.12.2 tell 10.11.12.1, length 28
21:22:08.346032 f6:4e:f0:31:76:45 (oui Unknown) > Broadcast, ethertype 802.1Q (0x8100), length 50: vlan 100, p 0, ethertype 802.1Q, vlan 2000, p 0, ethertype ARP, Ethernet (len 6), IPv4 (len 4), Request who-has 10.11.12.2 tell 10.11.12.1, length 28
}}}
 on VM (enp0s8):
{{{
21:30:21.737754 f6:4e:f0:31:76:45 (oui Unknown) > Broadcast, ethertype 802.1Q (0x8100), length 64: vlan 2000, p 0, ethertype ARP, Ethernet (len 6), IPv4 (len 4), Request who-has 10.11.12.2 tell 10.11.12.1, length 46
21:30:22.738035 f6:4e:f0:31:76:45 (oui Unknown) > Broadcast, ethertype 802.1Q (0x8100), length 64: vlan 2000, p 0, ethertype ARP, Ethernet (len 6), IPv4 (len 4), Request who-has 10.11.12.2 tell 10.11.12.1, length 46
21:30:23.737981 f6:4e:f0:31:76:45 (oui Unknown) > Broadcast, ethertype 802.1Q (0x8100), length 64: vlan 2000, p 0, ethertype ARP, Ethernet (len 6), IPv4 (len 4), Request who-has 10.11.12.2 tell 10.11.12.1, length 46
}}}

As seen, on VM side is missing outer vlan (vlan 100)

If a try to ping from VM to PC the outer vlan in right place only in ARP request. In ARP reply (PC -> VM) the outer vlan is missing.
on physical PC:
{{{
21:35:12.342498 08:00:27:5d:26:01 (oui Unknown) > Broadcast, ethertype 802.1Q (0x8100), length 64: vlan 100, p 0, ethertype 802.1Q, vlan 2000, p 0, ethertype ARP, Ethernet (len 6), IPv4 (len 4), Request who-has 10.11.12.1 tell 10.11.12.2, length 42
21:35:12.342501 08:00:27:5d:26:01 (oui Unknown) > Broadcast, ethertype 802.1Q (0x8100), length 64: vlan 100, p 0, ethertype 802.1Q, vlan 2000, p 0, ethertype ARP, Ethernet (len 6), IPv4 (len 4), Request who-has 10.11.12.1 tell 10.11.12.2, length 42
21:35:12.342521 f6:4e:f0:31:76:45 (oui Unknown) > 08:00:27:5d:26:01 (oui Unknown), ethertype 802.1Q (0x8100), length 50: vlan 100, p 0, ethertype 802.1Q, vlan 2000, p 0, ethertype ARP, Ethernet (len 6), IPv4 (len 4), Reply 10.11.12.1 is-at f6:4e:f0:31:76:45 (oui Unknown), length 28
21:35:13.343489 08:00:27:5d:26:01 (oui Unknown) > Broadcast, ethertype 802.1Q (0x8100), length 64: vlan 100, p 0, ethertype 802.1Q, vlan 2000, p 0, ethertype ARP, Ethernet (len 6), IPv4 (len 4), Request who-has 10.11.12.1 tell 10.11.12.2, length 42
21:35:13.343495 08:00:27:5d:26:01 (oui Unknown) > Broadcast, ethertype 802.1Q (0x8100), length 64: vlan 100, p 0, ethertype 802.1Q, vlan 2000, p 0, ethertype ARP, Ethernet (len 6), IPv4 (len 4), Request who-has 10.11.12.1 tell 10.11.12.2, length 42
21:35:13.343516 f6:4e:f0:31:76:45 (oui Unknown) > 08:00:27:5d:26:01 (oui Unknown), ethertype 802.1Q (0x8100), length 50: vlan 100, p 0, ethertype 802.1Q, vlan 2000, p 0, ethertype ARP, Ethernet (len 6), IPv4 (len 4), Reply 10.11.12.1 is-at f6:4e:f0:31:76:45 (oui Unknown), length 28
}}}

on VM:
{{{
21:35:10.614413 08:00:27:5d:26:01 (oui Unknown) > Broadcast, ethertype 802.1Q (0x8100), length 50: vlan 100, p 0, ethertype 802.1Q, vlan 2000, p 0, ethertype ARP, Ethernet (len 6), IPv4 (len 4), Request who-has 10.11.12.1 tell 10.11.12.2, length 28
21:35:10.614556 f6:4e:f0:31:76:45 (oui Unknown) > 08:00:27:5d:26:01 (oui Unknown), ethertype 802.1Q (0x8100), length 64: vlan 2000, p 0, ethertype ARP, Ethernet (len 6), IPv4 (len 4), Reply 10.11.12.1 is-at f6:4e:f0:31:76:45 (oui Unknown), length 46
21:35:11.615368 08:00:27:5d:26:01 (oui Unknown) > Broadcast, ethertype 802.1Q (0x8100), length 50: vlan 100, p 0, ethertype 802.1Q, vlan 2000, p 0, ethertype ARP, Ethernet (len 6), IPv4 (len 4), Request who-has 10.11.12.1 tell 10.11.12.2, length 28
21:35:11.615549 f6:4e:f0:31:76:45 (oui Unknown) > 08:00:27:5d:26:01 (oui Unknown), ethertype 802.1Q (0x8100), length 64: vlan 2000, p 0, ethertype ARP, Ethernet (len 6), IPv4 (len 4), Reply 10.11.12.1 is-at f6:4e:f0:31:76:45 (oui Unknown), length 46
21:35:12.615063 08:00:27:5d:26:01 (oui Unknown) > Broadcast, ethertype 802.1Q (0x8100), length 50: vlan 100, p 0, ethertype 802.1Q, vlan 2000, p 0, ethertype ARP, Ethernet (len 6), IPv4 (len 4), Request who-has 10.11.12.1 tell 10.11.12.2, length 28
}}}


It does not look as a TAP bug. If a try to bridge two tap interface via linux bridge, and create QINQ subinterfaces for each of them, this problem does not appear.

PCAP-s from VM and PC (qinqVM.pcap and qinqPC.pcap) in attachement.

Thanks in advance!",Arc
16695,VBoxNetNAT refuses connections for port-forwarding after one day or two,VirtualBox 5.1.20,Linux,2017-04-25T09:28:42Z,2017-04-25T12:17:09Z,2017-04-25T12:17:09Z,"I started using NAT network since several months ago.  My setup is quite simple: Linux host (CentOS 7.3) running two Windows 7 guests.  All guests use NAT network with static IPs.  Port-forwarding is configured on the NAT network.


{{{
NAT network: 10.0.2.1/24
Guest 1 IP: 10.0.2.11
Guest 2 IP: 10.0.2.12
Forward 1: <host_ip>:5911 <--> 10.0.0.11:5900
Forward 2: <host_ip>:5912 <--> 10.0.0.12:5900
}}}


Everything work great, until, after some time, maybe one day or two, connections to host port 2211/2212 got rejected.  One solution I find is to restart guest OS, sometime more than once, until the port-forward is normal again.

During the whole process (good --> bad --> restart --> good again), I can see that port 2211/2212 are always bound by process /usr/lib/virtualbox/VBoxNetNAT, and its pid never changed.

When connections are rejected on port 5911 and 5912, guests can connect to each other's 5900 port, which rules out guests failures.

Another observation is, sometimes the restart of one guest OS can solve problems for all guests.
",Steve Sun
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
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
16807,Interface ('VirtualBox Host-Only Ethernet Adapter #2') is not a Host-Only Adapter interface (VERR_INTERNAL_ERROR).,VirtualBox 5.1.22,Windows,2017-06-02T20:37:24Z,2017-06-02T21:07:58Z,2017-06-02T21:07:58Z,"1) Context
Virtual Version : v5.1.22
Host : Windows 10
Guest : Debian v8.7

2) Problem description : 
An error message appears when starting my Guest.

3) Error Message :
Interface ('VirtualBox Host-Only Ethernet Adapter #2') is not a Host-Only Adapter interface (VERR_INTERNAL_ERROR).
Code d'erreur : 
E_FAIL (0x80004005)
Composant : 
ConsoleWrap
Interface : 
IConsole {872da645-4a9b-1727-bee2-5585105b9eed}

4) Usefull infos :
I suspect that the problem was appeared when I have updated VirtualBox from v5.1.10 to v5.1.22
The host only network adapter was #2 and now as you can see in screen shots
this is the #3. So I suspect there a ""binding"" problem between #2 (old version of VBox) and #3 (new version of Vbox)
Is there new network devices between v5.1.10 and v5.1.22 ?
Is the default network device for my Host was changed ?

Best Regards",ManWithNoName
16789,VM dropped from network because of DHCP problems,VirtualBox 5.1.22,Windows,2017-05-26T20:42:05Z,2017-06-13T15:41:09Z,2017-06-13T15:41:09Z,"I have a VM in the NAT mode. It happened only once last month, but suddenly guest network lost its internet connection. So the card and network was here, but it has this standard 169 IP address and because of this no access to internet. Only the shutdown and start of the guest helped here. As one can see from the log, it looks like VM suddenly got some problems with DHCP in my local network, where my router is a DHCP server, and lost his 10.x.x.x address. Therefore, it got an 169.x.x.x address. Both guest and host are latest Windows 10.",boxer01
16851,Win 7 x64 Guest on Ubuntu 16.04 Host Freeze after ~4 Hours,VirtualBox 5.1.22,Linux,2017-06-21T18:34:27Z,2017-06-22T08:50:14Z,2017-06-22T08:50:14Z,"Have had a persistent problem for some time now (unsure when it started) whereby my Windows 7 x64 guest will completely lock up and is unresponsive.  VirtualBox console and other running non-Windows VMs do not seem to be affected.  The VirtualBox interface is still active and I can manipulate settings via the menu options in the GUI, but the guest OS GUI is frozen at the point it stopped working.

Saving State, then Restoring doesn't affect the outcome - only way to recover is to power off the guest VM and start it up again.

Reported this issue over in the forum (https://forums.virtualbox.org/viewtopic.php?f=7&t=82819) and was advised that this may be a rarely reproducible issue involving the NAT network subsystem and that logging a bugtrac ticket would be the best way to address this issue.

This appears to be the point at which the guest crashes (from Vbox.log):

{{{
00:26:21.080234 NAT: resolv.conf: nameserver 192.168.56.50
00:26:21.080254 NAT: resolv.conf: nameserver 127.0.1.1
00:26:21.080262 NAT: Adding domain name laptop
00:26:21.080264 NAT: DNS#0: 192.168.56.50
00:26:21.080266 NAT: DNS#1: 127.0.1.1
00:26:21.080269 NAT: DHCP offered IP address 10.0.2.15
00:26:22.688094 NAT: dnsproxy: timeout: req 00007f56d4071640 dnsgen 2 != 3 on socket 50 (udp) exp. in -427 state=SS_ISFCONNECTED f_(addr:port)=10.0.2.3:53 l_(addr:port)=10.0.2.15:50425 name=0.0.0.0:54045
03:01:30.079058 NAT: Can't allocate mbuf
03:01:38.957814 NAT: Link up
03:01:44.952776 NAT: Link up
03:01:50.966947 NAT: Link up
03:01:56.962828 NAT: Link up
03:02:02.966836 NAT: Link up
03:02:23.001524 NAT: Link up
03:02:29.001906 NAT: Link up
03:02:32.603387 VMMDev: vmmDevHeartbeatFlatlinedTimer: Guest seems to be unresponsive. Last heartbeat received 4 seconds ago
}}}


Full vbox.log file attached.
Core dump is available, but may contain sensitive data so I'd prefer not to attach to this ticket.  Have an email out to Frank Mehnert, but would gladly take instruction from elsewhere on how to get this to interested parties, securely.",John Mackoy
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
16902,P2P connections die quickly under certain circumstances,VirtualBox 5.1.22,Windows,2017-07-14T16:55:53Z,2017-07-15T09:03:45Z,2017-07-15T09:03:45Z,"Conditions to replicate are rather unusual so please cope with me:
- an application using P2P connectivity is let to operate for a few minutes (5 minutes should be more than enough);
- you may close the P2P application when you want to get to the next step. Wherever you close the P2P application and its active connections won't make a difference;
- pause the VM execution for a few minutes (5 minutes should be more than enough);
- when resuming VM try to repeat the first step and witness the connection failure.
TCP connections seam unaffected.
I only tested NAT network.

I reproduced this with [http://www.sopcast.com Sopcast] which is a P2P application.
- Install the latest version (4.2.0) in a Windows VM;
- Visit [http:///www.cooltvi.com cooltvi.com] in Internet Explorer and select a channel;
- Allow the ActiveX to run - this would start the live broadcast which is P2P based. 
Sopcast requires Direct3D9 for video to render. But this is not required to reproduce this issue, it can very well be reproduced with black screen.

I could reproduce with Windows xp/posready 2009, 7, 8.1 and 10 guests.
I tested with AMD PCNET Fast III, Intel PRO 1000 T-Server and MT Desktop, Paravirtualized Network.

I'll post logs if necessary. 
  
 
 
",pal1000
15303,NAT host adapter responds to traffic when it shouldn't,,other,2016-04-11T23:34:29Z,2017-07-19T11:23:01Z,2017-07-19T11:23:01Z,"When using a NAT network, the host adapter will generate TCP RST packets in response to packets that are not destined for that interface. For example, here we have the following network setup:
{{{
52:54:00:12:35:02 10.0.2.2   VirtualBox router
08:00:27:7c:00:6c 10.0.2.15  VM
}}}
And the VM sends this packet:
{{{
TCP SYN
Src: Eth 08:00:27:7c:00:6c / IP 10.0.2.15  / TCP 15717
Dst: Eth 08:00:27:7c:00:6d / IP 10.0.2.100 / TCP 80
}}}
Then, the VM will receive this spurious packet:
{{{
TCP RST,ACK
Src: Eth 52:54:00:12:35:02 / IP 10.0.2.100 / TCP 80
Dst: Eth 08:00:27:7c:00:6c / IP 10.0.2.15  / TCP 15717
}}}
Note the source MAC. This is the host adapter's MAC. The expected result is that no packet will be sent in response to the original packet above, since the target host does not exist on the network and any other host receiving the packet should disregard it since the destination MAC does not match their MAC.

I have attached a pcap of the problem that was generated like this (nping is part of nmap):
{{{
arping -I enp0s3 -c 1 10.0.2.2
nping --tcp --dest-mac 08:00:27:7c:00:6d 10.0.2.100
}}}
Tested with VirtualBox 4.3.36, 5.0.12 and 5.0.16 using Debian, Ubuntu and FreeBSD.",Mike446
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
16883,Virtualbox 5.1.22 crashes ethernet card on Ubuntu 16.04 64bit,VirtualBox 5.1.22,Linux,2017-07-07T13:53:10Z,2017-07-26T13:13:51Z,2017-07-26T13:13:51Z,"I have a stock install of Ubuntu 16.04 64bit (Unity desktop) on my laptop.
As an addition there is virtualbox 5.1.22 installed from official Oracle repository and vagrant 1.9.5.

Whenever I start any virtual machine ethernet card just crashes.

Steps to reproduce:

mkdir -pv ~/foo
cd ~/foo
vagrant init bento/ubuntu-16.04
vagrant up

",kiklop74
16964,Repeatable error copying network file into virtual box,VirtualBox 5.1.26,Windows,2017-07-31T15:31:13Z,2017-07-31T15:58:31Z,2017-07-31T15:58:31Z,"Never had a problem with Virtual Box before. Using Virtual box on a win10 pro computer running an XP Pro virtual O/S. With the latest 5.1.26 I now am unable to copy large files from a network share into the VHD. I am able to copy the files from the shared folder with the Win10 pro box. Attached is the error message.
",Affiance
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
17118,virtualbox nataliasmode proxyonly breaks local network connectivity on windows 10,VirtualBox 5.1.28,Windows,2017-09-28T18:09:31Z,2017-10-02T14:42:29Z,2017-10-02T14:42:29Z,"Hi,

I have enabled proxyonly for the nat and now for the entire local network i am unable to access the guest machine in any of the protocols. thoouh it is accessible from the internet.

Thanks,
Vipin",Vipin Jain
17292,VirtualBox-5.2.0-118431-Win.exe post install causing NetBT errors in Event Log,VirtualBox 5.2.0,Windows,2017-11-18T19:19:45Z,2017-11-19T21:11:16Z,2017-11-19T21:11:16Z,"After i installed VirtualBox-5.2.0-118431-Win.exe along with the Guest Additions on a 64 bit Windows 7 machine i continually get the following errors every few seconds in the Event Logs.  I downgraded back to 5.1.30 and the errors stopped.  So, 5.2.0 has some bugs with the NIC.  I am using NAT for Host Network settings and disabled all other NIC cards.  The only active NIC is the Wireless NIC: Intel(R) Dual Band Wireless-AC 7260

Here is the error with attachment:

Level	Date and Time	Source	Event ID	Task Category
Error	11/18/2017 10:37:24 AM	NetBT	4321	None	""The name """"WORKGROUP      :1d"""" could not be registered on the interface with IP address 10.0.2.15. The computer with the IP address 10.0.2.2 did not allow the name to be claimed by this computer.""
",kingpoop
12600,Allow dns proxy in the new NAT Network mode,VirtualBox 4.3.6,all,2014-01-11T16:34:03Z,2018-01-16T13:37:54Z,2018-01-16T13:37:54Z,"I would like to be able to activate DNS proxy in the new NAT Network mode as it is possible in NAT mode (with the command VBoxManage modifyvm ""VM name"" --natdnsproxy1 on).

As it is, if I set my VM with the new NAT Network mode and run the command (VBoxManage modifyvm ""VM name"" --natdnsproxy1 on), this change nothing and continue to give the host DNS server to the guess.

Allowing this setting would be awesome as it would completely shield the VM from host change while allowing VM to talk to each other.",djf_jeff
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
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
17405,Bridged Networking Malfunctioning,VirtualBox 5.2.4,Linux,2017-12-28T01:59:10Z,2018-01-28T17:24:12Z,2018-01-28T17:24:12Z,"'''Host OS:''' Debian 9.3 (Linux)
'''Hypervisor:''' Virtualbox 5.2.4 
'''Guest OS:''' Security Onion (Elastic) Beta 3, Kali 2017.3, and I feel confident in assuming all OS's would have the same issue and I can test others if needed.

'''Situation:''' This week I upgraded my home lab from older versions of the above software, all previously worked on my hardware without issue, but Bridge Mode Networking is now failing to connect to SOME online resource and has dropped packets when it does connect. However NAT Mode Networking allows access to all online resources without issue.

'''Guest Configuration:''' My SecurityOnion Guest VM has a Bridged Adapter connection on Network Adapter 1, giving it internal vm network and external network access / Network Adapter 2 is listening in promiscuous mode on my switch's Mirrored Port.

Upon installing the guest OS (SecOnion) I began having issues pulling updates from the ubuntu.com software repositories. This was odd because on my host machine Speedtest.net was saying I had a 60+mbps connection to my ISP and furthermore my host machine was able to access ubuntu.com and pull down the same repositories without issue, this is what led me to verifying that I can use NAT but not Bridged Mode. NAT does allow me to access all resources (and update the systme), but I need to use Bridge Mode for my lab.

What's REALLY odd is that even with Bridge mode in its limited capacity, it IS able to pull down Google.com, Wikipedia.com, even Reddit.com with little issue (It does seem like it doesn't fully resolve any of the webpages though -spinning tabs and whatnot). But it completely fails to access Ubuntu.com, Fedora.com, Amazon.com... It's just VERY odd behavior... and it only happens in the VM when using Bridged Mode.

This behavior is repeatable (unable to access ubuntu.com and others) and happens every time I've tried to build a VM on this newer software.

Please let me know if there is any additional information I can provide.

-J

",Id1010terror
17525,Conflict between VESA VBE 2.0 graphic adapter and NAT network on WINDOWS ME,VirtualBox 5.2.6,Windows,2018-02-05T03:55:19Z,2018-02-05T03:55:19Z,2018-02-05T03:55:19Z,"When you install VESA VBE 2.0 Oracle VM VirtualBox VBE Adapter to have 32 bits true color on WINDOWS ME MILLENIUM EDITION with a program called SciTech Display Doctor (this also works with win 98) you can't connect with the internet cause it seems that there's a conflict between the NAT network adapter and VESA VBE 2.0 cause I uninstalled SciTech Display Doctor and went back to standard 16 colors graphic adapter and I could access internet again. This doesnt happen with Win 98 I can install it and internet works, it's just with Millenium edition",tonypark77
15844,vboxmanage option to enable advertising default route for ipv6,VirtualBox 5.1.4,other,2016-08-22T09:44:26Z,2018-02-12T17:31:41Z,2018-02-12T17:31:41Z,"At the moment this can be configured only via gui, the ticket is a request to make it possible to configure advertising of the default route in NAT network config via cli (vboxmanage)",mwasilewski
17630,wireshark can capture only one way packet,VirtualBox 5.2.8,Windows,2018-03-20T11:30:15Z,2018-03-21T13:24:45Z,2018-03-21T13:24:45Z,"hi
I have windows 10 computer. 
I installed virtual box 5.2.8 and vmware workstation 14. 
I have created ubuntu vm on both virtual box and workstation and bridged network adapters to 
physical interface.  
I have installed wireshark to my computer. 
when I tried to get IP from DHCP server of DSL modem, virtualbox ubuntu get IP with same IP of the host computer. why? should it get different IP from host computer? isn't it?
I have set up static IP to ubuntu machines. I can send packets between host computer, virtual box ubuntu, vmware ubuntu and DSL modem.
when I tried to capture packets with wireshark from physical interface, I can capture both direction between host and vmware but I cannot capture virtual box packets both direction.
I can see only virtual box ubuntu outbound traffic to other machines, I cannot see inbound traffic from other machines. during this period, all traffic goes succesfully. 
why I couldn't see inbound traffic to virtual box machines. 
     ",sesci
16419,"Transmit pauses still happen, not on Linux guests but on Windows host",VirtualBox 5.1.12,Windows,2017-01-24T04:48:19Z,2018-03-22T02:52:05Z,2018-03-22T02:52:05Z,"Despite claim that bug #16221 has been fixed, that fix was at best partial. True, the send side pauses happen far less often than in version 5.1.10, but they still happen. They happen on Windows 10 host and on an interface that has no guests bound to it. I'm going to attach log from a guest, because it may have important information about the host, but this issue really applies to the host and not a guest.
",Rafcio
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
15159,Need bzimage feature in iPXE build for network adapter boot ROM,VirtualBox 5.0.14,Mac OS X,2016-02-18T16:17:05Z,2018-04-08T08:17:51Z,2018-04-08T08:17:51Z,"see ticket #13628 for background. That ticket can be closed.

I cannot boot Linux (specifically CoreOS Linux) over PXE because the bzimage feature is needed to support the CoreOS cpio.gz file.

Please enable the bzimage feature in your iPXE build. Thanks.

here's my iPXE script if it matters:

{{{
kernel /assets/coreos/current/coreos_production_pxe.vmlinuz coreos.autologin coreos.config.url=http://10.3.0.154:8080/ignition?uuid=dontmatch coreos.first_boot=1
initrd /assets/coreos/current/coreos_production_pxe_image.cpio.gz
boot
}}}",MyDogHasFleas
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
17815,Failed to save settings - Empty or null bridged interface name is not valid.,VirtualBox 5.2.12,Windows,2018-06-12T09:19:14Z,2018-06-12T13:15:56Z,2018-06-12T13:15:56Z,"After I disable the bridged network (because is no adapter for some reason, so can't use it) and try to save settings, I get the following error:

Failed to save settings

Empty or null bridged interface name is not valid.


Result Code: 
E_FAIL (0x80004005)
Component: 
NetworkAdapterWrap
Interface: 
INetworkAdapter {e925c2aa-4fe4-aaf6-91c5-e9b8ea4151ee}

",szx
17819,"Support for specifying bridged interface name by guid, not only name",VirtualBox 5.2.12,other,2018-06-13T19:25:07Z,2018-06-13T20:56:05Z,2018-06-13T20:56:05Z,"Some network interface drivers on Windows has ability to display interface options and description in various languages based on current user set locales. This could lead to situations where VM template created for such shared system could not be started when target user uses different locale (""Network interface named XXX could not be found"") as the interface description, used by VirtualBox for bridged network, is different - altough the real interface stays the same.
As the interface guid (using eg. vboxmanage list bridgedifs) stays the same, it would be benefitial to use this instead of interface description in VM configuration.",M@…
11031,'Bridged Networking' on host vlan interfaces does not work,VirtualBox 4.2.0,Linux,2012-10-05T22:17:44Z,2018-07-09T14:30:18Z,2018-07-09T14:30:18Z,"I have searched the forums, and looked on the internet... and this seems to be a regression in the 4.2.0 release.  Downgrading back to 4.1.22 on the same kernel resolves the issue.

I am on gentoo 64-bit, running gentoo-sources-3.6.0.  Same results on 3.5.4

I have a vm-host with several 1q vlan interfaces on it.  I then bind my VM's to a particular interface using the 'Bridge Adapter'.  The VM's are vlan-agnostic.

The symptom I have on VB 4.2.0 is that none of my VM's have network access.  As soon as I switch to NAT on the VM's everything works fine.  Downgrading to 4.1.22 on the same kernel restores network access for the 'Bridge Adapter'.

{{{
daffy TAZ6 # cat /proc/net/vlan/config
VLAN Dev name    | VLAN ID
Name-Type: VLAN_NAME_TYPE_RAW_PLUS_VID_NO_PAD
eth0.10        | 10  | eth0
eth0.11        | 11  | eth0
eth0.12        | 12  | eth0
eth0.13        | 13  | eth0
eth0.14        | 14  | eth0
eth0.20        | 20  | eth0
eth0.25        | 25  | eth0
}}}

My VM-HOST network layout:
{{{
[ROUTER]====1Q-TRUNK===[VM HOST]
                              eth0.10--bridged--VM1, VM2, VM3....
                              eth0.11--bridged--VM6, VM7, VM8
                              eth0.12--bridged--VM4
                              eth0.13
                              eth0.14--bridged--VM5
                              eth0.20
                              eth0.25
}}}

The ROUTER and VM-HOST have the VM's MAC address in their arp tables.  The VM itself only has the VM-HOST's MAC address - but not the ROUTER's.  The VM can communicate with the VM-HOST but not anything else on the same L2 vlan.  All other devices on the same L2 vlan have VM's MAC address (after a ping, say) but the VM never has any of the other hosts in it's arp table.  Seems like packets destined to the VM never make it past the VM-HOST.  I don't see any odd kernel events.

This is the forum post I started prior to this bug - https://forums.virtualbox.org/viewtopic.php?f=7&t=51886

I can attach all the details here if need be.",nocternal
17879,Slow traffic on Bridged network interface when using anything but virtio-net,VirtualBox 5.2.16,Linux,2018-07-20T18:42:15Z,2018-07-20T18:48:38Z,2018-07-20T18:48:38Z,"Hi,

I'm noticing my network interfaces on my VM is very slow 300-400KB/s when using any of these network intefaces:

PCnet-PCI II (Am79C970A)
PCnet-FAST III (Am79C973)
Intel PRO/1000 MT Deesktop (82540EM)
Intel PRO/1000 T Server (82543GC)
Intel PRO/1000 MT Server (82545EM) - couldn't bring network up

When I used:

Paravirtualized Network (virtio-net)

I saw the normal speeds ie 3-4MB/s which is what I should be getting.

The virtual machine is a Debian 9 (Stretch)

Linux virtualmachine 4.9.0-7-amd64 #1 SMP Debian 4.9.110-1 (2018-07-05) x86_64 GNU/Linux


 ii  virtualbox-guest-dkms             5.2.10-dfsg-6~bpo9+1           all          x86 virtualization solution - guest addition module source for dkms
ii  virtualbox-guest-utils            5.2.10-dfsg-6~bpo9+1           amd64        x86 virtualization solution - non-X11 guest utilities
ii  virtualbox-guest-x11              5.2.10-dfsg-6~bpo9+1           amd64        x86 virtualization solution - X11 guest utilities

The host is Archlinux (latest updates 2018-07-20) ie:

Linux host 4.17.6-1-ARCH #1 SMP PREEMPT Wed Jul 11 19:14:29 UTC 2018 x86_64 GNU/Linux

The virtual machine currently has:

Base Memory: 2048MB
Chipset:     PIIX3
Enable I/O APIC = yes
Proceessor(s) = 4
Execution Cap = 100%
PAE/NX = false
Paravirtulization Interface: Default
VT-x/AMD-V = yes
Nested Paging = yes
Video Memory 128MB

Network:

Bridged Adaptor, on VLAN 2. (VLAN is set inside of the virtual machine).
Has dual stack IPv4 & IPv6 ie NAT IPv6 addressss and IPv6 GLA address.

The version of VirtualBox that ArchLinux has at the moment is 5.2.16 r123745",Tyler A
17881,Network in Bridged mode - Guest can't ping host,VirtualBox 5.2.16,Windows,2018-07-21T21:58:53Z,2018-07-28T20:45:37Z,2018-07-28T20:45:37Z,"- Network configuration: 1 Interface using the Bridged Mode on the Ethernet interface.
- The Guest has access to the internet.
- The host can connect to the guest (ping, ssh, ...)
- The Guest can find the host MAC address and fills the ARP table.
- The Guest can't ping the host. (no answer for the ping).

",zeralight
17883,Bridge adaptor removed when updating to 5.2.16,VirtualBox 5.2.16,Windows,2018-07-22T16:45:54Z,2018-07-28T20:57:56Z,2018-07-28T20:57:56Z,"Hello,

When updating from 5.2.14 on a Windows 10 host, my VM configured with network using a Bridge Adaptor were not able to boot. By looking at the settings, the dropdown list when selecting the Bridged Adapter is empty. If I'm not mistaken, there is a Network adapter that should be showing in the Windows control panel, but it doesn't. Is it like the update deleted the adapter (as design I guess since there is a warning for that in the installer), but didn't recreate it.

I was able to resolve this by doing a complete uninstall and install, the bridged adapter was shown in the list. But I feel the update shouldn't break that.

PS: I selected Linux as Guest type, as it's my only guest, but I'm sure it applies to all guest.",sharky98
17891,Cannot Create Host-Only Network on Windows 10,VirtualBox 5.2.16,other,2018-07-24T20:17:10Z,2018-07-29T07:56:33Z,2018-07-29T07:56:33Z,"VirtualBox 5.2.16
Microsoft 10 Windows Professional
Version	10.0.17134 Build 17134

Try to add host only network via GUI or command line results in failure:
{{{
  Querying NetCfgInstanceId failed (0x00000002).
  Result Code: 
  E_FAIL (0x80004005)
  Component: HostNetworkInterfaceWrap
  Interface: IHostNetworkInterface {455f8c45-44a0-a470-ba20-27890b96dba9}
}}}

Probably because of failed install; setupapi.dev.log has 
{{{
       [Device Install (UpdateDriverForPlugAndPlayDevices) - sun_VBoxNetAdp]
       Section start 2018/07/24 14:30:48.164
       cmd: C:\Windows\System32\MsiExec.exe -Embedding BA4E62E93D721D463D6D0D2C75E94A47 E Global\MSI0000
       ndv: INF path: C:\Program Files\Oracle\VirtualBox\drivers\network\netadp6\VBoxNetAdp6.inf
       ndv: Install flags: 0x00000001
  !    ndv: Unable to find any matching devices.
       Section end 2018/07/24 14:30:48.164
       [Exit status: FAILURE(0xe000020b)]
}}}

I've danced random dances for hours to about a dozen different tunes called out by various forum posters on the Interwebs; including uninstalling, reinstalling, searching for infcache.1 in vain, deleting *.pnf files, standing on one foot, spinning around, I'm a little teapot, etc.  

Please: 

  -If anyone has another ""off the top of my head did you try this"" solution, note that very similar errors to this one keep popping up going all the way back to 2011.  So whatever you were going to say, I've probably seen it already.  

  -Maybe someone at VirtualBox could duplicate the issue on their own machine, diagnose and fix it!  As I've noted, confirmed by an elementary Google search, this kind of error has an impressively long pedigree. Sometimes errors, especially if they recur for as long as this one has, are REAL and are not due to accidental circumstances fixable by Dr. Reboot and the Installers.  

  -If there is any other information I can provide that would help someone in a position to fix the issue DUPLICATE the issue, please let me know.  I am happy to help contribute to a solution by helping to frame it and gather information.  I am done trying to fix the problem through thermodynamics.  ",ggraham412
16084,ssl connection incorrectly reset when using NAT,VirtualBox 5.0.28,Mac OS X,2016-10-20T06:19:10Z,2018-08-08T16:17:15Z,2018-08-08T16:17:15Z,"After upgrading VirtualBox from version 5.0.26 to 5.0.28 on OS X 10.11.6, I noticed that ssl connections created in python with urllib2.urlopen are incorrectly reset on a Debian 8 guest with a single network interface in NAT mode. I attached a minimal python script that almost always fails with the following traceback:
{{{
gzip: stdin: unexpected end of file
tar: Unexpected EOF in archive
tar: Error is not recoverable: exiting now
Failed
Traceback (most recent call last):
  File ""./test.py"", line 12, in <module>
    shutil.copyfileobj(xact, pipe)
  File ""/usr/lib/python2.7/shutil.py"", line 49, in copyfileobj
    buf = fsrc.read(length)
  File ""/usr/lib/python2.7/socket.py"", line 380, in read
    data = self._sock.recv(left)
  File ""/usr/lib/python2.7/httplib.py"", line 602, in read
    s = self.fp.read(amt)
  File ""/usr/lib/python2.7/socket.py"", line 380, in read
    data = self._sock.recv(left)
  File ""/usr/lib/python2.7/ssl.py"", line 714, in recv
    return self.read(buflen)
  File ""/usr/lib/python2.7/ssl.py"", line 608, in read
    v = self._sslobj.read(len or 1024)
socket.error: [Errno 104] Connection reset by peer
}}}
I also attached the tcpdump output on both the host and the guest. The issue seems to only occur when the network traffic goes through the host thunderbolt ethernet adapter. If I switch to Wi-Fi, the issue does not occur. Moreover, I am unable to reproduce the problem with curl or wget.",exg
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
11919,"vboxmanager hostonlyif create --name """"",VirtualBox 4.2.14,all,2013-07-01T21:06:34Z,2018-09-17T13:55:23Z,2018-09-17T13:55:23Z,"To enable the naming of 'hostonlyif' the create command needs to have a --name option such that (especially) on Windows host systems the name doesn't default to ""VirtualBox Host-Only Ethernet Adapter"", but instead can be set to something more useful.",Sauraus
18020,"first packet for ping for static IP is always ""Destination host unreachable"" when you re-start your system",VirtualBox 5.2.18,Windows,2018-09-27T20:19:34Z,2018-10-01T23:16:53Z,2018-10-01T23:16:53Z,"first packet for ping for static IP is always ""Destination host unreachable"" when you re-start your windows 10 machine

Scenario to reproduce the issue.

1. reboot the laptop/system
2. try to ping any static IP 192.168..
3. you will see ""destination host unreachable"" for the 1st packet
4. result:""destination host unreachable"" for first ICMP packet 

Manual solution:
1. reboot the machine
2. go to control panel/network and sharing center
3. then go to change adapter settings
4. disable ""virtualBox Host-Only Network""
5. enable  ""virtualBox Host-Only Network""
6. Now ping any static IP
7. results: No error. Works great


",raza
18068,NAT process infinite loop call `poll` function,VirtualBox 5.2.20,Linux,2018-10-22T07:42:56Z,2018-10-22T07:42:56Z,2018-10-22T07:42:56Z,"Host machine: Fedora 28
Guest machine: Windows 10

My guest system is Windows 10 and using NAT network, and Windows 10 system suddenly unable to access the Internet at some point, but my host machine can access the network normally. I using Wireshark capturing some ARP data flow in Windows 10:

{{{
1   0.000000 PcsCompu_7a:1a:df → RealtekU_12:35:02 ARP 42 Who has 10.0.2.2? Tell 10.0.2.15
    2   0.207297 PcsCompu_7a:1a:df → Broadcast    ARP 42 Who has 10.0.2.2? Tell 10.0.2.15
    3   3.718693 PcsCompu_7a:1a:df → Broadcast    ARP 42 Who has 10.0.2.2? Tell 10.0.2.15
    4   4.500012 PcsCompu_7a:1a:df → Broadcast    ARP 42 Who has 10.0.2.2? Tell 10.0.2.15
    5   5.500048 PcsCompu_7a:1a:df → Broadcast    ARP 42 Who has 10.0.2.2? Tell 10.0.2.15
    6   6.719889 PcsCompu_7a:1a:df → Broadcast    ARP 42 Who has 10.0.2.2? Tell 10.0.2.15
    7  10.721331 PcsCompu_7a:1a:df → Broadcast    ARP 42 Who has 10.0.2.2? Tell 10.0.2.15
    8  11.499537 PcsCompu_7a:1a:df → Broadcast    ARP 42 Who has 10.0.2.2? Tell 10.0.2.15
    9  12.500007 PcsCompu_7a:1a:df → Broadcast    ARP 42 Who has 10.0.2.2? Tell 10.0.2.15
   10  15.499582 PcsCompu_7a:1a:df → Broadcast    ARP 42 Who has 10.0.2.2? Tell 10.0.2.15
   11  16.721794 PcsCompu_7a:1a:df → Broadcast    ARP 42 Who has 10.0.2.2? Tell 10.0.2.15
   12  17.500389 PcsCompu_7a:1a:df → Broadcast    ARP 42 Who has 10.0.2.2? Tell 10.0.2.15
   13  18.500008 PcsCompu_7a:1a:df → Broadcast    ARP 42 Who has 10.0.2.2? Tell 10.0.2.15
   14  21.499517 PcsCompu_7a:1a:df → Broadcast    ARP 42 Who has 10.0.2.2? Tell 10.0.2.15
   15  22.725696 PcsCompu_7a:1a:df → Broadcast    ARP 42 Who has 10.0.2.2? Tell 10.0.2.15
   16  23.499997 PcsCompu_7a:1a:df → Broadcast    ARP 42 Who has 10.0.2.2? Tell 10.0.2.15
   17  24.499501 PcsCompu_7a:1a:df → Broadcast    ARP 42 Who has 10.0.2.2? Tell 10.0.2.15
   18  27.499508 PcsCompu_7a:1a:df → Broadcast    ARP 42 Who has 10.0.2.2? Tell 10.0.2.15
   19  27.982749 PcsCompu_7a:1a:df → Broadcast    ARP 42 Who has 10.0.2.2? Tell 10.0.2.15
   20  28.500004 PcsCompu_7a:1a:df → Broadcast    ARP 42 Who has 10.0.2.2? Tell 10.0.2.15
   21  29.500001 PcsCompu_7a:1a:df → Broadcast    ARP 42 Who has 10.0.2.2? Tell 10.0.2.15
   22  34.985277 PcsCompu_7a:1a:df → Broadcast    ARP 42 Who has 10.0.2.2? Tell 10.0.2.15
   23  35.500502 PcsCompu_7a:1a:df → Broadcast    ARP 42 Who has 10.0.2.2? Tell 10.0.2.15
   24  36.500023 PcsCompu_7a:1a:df → Broadcast    ARP 42 Who has 10.0.2.2? Tell 10.0.2.15
   25  38.248133 PcsCompu_7a:1a:df → Broadcast    ARP 42 Who has 10.0.2.2? Tell 10.0.2.15
   26  42.249642 PcsCompu_7a:1a:df → Broadcast    ARP 42 Who has 10.0.2.2? Tell 10.0.2.15
   27  42.999528 PcsCompu_7a:1a:df → Broadcast    ARP 42 Who has 10.0.2.2? Tell 10.0.2.15
   28  43.999519 PcsCompu_7a:1a:df → Broadcast    ARP 42 Who has 10.0.2.2? Tell 10.0.2.15
   29  47.235338 PcsCompu_7a:1a:df → Broadcast    ARP 42 Who has 10.0.2.2? Tell 10.0.2.15
   30  48.000015 PcsCompu_7a:1a:df → Broadcast    ARP 42 Who has 10.0.2.2? Tell 10.0.2.15
   31  49.000018 PcsCompu_7a:1a:df → Broadcast    ARP 42 Who has 10.0.2.2? Tell 10.0.2.15
}}}

IP 10.0.2.2 is NAT's gateway address, as you see, my Windows system send some ARP broadcast packet to find 10.0.2.2's MAC address, but not recive any response packet.

At the same time, in my host machine, the `NAT` process occupies a lot of CPU resources. I using `strace` command tracing `NAT` process:

{{{
poll([{fd=46, events=POLLPRI|POLLRDNORM|POLLRDBAND}, {fd=45, events=POLLIN}, {fd=98, events=POLLIN|POLLPRI}, {fd=76, events=POLLIN|POLLPRI}, {fd=229, events=POLLIN|POLLPRI}, {fd=93, events=POLLIN|POLLPRI}, {fd=91, events=POLLIN}, {fd=89, events=POLLIN}, {fd=81, events=POLLIN}, {fd=96, events=POLLIN}, {fd=102, events=POLLIN}, {fd=97, events=POLLIN}, {fd=88, events=POLLIN}, {fd=70, events=POLLIN}, {fd=68, events=POLLIN}], 15, 500) = 1 ([{fd=91, revents=POLLIN}])
poll([{fd=46, events=POLLPRI|POLLRDNORM|POLLRDBAND}, {fd=45, events=POLLIN}, {fd=98, events=POLLIN|POLLPRI}, {fd=76, events=POLLIN|POLLPRI}, {fd=229, events=POLLIN|POLLPRI}, {fd=93, events=POLLIN|POLLPRI}, {fd=91, events=POLLIN}, {fd=89, events=POLLIN}, {fd=81, events=POLLIN}, {fd=96, events=POLLIN}, {fd=102, events=POLLIN}, {fd=97, events=POLLIN}, {fd=88, events=POLLIN}, {fd=70, events=POLLIN}, {fd=68, events=POLLIN}], 15, 500) = 1 ([{fd=91, revents=POLLIN}])
poll([{fd=46, events=POLLPRI|POLLRDNORM|POLLRDBAND}, {fd=45, events=POLLIN}, {fd=98, events=POLLIN|POLLPRI}, {fd=76, events=POLLIN|POLLPRI}, {fd=229, events=POLLIN|POLLPRI}, {fd=93, events=POLLIN|POLLPRI}, {fd=91, events=POLLIN}, {fd=89, events=POLLIN}, {fd=81, events=POLLIN}, {fd=96, events=POLLIN}, {fd=102, events=POLLIN}, {fd=97, events=POLLIN}, {fd=88, events=POLLIN}, {fd=70, events=POLLIN}, {fd=68, events=POLLIN}], 15, 500) = 1 ([{fd=91, revents=POLLIN}])
poll([{fd=46, events=POLLPRI|POLLRDNORM|POLLRDBAND}, {fd=45, events=POLLIN}, {fd=98, events=POLLIN|POLLPRI}, {fd=76, events=POLLIN|POLLPRI}, {fd=229, events=POLLIN|POLLPRI}, {fd=93, events=POLLIN|POLLPRI}, {fd=91, events=POLLIN}, {fd=89, events=POLLIN}, {fd=81, events=POLLIN}, {fd=96, events=POLLIN}, {fd=102, events=POLLIN}, {fd=97, events=POLLIN}, {fd=88, events=POLLIN}, {fd=70, events=POLLIN}, {fd=68, events=POLLIN}], 15, 500) = 1 ([{fd=91, revents=POLLIN}])
poll([{fd=46, events=POLLPRI|POLLRDNORM|POLLRDBAND}, {fd=45, events=POLLIN}, {fd=98, events=POLLIN|POLLPRI}, {fd=76, events=POLLIN|POLLPRI}, {fd=229, events=POLLIN|POLLPRI}, {fd=93, events=POLLIN|POLLPRI}, {fd=91, events=POLLIN}, {fd=89, events=POLLIN}, {fd=81, events=POLLIN}, {fd=96, events=POLLIN}, {fd=102, events=POLLIN}, {fd=97, events=POLLIN}, {fd=88, events=POLLIN}, {fd=70, events=POLLIN}, {fd=68, events=POLLIN}], 15, 500) = 1 ([{fd=91, revents=POLLIN}])
poll([{fd=46, events=POLLPRI|POLLRDNORM|POLLRDBAND}, {fd=45, events=POLLIN}, {fd=98, events=POLLIN|POLLPRI}, {fd=76, events=POLLIN|POLLPRI}, {fd=229, events=POLLIN|POLLPRI}, {fd=93, events=POLLIN|POLLPRI}, {fd=91, events=POLLIN}, {fd=89, events=POLLIN}, {fd=81, events=POLLIN}, {fd=96, events=POLLIN}, {fd=102, events=POLLIN}, {fd=97, events=POLLIN}, {fd=88, events=POLLIN}, {fd=70, events=POLLIN}, {fd=68, events=POLLIN}], 15, 500) = 1 ([{fd=91, revents=POLLIN}])
poll([{fd=46, events=POLLPRI|POLLRDNORM|POLLRDBAND}, {fd=45, events=POLLIN}, {fd=98, events=POLLIN|POLLPRI}, {fd=76, events=POLLIN|POLLPRI}, {fd=229, events=POLLIN|POLLPRI}, {fd=93, events=POLLIN|POLLPRI}, {fd=91, events=POLLIN}, {fd=89, events=POLLIN}, {fd=81, events=POLLIN}, {fd=96, events=POLLIN}, {fd=102, events=POLLIN}, {fd=97, events=POLLIN}, {fd=88, events=POLLIN}, {fd=70, events=POLLIN}, {fd=68, events=POLLIN}], 15, 500) = 1 ([{fd=91, revents=POLLIN}])
poll([{fd=46, events=POLLPRI|POLLRDNORM|POLLRDBAND}, {fd=45, events=POLLIN}, {fd=98, events=POLLIN|POLLPRI}, {fd=76, events=POLLIN|POLLPRI}, {fd=229, events=POLLIN|POLLPRI}, {fd=93, events=POLLIN|POLLPRI}, {fd=91, events=POLLIN}, {fd=89, events=POLLIN}, {fd=81, events=POLLIN}, {fd=96, events=POLLIN}, {fd=102, events=POLLIN}, {fd=97, events=POLLIN}, {fd=88, events=POLLIN}, {fd=70, events=POLLIN}, {fd=68, events=POLLIN}], 15, 500) = 1 ([{fd=91, revents=POLLIN}])
poll([{fd=46, events=POLLPRI|POLLRDNORM|POLLRDBAND}, {fd=45, events=POLLIN}, {fd=98, events=POLLIN|POLLPRI}, {fd=76, events=POLLIN|POLLPRI}, {fd=229, events=POLLIN|POLLPRI}, {fd=93, events=POLLIN|POLLPRI}, {fd=91, events=POLLIN}, {fd=89, events=POLLIN}, {fd=81, events=POLLIN}, {fd=96, events=POLLIN}, {fd=102, events=POLLIN}, {fd=97, events=POLLIN}, {fd=88, events=POLLIN}, {fd=70, events=POLLIN}, {fd=68, events=POLLIN}], 15, 500) = 1 ([{fd=91, revents=POLLIN}])
.......

}}}

as you see, NAT process infinite loop call `poll` function",lu4nx
18056,Linux VM fails to PXE boot on MacOS host,VirtualBox 5.2.20,other,2018-10-17T12:29:26Z,2018-10-26T00:02:00Z,2018-10-26T00:02:00Z,"Virtualbox (5.2.18) + extensions installed on a 2017 iMac with MacOS (OSX) 10.14 Mojave and it seems impossible to make the VM get an IP address from my DHCP server during PXE booting.

I tried all possible combinations for configuring the network adapter for the VM but still it fails to get the DHCP IP. I even checked the DHCP server logs and I am sure that the IP used by the VM never reached it.

The config I was expecting to be working:

    Bridged Adapter: en0 (this is the LAN of the iMac)
    Adapter Type: one of Intel ones (but tried all 6 possible alternatives)
    Promiscous Mode: deny
    MAC Address: a generated one
    Cable Connected: Checked.

I am not sure if this problem is specific to MacOS Mojave or the Ethernet board in iMac as I did not had the chance to test with other versions.

Initially posted on https://forums.virtualbox.org/viewtopic.php?f=8&t=89792",sorin
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
18100,Old DHCP leases interfere with changed server configuration,VirtualBox 5.2.20,Linux,2018-11-03T19:31:54Z,2018-11-03T19:35:58Z,2018-11-03T19:35:58Z,"Host: openSUSE Leap 15

virtualbox-host-kmp-default-5.2.20_k4.12.14_lp150.12.22-lp150.4.20.1.x86_64
virtualbox-host-source-5.2.20-lp150.4.20.1.noarch
virtualbox-5.2.20-lp150.4.20.1.x86_64
virtualbox-qt-5.2.20-lp150.4.20.1.x86_64

In short, the lease file for a NAT net must be deleted by hand. Otherwise the DHCP server (with a different IP) hands out the old leases (wrong IPs).",robert spitzenpfeil
4626,PPPoE fails over bridged HP8510w 4965AG WLAN card,VirtualBox 3.0.2,Windows,2009-07-26T10:28:40Z,2018-11-08T23:11:59Z,2018-11-08T23:11:59Z,"I have a problem where I have a host machine, an HP8510w laptop with an intel 4965AG WLAN card. I am running Vista 64 Ultimate (same problem with Win 7 64 RTM) with a guest machine running Windows XP Sp3. The most important aspects of this setup is that the guest machine is set to be bridged to my WLAN card (Intel 4965AG). I am using static IP's with a router.

After the Guest OS is installed, I have configured an IP address. I can ping the router from the Host OS and I can also ping the router from the Guest OS. All other aspects of networking seem to be working. (I do not use DHCP purely because of my network setup but I feel this is unimportant).

I have several PPPoE accounts and a router that is in bridge mode. When I try to initiate a PPPoE connection in the Guest OS (WinXP), PADI packets leave the guest machine, go through the bridged network, reach the router. The router then sends a PADO response which can be seen on the Host OS and is also passed on to the Guest OS.

Unfortunately, the Guest OS is ignoring these packets as the target MAC address does not seem to be for the Guest OS (Which is understandable, but surely the bridging driver/service installed on the Host OS NIC is supposed to correct this?)

This seems to be a problem with the bridging driver/service for VirtualBox. This may not be of any concern to you, but the problem also exists in VMware Workstation. This is not a problem for Microsoft Virtual Machine though.

I have discovered a slight workaround. If I set the MAC address of the virtual network card in the guest to the same MAC address of the Host OS WLAN card, the PADO packets are relayed and it now works. Unfortunately, this causes other problems with Linux Guest's trying to use the same workaround and I cannot use this solution permanently.

I have attached the Vbox.log, as well as two wireshark captures from both the host and the guest machine.",Kinnoken
18135,Guest network down with version 5.2 and e1000,VirtualBox 5.2.20,Linux,2018-11-17T15:07:25Z,2018-11-17T15:07:25Z,2018-11-17T15:07:25Z,"After an upgrade from 5.1.38-122592 to 5.2.20-125813 the guest network did not automatically come up. The network worked fine after bringing the interface down/up.
Another copy of the same VM running on different hardware with identical software did not have the problem.

Both VMs were using E1000 network adapters in bridged mode. Switching to either of the PCnet adapters fixed the issue on the ""not working"" system.

[Beware: User speculation] The not working system is slower and it looks like there was a recent change to the E1000 LinkUpDelay from 5000ms to 3000ms. I'm suspecting that the shortened delay may be related to the problem. I could not find a configuration setting for the LinkUpDelay.

Host systems: Debian 9 (stable) 64 bit (fully up to date)

Guest systems: Debian 9 32 bit (fully up to date)

About the VirtualBox version. I first noticed the issue on 5.2.20, but did not have a chance to gather logs until after upgrading to 5.2.22. Both versions have the issue.

Not working hardware:
{{{
  AMD Turion(tm) 64 Mobile Technology ML-34 (800 MHz single core)  
  Ethernet controller: Realtek Semiconductor Co., Ltd. RTL-8100/8101L/8139 PCI Fast Ethernet Adapter (rev 10)
	Subsystem: Hewlett-Packard Company RTL-8100/8101L/8139 PCI Fast Ethernet Adapter
	Flags: bus master, medium devsel, latency 128, IRQ 22, NUMA node 0
	I/O ports at a000 [size=256]
	Memory at c020a400 (32-bit, non-prefetchable) [size=256]
	Capabilities: [50] Power Management version 2
	Kernel driver in use: 8139too
	Kernel modules: 8139cp, 8139too
}}}
Working hardware:
{{{
  Intel(R) Core(TM)2 Duo CPU T7100 @ 1.80GHz (dual core, 800 MHz)  
  Ethernet controller: Broadcom Limited NetLink BCM5787M Gigabit Ethernet PCI Express (rev 02)
	Subsystem: Hewlett-Packard Company 6710b
	Physical Slot: 1
	Flags: bus master, fast devsel, latency 0, IRQ 30
	Memory at e4000000 (64-bit, non-prefetchable) [size=64K]
	Expansion ROM at <ignored> [disabled]
	Capabilities: [48] Power Management version 3
	Capabilities: [50] Vital Product Data
	Capabilities: [58] Vendor Specific Information: Len=78 <?>
	Capabilities: [e8] MSI: Enable+ Count=1/1 Maskable- 64bit+
	Capabilities: [d0] Express Endpoint, MSI 00
	Capabilities: [100] Advanced Error Reporting
	Capabilities: [13c] Virtual Channel
	Capabilities: [160] Device Serial Number 00-1c-c4-ff-fe-c9-02-6d
	Capabilities: [16c] Power Budgeting <?>
	Kernel driver in use: tg3
	Kernel modules: tg3
}}}",FixItDad
18029,NAT network UDP port forwarding not working,VirtualBox 5.2.18,Windows,2018-10-04T07:07:04Z,2018-11-23T11:25:11Z,2018-11-23T11:25:11Z,"I've created a machine with linux ubuntu with NAT network attached.
The machine connects properly and receives an address 10.0.2.7.
I've created a port forwarding from UDP 500 to 10.0.2.7 UDP 500.
It seems that packets sent to UDP 127.0.0.1:500 are not arriving to the machine. (checked with tcpdump -i enp0s3 udp 500 on the machine.
Doing the exact same with TCP works fine.
Packets are sent with ""Packet Sender"", and verified with rawcap on the host.",Asi Lev
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
18152,Windows 2012 R2 Build 9600 broken networking,VirtualBox 5.2.22,Mac OS X,2018-11-26T17:53:57Z,2018-11-28T12:44:54Z,2018-11-28T12:44:54Z,"Upgraded to VirtualBox Version 5.2.22 r126460 (Qt5.6.3) on macOS 10.12.6 and Windows 2012 R2 as a VM networking does not work. In fact, the 2012 VM does not even detect a network interface.

[[Image(https://user-images.githubusercontent.com/6723257/49027270-7020f880-f165-11e8-86bc-621db519a02c.png)]]	

[[Image(https://user-images.githubusercontent.com/6723257/49028433-00603d00-f168-11e8-9456-67cf6261b690.png)]]	",Bob Tanner
18178,NAT driver drops inbound retransmits that happen after FIN,VirtualBox 5.2.22,other,2018-12-12T03:11:43Z,2018-12-12T14:54:15Z,2018-12-12T14:54:15Z,"In TCP, it is possible and allowed (and actually, necessary) for the sending side to retransmit after sending the FIN but before receiving a FIN from the other side.  The sending side will send a final ""window"" of TCP segments, ending with a FIN packet.  If one of those is dropped, the receiving side should ACK the most recently received packet, then the sender will retransmit.  Only after all packets are received and acknowledged should the recipient ACK the sender's FIN segment and send back its own.

Instead, guests within virtualbox seem to immediately respond to the FIN with a FIN/ACK and tear down the connection.  This means that if a segment is dropped within the final window transmission, the download is silently truncated.  It's likely a rare bug, in that it only becomes high-probability with a combination of high latency, large window sizes, and nontrivial amounts of packet loss.  With almost all TCP schedule algorithms, even small amounts of packet loss result in a very small transmission window.  The new BBR, on the other hand, tries to probe the latency and bandwidth available rather than relying on packet loss for feedback, so it's far more likely to result in a large TCP window despite some packet loss.",Elliott
18184,arp fails when connecting to a wireless connection on host via bridged network,VirtualBox 5.2.22,Windows,2018-12-15T08:46:29Z,2018-12-18T13:51:03Z,2018-12-18T13:51:03Z,"Host: Windows 10 Pro
Guest: eCS 2.2 beta (drivers: all the latest and greatest)

From the guest, I am trying to connect to a wireless connection on the host. For sake of simplicity and performance I have set up ""bridged network"".

Sometimes but not always I have problems to access the net from the guest. When that happens, I see this (example) in the ARP table of the guest:

""arp -a"":

ARP table contents:
{{{
interface   hardware address   IP address       minutes since last use
lan 0       (incomplete)       www.xxx.yyy.zzz  0
}}}
Apparently, the ARP request does not pass through. If I reboot the guest a couple of times AND if I actually use the wireless connection on the host, then eventually, I will be able to access the wireless connection from the guest.
I have not observed this problem with a wired connection (on the host). This seems to always work ok.",lerdmann
18194,netplan bond not working (ubuntu 18.04),VirtualBox 5.2.22,all,2018-12-18T10:10:24Z,2018-12-27T17:17:21Z,2018-12-27T17:17:21Z,"Hey guys,

today I set up a network bond environment under Ubuntu 18.04 (4.15.0-42-generic). After running ""sudo netplan apply"" interface ""bond0"" with the given IP comes up. But it is not possible to tranfer any packets through this interface, neither in nor out.
This issue exists with the latest dev versions of !VirtualBox 5.2 and 6, too.

My netplan configuration:
{{{
network:
  version: 2
  renderer: networkd
  ethernets:
    eth0:
      dhcp4: no
      dhcp6: no
    eth1:
      dhcp4: no
      dhcp6: no
  bonds:
    bond0:
      dhcp4: no
      dhcp6: no
      interfaces: [eth0, eth1]
      addresses: [192.168.56.81/24]
      parameters:
        mode: active-backup
        mii-monitor-interval: 100
        primary: eth0
}}}",lemerp
18173,Bridged Adapter not working version 5.2.22,VirtualBox 5.2.22,Windows,2018-12-07T03:26:14Z,2019-01-18T02:44:59Z,2019-01-18T02:44:59Z,"Using Bridged Adapters with Windows 10 Host and Windows 10 Guest fails to work as expected. The host and the guest can not ping each other , neither can the guest ping anything outside of its own machine. 

This issue I have narrowed down to having a locally administered MAC address with in the Guest machine.  While the work around is to use the VirtualBox setting as the MAC address - this is not the preferred method for portability of the Disk Image File. I had narrowed it down by swapping the bound network interface lan and wifi to network 1 and network 2 and then reversing that - disabling the first network with in the guest (which had the locally administered address) - everything then worked - and I only realized it was the MAC address being locally administered within the guest - because I needed to set it for Network2 at which point everything failed to communicate again. 
I then administered the local mac in the Vbox Settings network page. I would prefer this to be with in the image itself in network properties. If I have several images with the same locally administered MAC , I would think the VBox Bridge would act as the router hop so that I could  have multiple of this image on the same network.



",Ken The Eskimo
18495,VirtualBox NAT alias option use-same-ports (--nataliasmode1=sameports) has no effect on Ubuntu 16.04 host OS,VirtualBox 6.0.4,Linux,2019-03-14T20:53:00Z,2019-03-14T20:53:00Z,2019-03-14T20:53:00Z,"== Steps to reproduce ==

    1. Create a VirtualBox VM as follows, accepting default values for anything not listed here:

        * Name: archlinux-2019.03.01-x86_64
        * Type: Linux
        * Version: Arch Linux (64-bit)

    2. Download archlinux-2019.03.01-x86_64.iso into the VM directory:

    {{{
cd 'VirtualBox VMs'/archlinux-2019.03.01-x86_64
curl -O http://mirrors.acm.wpi.edu/archlinux/iso/2019.03.01/archlinux-2019.03.01-x86_64.iso
    }}}

    3. Confirm the MD5 checksum. First, display the expected checksum:

    {{{
curl http://mirrors.acm.wpi.edu/archlinux/iso/2019.03.01/md5sums.txt
    }}}

    Verify on Linux:

    {{{
md5sum archlinux-2019.03.01-x86_64.iso
    }}}

    Verify on macOS:

    {{{
md5 archlinux-2019.03.01-x86_64.iso
    }}}

    4. Start the VM in VirtualBox, click '''Choose a virtual optical disk file''' (represented by a folder icon with an upward-pointing green arrow), and select the archlinux-2019.03.01-x86_64.iso file downloaded in Step 2.

    5. Boot the VM, selecting default options for everything.

    6. On the host (64-bit Ubuntu Xenial Xerus 16.04.6 LTS), find two unused privileged (port number less than 1024) ports; for example, the following command will return nothing if both ports 1022 and 1023 are free:

    {{{
netstat -Wa | grep -E '1022|1023'
    }}}

    7. On the guest (64-bit Arch Linux 2019.03.01), confirm that the first free port from Step 6 is also free on the guest:

    {{{
netstat -Wa | grep 1022
    }}}

    If this  command returns any output, repeat Steps 6 and 7 until you have found two free ports.

    8. On the host (64-bit Ubuntu Xenial Xerus 16.04.6 LTS), start listening on the second free port, the receiving port:

    {{{
sudo nc -l 1023
    }}}

    9. On the guest (64-bit Arch Linux 2019.03.01), open a connection to the receiving port on the host, originating the connection from the first free port, the sending port:

    {{{
nc -p 1022 ala-michaelk-lx1.corp.ad.wrs.com 1023
    }}}

    Replace `ala-michaelk-lx1.corp.ad.wrs.com` with the fully qualified domain name (FQDN) of the host, as returned by the `hostname -f` command.

    After running both `nc` commands, any text entered on the guest should appear on the host and vice versa.

    10. In another shell on host, look for connections to the receiving port:

    {{{
netstat -W | grep 1023
    }}}

    Initially observe that network address translation (NAT) has replaced the sending port (1022) with a random port (48946), as expected for `--nataliasmode1=default`:

    {{{
$ netstat -W | grep 1023
tcp        0      0 ala-michaelk-lx1.corp.ad.wrs.com:1023 ala-michaelk-lx1.corp.ad.wrs.com:48946 ESTABLISHED
tcp        0      0 ala-michaelk-lx1.corp.ad.wrs.com:48946 ala-michaelk-lx1.corp.ad.wrs.com:1023 ESTABLISHED
    }}}

    11. On the host (64-bit Ubuntu Xenial Xerus 16.04.6 LTS), close the connection by pressing Ctrl-D (EOF) in the shell running `nc`.

    12. Close the guest console window, select '''Save the machine state''', and click '''OK'''.

    13. On host, switch the VM to `--nataliasmode1=sameports`:

    {{{
VBoxManage modifyvm archlinux-2019.03.01-x86_64 --nataliasmode1=sameports
    }}}

    14. In VirtualBox, click '''Start''' to restore the VM.

    15. Repeat Steps 8–11.

== Expected ==

The port number for the sending port (1022) is preserved, as seen on host macOS Mojave Version 10.14.3:

{{{
inu:~ michael$ netstat -W | grep 1023
tcp4       0      0  inu.corp.ad.wrs.com.1023  inu.corp.ad.wrs.com.1022  ESTABLISHED
tcp4       0      0  inu.corp.ad.wrs.com.exp2  inu.corp.ad.wrs.com.1023  ESTABLISHED
}}}

== Observed ==

The port number for the sending port (1022) is replaced with a random port number, as seen on host 64-bit Ubuntu Xenial Xerus 16.04.6 LTS:

{{{
$ netstat -W | grep 1023
tcp        0      0 ala-michaelk-lx1.corp.ad.wrs.com:48972 ala-michaelk-lx1.corp.ad.wrs.com:1023 ESTABLISHED
tcp        0      0 ala-michaelk-lx1.corp.ad.wrs.com:1023 ala-michaelk-lx1.corp.ad.wrs.com:48972 ESTABLISHED
}}}
",interfrastic
18540,PPTP not connecting from Windows guest in 6.0.4,VirtualBox 6.0.4,Windows,2019-04-03T09:00:09Z,2019-04-09T14:35:06Z,2019-04-09T14:35:06Z,"Hi,

Running Virtualbox 6.0.4 on Windows 10 x64 host, guests cannot connect to PPTP VPN. Tried with both Windows 7 x64 and Windows 10 32bits guests.

Connection hangs at ""checking username and password"" and finally disconnects with ""Error 734: The PPP Link Control Protocol Was Terminated""

Downgrade to 6.0.2 solves the issue, guests can connect again to PPTP.

Using bridged networking :-)

I will be happy to provide any log or test you may need.

PKX.",pkx232c
18472,VirtualBox no longer working after latest set of Windows 10 security patches.,VirtualBox 6.0.4,Windows,2019-03-05T02:54:29Z,2019-04-14T21:24:06Z,2019-04-14T21:24:06Z,"  I already submitted a Windows 10 feedback on this, as I'm not sure if it's a Windows 10 bug or a VirtualBox issue.
  
  After last week's Windows 10 Pro security patches, I can no longer start a VirtualBox virtual machine. On version 5.26, it gives the error
    verr_intnet_flt_if_not_found
when using a Windows 7 machine with a bridged wifi and Ethernet network. On
VirtualBox version 6.04, it just hangs forever at the ""Starting virtual machine"" screen, and I have to kill the process to cancel it.

    Even before this set of patches, it had run fine on 5.22 and 5.26, but 
6.04 would always hang after getting almost all the way through the boot process, up to starting most of the commands in the startup folder. That would happen from Windows 10 to Windows 7 or 10 VMs, and from Linux Ubuntu 18 to Windows 10 VMs with a similar set of startups, but not from Mac OSX to Windows 10; that one ran fine.",baseballbob
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
6324,Bridging guest on mac os x host vlan cause reception of malformed packets on gest NIC,VirtualBox 3.1.4,Mac OS X,2010-03-04T16:04:59Z,2019-05-06T23:59:38Z,2019-05-06T23:59:38Z,"On Mac OS X 10.5.8 with a primary NIC named en0 and a virtual NIC named vlan3 accessing tagged traffic on en0

Guest is linux, eth0 is bridged to vlan3

Sniffing traffic with tcpdump on both host (vlan3) and guest (eth0) shows that some of the packets reaching guest contains additional 4 bytes after source/dest MAC address replicating the last 4 bytes of the source MAC.",Luca Ghedini
14271,"Start/Stop VM affect PPPoE link, with bridged networking.",VirtualBox 5.0.0,other,2015-07-13T20:41:18Z,2019-05-12T06:07:40Z,2019-05-12T06:07:40Z,"VBox 5.0.0 on Windows 7 host, Starting Windows XP guest with '''Bridged networking''', will hang PPPoE link of host.

It also hang PPPoE connection while Stopping VM.

If VM networking is NAT, then all well.

It didn't happened with version 4.3.28",NoNoNo
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
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
18701,virtual box and multiple ubuntu 16 vagrant images have intermittent hanging problems via ssh,VirtualBox 5.2.30,other,2019-06-10T06:02:44Z,2019-06-21T16:51:18Z,2019-06-21T16:51:18Z,"I frequently have an issue using the bento/ubuntu16.04 or ubuntu/xenial64 images for vagrant on mac os 10.13.6 where the ssh session will completely freeze and I cannot vagrant ssh back in.  these two images use virtual box.

since I'm able to reproduce the problem with multiple images, and I've also just reinstalled my whole os from scratch and am still getting the problem I suspect this may be a virtual box issue related to ssh.

I am using virtual box 5.2.30 which is the version required for these two images.",openfirehawk
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
4427,active FTP doesn't work with NAT,VirtualBox 3.0.0,Solaris,2009-07-07T23:40:24Z,2019-09-05T02:54:35Z,2019-09-05T02:54:35Z,"This is with a 64-bit OpenSolaris host (2009.06).  It happens with all tested guests (XP, Ubuntu, OpenSolaris, Solaris 10), both with NAT and bridged networking.  The problem did not exist prior to 3.0.0, and has been confirmed both with pre-existing guests and newly created guests.

When you open an FTP session from the guest to the OpenSolaris host, the host returns an error like this one from a NAT guest:

Jun 21 19:50:21 fnog ftpd[1902]: [ID 227848 daemon.warning] refused PORT 10.0.2.15,60783 from fnog [192.168.99.22]

192.168.99.22 is the host IP.

If you do the same with VB 2.2.4 on the same host, ftpd logs no errors and successfully connects the guest.  This has been tested on two different hosts.  Both tested installations of the host OS use an unmodified default ftp configuration.

With FTP servers on the Internet, VB guests connect, but are unable to list files or directories on the FTP server using either the 'ls' or 'dir' commands.  The same FTP servers interact normally with computers that are not VB guests.  One tested example would be ftp.sunfreeware.com.

Shared folders and SSH/SCP/SFTP exhibit no observed problems from guest to host, but are slower for large transfers and for network testing.

I will be attaching a log file soon.",bqbauer
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
18932,No DNS from DHCP on NAT connection,VirtualBox 6.0.12,Windows,2019-09-16T13:48:19Z,2019-09-17T00:05:17Z,2019-09-17T00:05:17Z,"On VirtualBox 6.0.12, with plain NAT configuration, the domain name resolution does not work anymore on Windows/Linux guests on Windows host.

I've checked quite everything on host and guests configuration and come up to the hypothesis that VirtualBox dhcp ""server"" does not send the DNS address, but it used to do on previous versions.

This is confirmed by DHCP not containing the DNS entry as shown by the following DHCP response:


{{{
$ sudo nmap --script broadcast-dhcp-discover

Starting Nmap 7.60 at 2019-09-12 08:08 CEST
Pre-scan script results:
| broadcast-dhcp-discover:
|   Response 1 of 1:
|     IP Offered: 10.0.2.16
|     DHCP Message Type: DHCPOFFER
|     Subnet Mask: 255.255.255.0
|     Router: 10.0.2.2
|     IP Address Lease Time: 1d00h00m00s
|_    Server Identifier: 10.0.2.2
WARNING: No targets were specified, so 0 hosts scanned.
Nmap done: 0 IP addresses (0 hosts up) scanned in 0.51 seconds
}}}
",Han Fastolfe
18973,BSOD (crash) on Windows 10 host with console Linux guest in network driver,VirtualBox 6.0.12,Windows,2019-09-29T08:18:40Z,2019-10-03T18:04:12Z,2019-10-03T18:04:12Z,"Bug previously opened as #18854 (BSOD on Windows 10 host with console CentOS 7 Linux guest in network driver) is still exist in VirtualBox 6.0.12.
It is releated to active network I/O operations on Windows 10 x64 host with Linix guests (CentOS 7 or Debian 10 x64, for example).
I have reproduce it again when I have created and installed Debian 10 guest and have executed the command
cd /opt && mkdir -p ttt && wget -O - --user UserName --password Password ftp://192.168.0.28/full_backup_29.09.2019 | restore -x -a -T /opt/ttt -f /dev/stdin
where:
192.168.0.28 is IP address of Windows 10 host
192.168.0.91 is IP address of Debian 10 guest
192.168.0.0/24 is a 1 Gbps network on ""Intel(R) Ethernet Connection (2) I219-V"" NIC adapter.",MaaSoftware
19026,Windows sleep breaks network hotplugging,VirtualBox 6.0.12,Windows,2019-10-18T06:31:03Z,2019-10-19T00:50:00Z,2019-10-19T00:50:00Z,"I have a windows 10 host system with archlinux as guest. Both operate using virtualbox 6.0.12.

In virtualbox, I have set up two network interfaces
1. Bridge 
2. Host only adapter


The network bridge usually operates either on a USB-C docking station or the laptops own network interface depending on where I am working.
So far, changing the bridges' interface (docking station vs built-in) seems to work fine. However, if I meanwhile put the windows asleep, e.g., through closing its lid it seems to break.

Here is what I mean with break:
The bridge network (when connected to either the docking station or the built-in adapter) obtains an IP from a DHCP which offers IPs in range 172.28.0.0/16.
If the above mentioned problem occurs (putting windows asleep and changing the bridge's interface e.g. from docking station to built-in or the other way around). The linux interface is not able to obtain an IP (it seems to default to an IP starting with 169.xxxx) and also restarting the dhcp client does not change this. The only thing that seems to work is to shutdown and start the VM again.",bomvir
18751,Very low upload throuput in NAT adapter - Windows 10 x64 1903 host/guest,VirtualBox 6.0.8,Windows,2019-07-11T21:52:11Z,2019-10-20T23:57:16Z,2019-10-20T23:57:16Z,"Virtualbox 6.0.8+Extensions+VBoxGuestAdditions

Upload throuput using NAT is so extremaly bad, as compared to what Bridged provides, that I wonder if a bug could be there.

Full details explained here https://forums.virtualbox.org/viewtopic.php?f=2&t=93707

As workaround I switch on/off one or the other interface in the guest.",caspertone2003
19095,Network connection mode couldn't bridge to “VMware Network Adapter” on Windows 10,VirtualBox 6.0.14,Windows,2019-11-19T02:43:27Z,2019-11-22T08:51:41Z,2019-11-22T08:51:41Z,"I have a virtual machine that can only run on the vbox，but my primary system is installed on  ""Vmware Workstation Pro""。On MacOS，vbox network can bridge to vmware network adapter such as ""VMnet8""
.But it doesn't  work that way on window 10.",zlgxzswjy
19128,Kernel bug (vboxdr - VBoxNetFlt) - eth device unintentionally enters promiscuous mode,VirtualBox 6.0.14,Linux,2019-12-03T21:42:59Z,2019-12-04T06:44:26Z,2019-12-04T06:44:26Z,"Hello, 

When a natnetwork definied. For a while, after some reboots of VM, when VM just started Linux Kernel shows problems.
It is reproducabe: make a new natnetwork eg. like this:

{{{

$ VBoxManage natnetwork add --netname anyad \
--network ""192.168.15.0/24"" --enable --ipv6 on \
--port-forward-4 ""www:tcp:[]:10080:[192.168.15.10]:80"" \
--port-forward-4 ""ssh:tcp:[]:10022:[192.168.15.10]:22"" \
--port-forward-4 ""ssl:tcp:[]:10443:[192.168.15.10]:443"" \
--port-forward-6 ""www_ipv6:tcp:[]:10080:[192.168.15.10]:80"" \
--port-forward-6 ""ssh_ipv6:tcp:[]:10022:[192.168.15.10]:22"" \
--port-forward-6 ""ssl_ipv6:tcp:[]:10443:[192.168.15.10]:443
}}}
""


{{{
$ VBoxManage dhcpserver modify --ip 192.168.15.3 --netmask 255.255.255.0 \
--netname anyad --lowerip 192.168.15.10 --upperip 192.168.15.100
}}}


Then you select natnetwork definied above for VM. After some rebootings of VM there will be Kernel messages just when you start the affected VM like this:


{{{
[ 6693.723692] vboxdrv: 0000000000000000 VMMR0.r0
[ 6693.850079] vboxdrv: 0000000000000000 VBoxDDR0.r0
[ 6693.896097] VBoxNetFlt: attached to 'enp3s0' / xx:zz:xx:zz:xx:zz
[ 6693.901656] vboxdrv: 0000000000000000 VBoxEhciR0.r0
}}}

No need VM to start the guest OS totally, as soon as VM begun to run the Kernel messages sign.
When VM will be just stopped, Kernel message will be like this:
{{{

[ 6355.406993] device enp3s0 left promiscuous mode
[ 6356.691870] vboxnetflt: 0 out of 9668 packets were not sent (directed to host)

}}}

Temporary workaround:

{{{
$ VBoxManage natnetwork remove --netname anyad
$ VBoxManage dhcpserver remove --netname anyad
}}}

After re-make a new natnetwork with same option like above I wrote.


Affected VB versions: 6.0.14 and 6.1.0_RC1 r135151[[BR]]

Affected Kernel: Linux 5.0.0-36-generic",petervagyok
6579,Cannot get a bridged network connection on guest OSes via a WPA2 wireless network with MSCHAPv2/PEAP authentication,VirtualBox 3.1.6,Windows,2010-04-22T21:58:37Z,2020-01-28T17:49:10Z,2020-01-28T17:49:10Z,"I have WinXP SP3 as a host OS.  I have used XP SP3 and Ubuntu 9.10 as guest OSes.  The problem appears to happen when I am conencted to a WPA2 wireless network with PEAP/MSCHAPv2 authentication.  The guest OSes do not get an IP address.  On the Windows guest, I get a private IP.

When I try this with networks with no PEAP/MSCHAPv2 authentication, this problem doesn't happen as I am able to get IP addresses for both guest OSes.

There was also a discussion on the VB forums where I discussed this:  [http://forums.virtualbox.org/viewtopic.php?f=6&t=30093]

Please advise.  Thanks.",prefection9791
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
19308,"Networking mode ""NAT Network"" shows very poor throughput",VirtualBox 6.0.16,Windows,2020-02-13T12:47:40Z,2020-02-13T12:47:40Z,2020-02-13T12:47:40Z,"Information about my environment:

Physical Host: Windows 10
VBox version: 6.0.16

Guest VM: Debian 9 Linux, 64 bit
Guest additions: 6.0.16.
Networking mode: NAT Network



Use case and problem description: 
I have a Linux guest on Win10 host, using vbox 6.0.16 guest additions. The VM rsync files from a vboxsf shared folder to a remote host via SSH. The network is 
plenty fast (modern 802.11n network - not used for anything else) on which I can easily achieve > 50 MiB/s (measured by iperf) from the host to the remote 
server. However, when I go from guest to remote server, it maxes out at about 200kiB/s

I have checked via atop and htop that CPU is not a bottleneck on neither client nor server. And the physical network is obviously not the bottleneck...
I have verified that I can both read and write files from the vboxsf share plenty fast as well.



I just tried plain NAT as networking mode and that works MUCH better. Now it is several MiBs per second. So it must be something to do with NAT network


So I guess there must be a problem in how networking is implemented in NAT Network compared to plain NAT that causes the slowdown.

",tdn
12038,bridged interface  one way VLAN traffic,VirtualBox 4.2.16,Mac OS X,2013-08-19T13:36:02Z,2020-02-19T09:41:37Z,2020-02-19T09:41:37Z,"A trunk port which is connected to the host adapter, is defined as a bridged interface.
On the guest host (Debian 3.2.32-1 x86_64)vlan support is enabled and the subinterfaces are up.
The host OS version is MAC OS 10.8.4.
The packet sniffer traces of the host physical interface and the virtualbox adapter interface shows that the packets ( pppoe padi ) send by the guest, will be send with the right vlan tag to the destination (seen on adapter and host interface level).
The request packet (pppoe pado) is seen only in the packet dump of the host interface (also with the expected vlan tag) but not seen in the virtualbox adapter dump ( result packet will not be send to guest os).
I have seen the same behavior when using a tagged vlan as a source interface for a guest network adapter.
I have tested this with the virtio-net and 82540EM network adapter types (same behavior).

Kind regards
Sven",svschmid
19327,Linux host vlan interface cannot be bridged to guest,VirtualBox 6.1.4,Linux,2020-02-20T16:56:07Z,2020-02-20T16:56:07Z,2020-02-20T16:56:07Z,Linux host vlan interface cannot be bridged to guest.,tulipb
19422,VirtualBox Host-Only Ethernet Adapter DHCP settings proper apply need restart of VB,VirtualBox 6.1.4,Windows,2020-03-22T20:28:05Z,2020-03-28T13:29:46Z,2020-03-28T13:29:46Z,"Changing DHCP properties of VirtualBox Host-Only Ethernet Adapter (Ctrl+H) need restart of the whole VB to be applied properly. If not, settings VB was started with are applied (whatsoever user changes them), after just guest is restarted.


It should work in other way: user stops guest, changes DHCP properties of VirtualBox Host-Only Ethernet Adapter (Ctrl+H), starts guest and changes are properly applied.


Now it needs to stop all guests, main window of VB should be closed, VB should be started again.",MikhailRokhin
19478,NAT limitations,VirtualBox 6.1.4,Windows,2020-04-11T19:07:24Z,2020-04-11T19:11:12Z,2020-04-11T19:11:12Z,"Current version NAT limitations are well documented in https://www.virtualbox.org/manual/UserManual.html#nat-limitations

Some of them, such as ICMP, have been there over ten years, as this bugtrack documents: https://www.virtualbox.org/ticket/181

So, back in march 2007, ""Frank"" decided that is was ""wontfix"".

I am trying to use VoIP solutions (SIP), asterisk, etc but I would prefer to use a VM box and use NAT for this. I am experiencing dificulties that I believe are due to those sw using inside ICMP, so, no ICMP no working...

TIA",caspertone2003
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
19536,"Problems when switching from ""NAT"" to ""Bridge"" and vice versa. VM is not assigned an IP address via DHCP when using ""Bridge"".",VirtualBox 5.2.40,Windows,2020-04-26T14:19:17Z,2020-04-26T14:19:17Z,2020-04-26T14:19:17Z,"Host is a Windows 10 (Build 1909). If you change in Virtualbox 5.2.40 with a VM (Windows 10 (Build 1909) in the network area from ""NAT"" to ""Bridge"" the VM does not get a new IP address via DHCP within the VM. 
With Virtualbox 5.2.38 it works with the same host and with the same VMs without problems online. You can switch between ""NAT"" and ""Bridge"" and the VM gets an IP address internally via its DHCP service. This can also be observed in the DHCP server of the network.  

The error is reproducible and occurs immediately after installing Virtualbox 5.2.40 and disappears as soon as Virtualbox 5.2.38 is installed again.",RonaldMcDonald
19548,VirtualBox freeze guest Ubuntu 18.04 if i add bridge or vlan,VirtualBox 6.1.6,Windows,2020-05-02T14:44:47Z,2020-05-02T14:49:17Z,2020-05-02T14:49:17Z,"host VirtualBox 6.1.6 r137129 (on windows 8 x64), guest Ubuntu 18.04 LTS HWE kernel 5.3.0-51-104generic #44~18.04.2-Ubuntu SMP Thu Apr 23 14:27:18 UTC 2020 x86_64 GNU/Linux, host have 1 ethernet interface directly connected to standalone d-link router with cable, guest have 3 nic's, 1 nat, 2 internal network, 3 brdiged-adapter. 

problem with manage bridge or vlan on guest, if i add manualy interface to bridge or configure vlan, after execute command - guest(ubuntu) freeze, do manual reboot.. example:

#bridge  
modprobe bridge
brctl addbr br0 #(all is ok)
brctl addif br0 bond0 #(all is ok)
brctl addif enp0s3 #(freeze) (tests enp0s3 as NAT, enp0s8 as Lan and enp0s9 as Bridged-adapter)

doesn't matter enp0s3/8/9 up or down before add to bridge, with IP address or without it..

#vlan
apt install vlan
modprobe 8021q
vconfig add enp0s3 100 
added VLAN with VID == 100 to IF -:enp0s3:-
(freeze)

maybe this a problem with my ubuntu in wrong network configuration or with kernel, I ask your help to make it all work :)",Deloris
19552,NAT Network is not working when I try to create or edit  a different IP other than (10.0.2.0)),VirtualBox 6.1.6,Windows,2020-05-04T09:19:43Z,2020-05-04T09:19:43Z,2020-05-04T09:19:43Z,"Virtualbox  version 6.1.6

This version has issues when trying to ping internet using NAT network.
there is no pin and cannot access the internet.

the problem is not in the default NAT network created by virtualbox 10.0.2.0/24.

the problem appears when i configure a new NAT network or edit the default one, like for example 192.168.0.0/24 in this case it will not work and can not access the internet.

I tested the following versions 6.0.20, 6.0.18, 6.0.12 and all of them work fine with no problems. 

 ",hassanmonji
19626,"VirtualBox host-only adapter keeps getting set to an invalid configuration, which breaks multicast.",VirtualBox 6.1.8,Windows,2020-05-27T18:29:01Z,2020-05-28T14:51:14Z,2020-05-28T14:51:14Z,"Greetings!

OS: Windows 10 Pro x64
VirtualBox: 6.1.8r137981(Qt5.6.2)

The ""VirtualBox Host-Only Network"" adapter in Windows keeps getting set to an invalid state. When virtualbox is first installed, it populates the IPv4 IP address and DNS server. I also have to manually set the ""Automatic Metric"" to something like 800 as leaving it set to automatic breaks Multicast packets.

Every so often, I'll find I can't join a Multicast stream. Checking the settings in the ""VirtualBox host-only network"" adapter reveals:
- IP address/Subnet/Gateway are still set to manual, but are blank.
- DNS server is set to manual, and is completely blank
- Automatic Metric is set to automatic.

If I set the metric back to 800 and click ok, I get a message saying the IP address needs to be specified.

I have absolutely no idea what keeps changing the network properties for this adapter and setting it to an invalid state.",Fishscene
19638,no network connection with virtio-net after some time,VirtualBox 6.0.22,Linux,2020-06-03T17:54:10Z,2020-06-03T17:57:42Z,2020-06-03T17:57:42Z,"Hi,

I'm running an Ubuntu 18.04 guest on a ubuntu 18.04 host. The guest uses virtio-net for the network adapter.

After some uptime, you can use the interface anymore. The syslog is flodded with

{{{
net eth0: Unexpected TXQ (0) queue failure: -5
}}}

I have to reboot the VM to get it working again.

If you need any information, please don't hesitate to ask for.

Regards,
meiser",Peter Meiser
19639,host freezes when network load is high,VirtualBox 6.1.8,Windows,2020-06-03T20:49:20Z,2020-06-03T20:49:20Z,2020-06-03T20:49:20Z,"Hello, my friends.

I use a virtual machine to work while I stay in quarantine.
Periodically I faced with heisenbug when my host machine freezes.
I had no idea why this was happening.
But today I was able to reproduce the steps that lead to freezing.

So, what I have.
VBox: 6.1.8
Host: win 7 x64
Motherboard: ASUS AC97 rev.2 
Host disk: SSD Plextor PX-128M6S
Host network card: Realtek PCIe GBE (pci\ven_10ec&dev_8168&subsys_85051043&rev_09)

Guest: win 7 x64
Guest virtual network: Bridge / Intel pro 1000MT Desktop
Virtual disk: VHD / AHCI / i/o caching enabled
Virtual chipset: ICH9 / i/o apic enabled


What I do.
When I try to download a large file (e.g. 1 GB) 
then after a while the guest and the host system freezes.. absolutely )))

What could be the real cause of freezing
- bridged network adapter,
- i/o caching, scaling virtual disk,
- or chipset ...
I don't know,
but I tried a dozen variants of parameters,
and all the same, periodically it happens..
",Aleksey_Popov_1988
19651,DNS not working with NAT on some networks.,VirtualBox 6.1.10,Windows,2020-06-09T12:39:59Z,2020-06-09T12:39:59Z,2020-06-09T12:39:59Z,"Host is Win10, Guest is Debian 10.  Network set to NAT with TCP port 22 forwarded (though ssh will not work either)

Internet access worked fine until I changed WIFI networks. DNS does not seem to work. I can ping the DNS server, but DNS resolving does not work.  I've noticed some strange patterns.  At home it works fine. When I connect to my cellphone hotspot while at home everything worked too. At my hotel, at first it would not work. Then trying at my remote office guest wifi network, it also would not work. Then trying my cellphone hotspot mode, it also would not work. However, upon returning back to my hotel, it suddenly worked. I have the exact same pattern with trying to connect my wireguard vpn. Note back at the hotel, once I connect the vpn, dns stops working, it is unable to contact the dns server on my vpn, eventhough the host is able to.  Virtualbox sees the network changes, debian updates the network configuration, I can ping addresses outside, but dns fails with the ICMP issue. I've noticed that the DNS issue is ok if I switch to a bridged network. Unfortunately, some networks will only give me one IP so getting it to work with NAT is preferred.


In the VM log, I see:
{{{
00:00:18.130180 NAT: Link up
00:00:19.424766 NAT: DHCP offered IP address 10.0.2.15
}}}
On the guest, in network manager, it has a 10.0.2.15 IP address and is able to get DNS servers matching what I have on the host. /etc/resolv.conf has the correct servers
I have tried rebooting the VM. I've tried turning off the firewall on the host.


/etc/resolv.conf:
{{{
nameserver 1.1.1.1
}}}
ping 1.1.1.1 works
{{{
11:38:39.397764 IP 10.0.2.15 > 1.1.1.1: ICMP echo request, id 2960, seq 2, length 64
11:38:39.436573 IP 1.1.1.1 > 10.0.2.15: ICMP echo reply, id 2960, seq 2, length 64
}}}
dig @1.1.1.1 google.com does not work
{{{
11:38:43.814134 IP 10.0.2.15.50821 > 1.1.1.1.53: 29800+ [1au] A? google.com. (51)
11:38:43.814861 IP 10.0.2.2 > 10.0.2.15: ICMP net 1.1.1.1 unreachable, length 36
11:38:45.697058 IP 10.0.2.15.50263 > 172.30.0.27.53: 32978+ AAAA? clients3.google.com. (37)
11:38:45.697650 IP 10.0.2.15.46410 > 172.30.0.27.53: 56459+ A? clients3.google.com. (37)
11:38:45.698116 IP 10.0.2.2 > 10.0.2.15: ICMP net 172.30.0.27 unreachable, length 36
11:38:45.698446 IP 10.0.2.2 > 10.0.2.15: ICMP net 172.30.0.27 unreachable, length 36
11:38:48.814785 IP 10.0.2.15.50821 > 1.1.1.1.53: 29800+ [1au] A? google.com. (51)
11:38:48.816463 IP 10.0.2.2 > 10.0.2.15: ICMP net 1.1.1.1 unreachable, length 36
}}}",eng3
19675,DHCP server mac address conflicts with nat-host mac-address,VirtualBox 6.1.10,Windows,2020-06-19T19:56:40Z,2020-06-19T19:56:40Z,2020-06-19T19:56:40Z,"
https://gitlab.alpinelinux.org/alpine/aports/-/issues/11669

When the two mac-addresses of the dhcp server and the emulated-host interface in NatNetwork are different, the arp cache may end up with the mac address of host entered as that from the dhcp. WHen that happens further communcation with host (CIFS/ssh) fails.

The eesolution was to set the dhcp server from the default 10.1.x.2 to 10.1.x.5. Then mac addresses don't clash

There should be a vboxmanage setting to set the mac address of the 
host-ip and of the dhcp-server-ip ",gkamathh
8698,VirtualBox Host-Only Network Adapter prevents multicast traffic,VirtualBox 4.0.4,Windows,2011-04-07T21:12:06Z,2020-06-28T14:04:55Z,2020-06-28T14:04:55Z,"After installing Oracle VirtualBox and VirtualBox installing the ""VirtualBox Host-Only Network"" on my Windows 7 64-bit machine, I am no longer able to receive multicast streams on the host machine. This problem occurs even when VirtualBox is not running.

To get around this issue, I have to go into Network Connections everytime I want to stream from a multicast source and disable the VirtualBox Host-Only Network adapter. I then have to remember to reenable it everytime I wish to use VirtualBox.",Michael Irigoyen
19773,Cannot see Host Only Adapter in Windows 10 adapters,VirtualBox 6.1.10,Windows,2020-07-28T08:51:40Z,2020-07-28T08:51:40Z,2020-07-28T08:51:40Z,"After some wailing and gnashing of teeth, I got host only networking to work with Uvuntu 20.04. I was expecting to see the adapter in the Control Panel\Network and Internet\Network Connections but it doesn't show up. It does appear in the Device Manager.
",d0325mgray
19764,paravirtualized adapter doesn't receive packets until a ping6 of the gateway,VirtualBox 6.1.10,Mac OS X,2020-07-25T11:30:11Z,2020-07-28T20:00:10Z,2020-07-28T20:00:10Z,"OpenBSD 6.7 guest on macOS Catalina, where the guest is configured for IPv6-only and a paravirtualized network bridged adapter. After booting the OpenBSD guest, and obtaining the IPv6 address by autoconfiguration, the Internet seems unreachable. Simultaneous packet captures on the guest and the host show, for example, a DNS request egress the guest and the host, and the DNS response ingress the macOS host but not the OpenBSD guest. A workaround is to ping6 the IPv6 gateway public address, then suddenly packets for the guest will start showing up in the guest packet capture.

However, the ping6 also inserts the neighbor entry for the IPv6 gateway public address. Otherwise, because of autoconfiguration, the Internet6 default route is the IPv6 gateway link-local address and there is only the gateway's link-local address in the neighbor mapping table.",jasonmader
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
19837,Forwarded ports are blocked,VirtualBox 6.1.10,Windows,2020-08-27T13:42:17Z,2020-08-27T13:42:17Z,2020-08-27T13:42:17Z,"It can happen that ports which are forwarded to the guest are blocked on the host and therefore you are unable to open those ports on the host. Then you have to remove the forwarding, open the ports and then re-add the forwarding.

Expected behaviour:
Forwarded ports should not be blocked.",jnevada
16221,After upgrading to 5.1.10 Network interface is not working enp0s3: Detected Tx Unit Hang,VirtualBox 5.1.10,Windows,2016-11-23T15:56:25Z,2020-09-08T16:49:04Z,2020-09-08T16:49:04Z,"After upgrading to virtualbox 5.1.10  Network interface is not working after boot unless its manually reset after boot.Downgrading to virtualbox 5.1.8 fixes the problem.However, upgrading to 5.1.11 is mostly working but not 100% of the time. During the testing it didn't work a few times.
Linux arch 4.8.10-1-ARCH guest on windows 10 Host. 

journalctl -b
kernel: e1000 0000:00:03.0 enp0s3: Detected Tx Unit Hang",vdv
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
19968,File transfers to / from guest corrupted,VirtualBox 6.1.14,Windows,2020-10-14T16:03:34Z,2020-10-15T18:02:39Z,2020-10-15T18:02:39Z,I have a Centos guest OS running on Win10 host. I am unable to reliably transfer files or perform a Yum update on the guest OS. With Yum update the checksums consistently fail - but always different values for the downloaded file. Mozilla FTP and WinSCP to the guest also fail. Makes no difference whether using bridged network or local host. Seems to occur on all VM's I have running. What can be causing this? Seems everything else runs ok.,VicK
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
20024,Linux host freezes with bridged adapter and apt,VirtualBox 6.1.16,Linux,2020-11-08T00:50:16Z,2020-11-08T03:28:46Z,2020-11-08T03:28:46Z,"My Linux (Fedora 33) host freezes whenever I enable bridged adapter and the guest transfers (some) data.

Steps to reproduce:
1. Install an Ubuntu 20.04 server guest
2. Go to Guest settings, Network, Attached to, Bridged Adapter
3. Run an apt install command on it. I was following [these instructions](https://jitsi.github.io/handbook/docs/devops-guide/devops-guide-quickstart).
4. The host completely freezes, and I'm forced to reboot.

I've installed some server software (Jitsi Meet) and now it freezes even on guest boot.

Some hardware details:

{{{
*-cpu
          product: AMD Ryzen 5 3500U with Radeon Vega Mobile Gfx
          vendor: Advanced Micro Devices [AMD]
          physical id: 1
          bus info: cpu@0
          size: 1443MHz
          capacity: 2100MHz
          width: 64 bits
          capabilities: fpu fpu_exception wp vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush mmx fxsr sse sse2 ht syscall nx mmxext fxsr_opt pdpe1gb rdtscp x86-64 constant_tsc rep_good nopl nonstop_tsc cpuid extd_apicid aperfmperf pni pclmulqdq monitor ssse3 fma cx16 sse4_1 sse4_2 movbe popcnt aes xsave avx f16c rdrand lahf_lm cmp_legacy svm extapic cr8_legacy abm sse4a misalignsse 3dnowprefetch osvw skinit wdt tce topoext perfctr_core perfctr_nb bpext perfctr_llc mwaitx cpb hw_pstate sme ssbd sev ibpb vmmcall fsgsbase bmi1 avx2 smep bmi2 rdseed adx smap clflushopt sha_ni xsaveopt xsavec xgetbv1 xsaves clzero irperf xsaveerptr arat npt lbrv svm_lock nrip_save tsc_scale vmcb_clean flushbyasid decodeassists pausefilter pfthreshold avic v_vmsave_vmload vgif overflow_recov succor smca cpufreq
}}}



{{{
*-network
                description: Wireless interface
                product: RTL8822CE 802.11ac PCIe Wireless Network Adapter
                vendor: Realtek Semiconductor Co., Ltd.
                physical id: 0
                bus info: pci@0000:02:00.0
                logical name: wlp2s0
                version: 00
                serial: [REMOVED]
                width: 64 bits
                clock: 33MHz
                capabilities: bus_master cap_list ethernet physical wireless
                configuration: broadcast=yes driver=rtw_8822ce driverversion=5.8.18-300.fc33.x86_64 firmware=N/A ip=[REMOVED] latency=0 link=yes multicast=yes wireless=IEEE 802.11
                resources: irq:81 ioport:2000(size=256) memory:c0700000-c070ffff
}}}

I will append a log file in some minutes",gabrc
20044,IP Duplicate with MacOS 11.0.1 (Big Sur) and VBox 6.1.16,VirtualBox 6.1.16,Windows,2020-11-17T06:08:36Z,2020-11-17T06:08:36Z,2020-11-17T06:08:36Z,"After installing MacOS X 11.0.1 and reinstalling VBox 6.1.16 to fix the kernel issue.

Now all Guest OS cannot connect to network (Bridged Adapter), since it detect a conflict IP address.

Looking in Windows Event Viewer and the duplication of 0.0.0.0 is identified with the MAC address of the Host MacOS server

I think we should have a new release to correct this issue in MacOSX Big Sur
Thank you",BDelorme
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
20054,network problems under bigsur macOS version,VirtualBox 6.1.16,Windows,2020-11-20T14:05:49Z,2020-12-01T11:59:52Z,2020-12-01T11:59:52Z,"I have problems getting a working network connection when I transferred from Catalina to Bigsur

Sometimes VBOX crashes when I use NAT option for the adapter, normally use bridged option",pbvbox
16973,"Thunderbolt 3 Docks, VirtualBox needs new behavior model",VirtualBox 5.1.26,Windows,2017-08-02T18:50:58Z,2020-12-02T06:19:52Z,2020-12-02T06:19:52Z,"My specific hardware.
* HP zBook 15 G3 Laptop
  * NIC: Intel Dual Band Wireless-AC 8260
  * NIC: Intel Ethernet connection I219-LM
* HP Elite Thunderbolt 3 Dock
  * NIC: Broadcom NetXtreme Gigabit Ethernet
* Host: Windows 7 Enterprise
  * Selected Bridged Adapter Intel PRO/1000 MT Desktop
* Guest: CentOS 7

**Situation**
* Thunderbolt 3 docking stations extend the PCIe such that new devices may appear when docked and disappear when undocked.
* One specific issue is with the NIC. While docked I use the NIC provided by the docking station.
* When undocked I use the Wireless NIC or the NIC on the motherboard.

**Issue**
* VirtualBox is unable to cope went the NIC in the dock completely disappears after undocking.
  * In Windows Device Manager the NIC does not appear
* It is also does not seem to hand gracefully when a Wireless NIC is disconnected from any network.
  * VirtualBox has no wireless bridge adapter option.

I hope this description is through enough.",J.R.
15845,e1000 Detected Tx Unit Hang,VirtualBox 5.1.2,Windows,2016-08-22T09:48:52Z,2020-12-17T12:22:56Z,2020-12-17T12:22:56Z,"Hi,

My Arch Linux desktop (client) is sometimes hanging, seems like the kernel module is detecting a disconnection:
{{{
aug 22 11:25:07 virtwin nm-dispatcher[4102]: req:1 'dhcp4-change' [enp0s3]: new request (0 scripts)
aug 22 11:25:07 virtwin nm-dispatcher[4102]: req:1 'dhcp4-change' [enp0s3]: completed: no scripts
aug 22 11:25:08 virtwin chromium.desktop[1507]: [1507:1530:0822/112508:ERROR:connection_factory_impl.cc(369)] Failed 
aug 22 11:25:38 virtwin NetworkManager[271]: <info>  [1471857938.2914] device (enp0s3): link disconnected (deferring 
aug 22 11:25:38 virtwin kernel: e1000 0000:00:03.0 enp0s3: Reset adapter
aug 22 11:25:38 virtwin NetworkManager[271]: <info>  [1471857938.3570] device (enp0s3): link connected
aug 22 11:25:38 virtwin NetworkManager[271]: <info>  [1471857938.3571] device (enp0s3): DHCPv4 lease renewal requeste
aug 22 11:25:38 virtwin kernel: e1000: enp0s3 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: RX
aug 22 11:25:38 virtwin NetworkManager[271]: <info>  [1471857938.3753] dhcp4 (enp0s3): canceled DHCP transaction, DHC
aug 22 11:25:38 virtwin NetworkManager[271]: <info>  [1471857938.3753] dhcp4 (enp0s3): state changed bound -> done
aug 22 11:25:38 virtwin NetworkManager[271]: <info>  [1471857938.3760] dhcp4 (enp0s3): activation: beginning transact
aug 22 11:25:38 virtwin NetworkManager[271]: <info>  [1471857938.3783] dhcp4 (enp0s3): dhclient started with pid 4117
aug 22 11:25:38 virtwin dhclient[4117]: DHCPREQUEST on enp0s3 to 255.255.255.255 port 67
aug 22 11:25:41 virtwin kernel: e1000 0000:00:03.0 enp0s3: Detected Tx Unit Hang
                                  Tx Queue             <0>
                                  TDH                  <1>
                                  TDT                  <9>
                                  next_to_use          <9>
                                  next_to_clean        <2>
                                buffer_info[next_to_clean]
                                  time_stamp           <10012adce>
                                  next_to_watch        <2>
                                  jiffies              <10012b100>
                                  next_to_watch.status <0>
}}}
I must admit I do all my work in this virtual machine, but I can't recall to have seen disconnects in Windows (the host).

Guest OS: Arch Linux
Kernel: 4.7.1-1-ARCH",LordChaos
20109,Guest Bridged Networking Stops Working After Host Link Was Down,VirtualBox 6.1.16,Windows,2020-12-31T00:11:39Z,2020-12-31T00:11:39Z,2020-12-31T00:11:39Z,"I tested bridged networking on a Windows 10 Host with a Windows 7 64-bit Guest and a Windows XP 32-bit Guest.  They both exhibit the same problem with a bridged network adapter.  If the host's bridged link was down when the virtual machine was started, or goes down temporarily after the virtual machine is started, communication is lost through the bridged adapter on the host.  It is still possible to ping the host's address assigned to the real adapter, but no devices connected to the LAN on the real host adapter will communicate.

Virtual Network Adapter
Windows 7 64-bit Intel PRO/1000 MT
Windows XP 32-bit PCnet-FAST III

Host LAN Adapter Intel I219-V (1 Gb) VEN 0x8086 DEV 0x15B8
Host OS Windows 10 64-bit 10.0.19042

The work around for the problem is to temporarily disable and then enable the host LAN adapter using the Network Connections in the Control Panel.  Then disable and enable the virtual network adapter in the devices menu for the virtual machine.  After doing both of those things, the bridged adapter will communicate again.  I have noticed that it sometimes recovers if I just temporarily disable the network adapter for the virtual machine, but that seems to depend on whether the host adapter was up when the virtual machine was started.

I noticed this problem on a LAN port connected to a test network that normally has the switch powered off until I need to run tests.  If I power up the switch after starting the virtual machine then there is no communication to the network switch until I perform the steps that I outlined.",ErikWlfn
16808,Removed network adapters are still showing in bridged networking,VirtualBox 5.1.22,Windows,2017-06-03T05:48:24Z,2021-01-13T16:15:05Z,2021-01-13T16:15:05Z,"When I run ""vboxmanage list bridgedifs"", I get a list of adapter that still contains adapters that are not in the system anymore. In my case, I used to have VLANs adapters that were created using the Intel ANS utility. The VLAN were since removed but are still showing in VirtualBox bridged networking. This is annoying.

In the log below, all adapters having a HardwareAddress of 00:00:00:00:00:00 are not in the system anymore but are still listed in all VirtualBox bridged networking list.

I tried removing and reinstalling VB, removing and reinstalling the NDIS6 Bridged Network Driver, nothing works, the old adapters are still showing up in the list. The Windows registry does not contain any references to the GUID of the removed adapters anymore. Why is VB still 

{{{
C:\Program Files\Oracle\VirtualBox>VBoxManage list bridgedifs
Name:            Intel(R) Ethernet I210-T1 GbE NIC
GUID:            da04ab21-b3e6-4bad-b6ad-497cfcd15188
DHCP:            Enabled
IPAddress:       192.168.4.170
NetworkMask:     255.255.255.3
IPV6Address:
IPV6NetworkMaskPrefixLength: 0
HardwareAddress: a0:36:9f:cd:99:ad
MediumType:      Ethernet
Status:          Up
VBoxNetworkName: HostInterfaceNetworking-Intel(R) Ethernet I210-T1 GbE NIC

Name:            Intel(R) Ethernet I210-T1 GbE NIC - VLAN : untagged Intranet
GUID:            42ffbcdd-fad9-4a1e-bc7f-de92582df835
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-Intel(R) Ethernet I210-T1 GbE NIC - VLAN : untagged Intranet

Name:            Intel(R) Ethernet I210-T1 GbE NIC - VLAN : VLAN 5 DMZ
GUID:            dbc6c4c8-8e06-4b50-a0ba-b82766724257
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-Intel(R) Ethernet I210-T1 GbE NIC - VLAN : VLAN 5 DMZ

Name:            Intel(R) Ethernet I210-T1 GbE NIC - VLAN : VLAN 1 Gestion
GUID:            d59e7f43-fc7f-4830-902a-74881b6354db
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-Intel(R) Ethernet I210-T1 GbE NIC - VLAN : VLAN 1 Gestion

Name:            Intel(R) Ethernet I210-T1 GbE NIC - VLAN : VLAN 3 Tests
GUID:            146679e9-63c0-439f-a968-1545520a0e34
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-Intel(R) Ethernet I210-T1 GbE NIC - VLAN : VLAN 3 Tests
}}}

",viaujoc
20147,Problems when masquerade is enabled on host,VirtualBox 6.1.16,Linux,2021-01-22T19:27:56Z,2021-01-22T19:27:56Z,2021-01-22T19:27:56Z,"Steps to reproduce issue:

1. Configure host linux with firewalld  + enable masquerade on public zone (or configuration alike with iptables or nftables by hand)
2. Test access to both http and https on guest side
3. Disable masquerade on host and repeat 2

If netfilter masquerading is enabled on host, and guest is in bridge modem, both http and https don't work.

For example:

{{{

curl -I http://www.virtualbox.org
curl: (56) Recv failure: Connection reset by peer
root@techier-glossa:~# curl -I https://www.virtualbox.org
curl: (35) OpenSSL SSL_connect: Connection reset by peer in connection to www.virtualbox.org:443
}}}


If I disable netfilter masquerading, it works.

In bridge mode it should not concern at all if host is doing that.

This the configuration of firewalld:

[root@munster ~]# firewall-cmd --zone=lxc --list-all   

{{{
lxc (active)
  target: ACCEPT
  icmp-block-inversion: no
  interfaces: lxcbr0
  sources: 
  services: 
  ports: 
  protocols: 
  masquerade: no
  forward-ports: 
  source-ports: 
  icmp-blocks: 
  rich rules: 
[root@munster ~]# firewall-cmd --zone=libvirt --list-all
libvirt (active)
  target: ACCEPT
  icmp-block-inversion: no
  interfaces: virbr0
  sources: 
  services: dhcp dhcpv6 dns ssh tftp
  ports: 
  protocols: icmp ipv6-icmp
  masquerade: no
  forward-ports: 
  source-ports: 
  icmp-blocks: 
  rich rules: 
        rule priority=""32767"" reject
[root@munster ~]# firewall-cmd --zone=public --list-all
public (active)
  target: default
  icmp-block-inversion: no
  interfaces: wlp108s0
  sources: 
  services: dhcpv6-client kdeconnect mdns ssh
  ports: 
  protocols: 
  masquerade: yes
  forward-ports: 
  source-ports: 
  icmp-blocks: 
  rich rules: 

}}}



As far I know, In bridge mode it should not concern at all if host is doing that, should it?

Thanks in advance",sblk
20095,Virtualbox still resets intel adapters,VirtualBox 6.1.14,other,2020-12-17T12:31:17Z,2021-01-24T13:34:08Z,2021-01-24T13:34:08Z,"Using virtualbox 6.1.14 on linux host with linux guest makes intel driver to reset adapter.
This maybe duplicate but someone is closing not fixed bugs.
Seems like the bug is present from over 10 years.
I tried virtio but its not usable because after 2-3 days or so it just freez my virtual machines and they need to be power cycled. E1000 driver just makes disconnects way better. Using PCNet drivers are no option for me because i need gigabit connection.
",Sanitariu
20188,"Network change cause bridged network broken, no adapters in bridged adapter.",VirtualBox 6.1.16,Windows,2021-02-14T15:20:32Z,2021-02-14T15:20:32Z,2021-02-14T15:20:32Z,"OS: Windows 10 1909 18363.1316[[BR]]
VBox version: 6.1.16 r140961
----
Problem: (I guess) network changes might cause bridged network broken, like this:
[[Image(https://i.imgur.com/dtOqgNm.png)]]

All interfaces are gone in the bridged adapter. Only showing ""not selected""

----
How to reproduce:

Install/run/upgrade Nox player(a Android simulator, it's a VM that running android) while running the VirtualBox.

And I recorded a video to reproduce this bug: https://www.youtube.com/watch?v=RzTA-qMp3Uk

----
The only way to get bridged network back is upgrade VirtualBox or reinstall.
If I am using the latest VirtualBox, I have to uninstall it, then install it again. Very annoying.
Repair VirtualBox/reboot PC doesn't work.

I guess the installation/running process of Nox player changed some network setting, cause VirtualBox lost all of the network setting. And repair doesn't reconfigure it.

Is there any other way I can reconfigure network settings without reinstall? 
The only way to reconfigure it that I found is uninstall and install again, which makes me reboot my PC twice and reconfigure all vm again.

And pleasse fix this bug,thank you. The network of VM always crash after I running the Nox player. I can't use VirtualBox at all.",HuJK
20194,Host-only card cannot be created,VirtualBox 6.1.18,Windows,2021-02-15T20:02:12Z,2021-02-15T20:02:12Z,2021-02-15T20:02:12Z,"Dear Team,

I should create an internal network for a uni project, but I cannot create host-only server for my debian virtual machine. Anything I do I keep receiving the below error message:

A gazda hálózati kártya létrehozása sikertelen.

Querying NetCfgInstanceId failed (0x00000002).

Eredmény kód: E_FAIL (0x80004005)
Komponens: HostNetworkInterfaceWrap
Interfész: IHostNetworkInterface {455f8c45-44a0-a470-ba20-27890b96dba9}


Virtualization is allowed, nothing is blocked.",Volodka91
17897,"Port forwardings can only be added, not deleted with ""VBoxManage natnetwork""",VirtualBox 5.2.12,all,2018-07-27T14:59:59Z,2021-02-16T01:32:59Z,2021-02-16T01:32:59Z,"For ""natnetwork"" type network setups, port forwarding rules can be added with e.g.:

{{{
VBoxManage natnetwork modify --netname kommune1 --port-forward-4 ""...""
}}}

but, there is no corresponding way to remove an existing rule.

For ""nat"" type networks, both options exist:

{{{
VBoxManage modifyvm Name --natpf1 ""...""
VBoxManage modifyvm Name --natpf1 delete ""...""
}}}

I would like to see an option added to `VBoxManage natnetwork modify` that allows the deletion of rules by their name.

In the meantime, as a workaround, the documentation should suggest that rules can be manually removed from the configuration file `~/Library/VirtualBox/VirtualBox.xml` (on macOS, not sure about the path on other platforms).",damiano++
20099,bridged mode not working in VB on macOS Big Sur for VB windows clients,VirtualBox 6.1.16,Mac OS X,2020-12-23T11:01:20Z,2021-02-17T03:59:37Z,2021-02-17T03:59:37Z,"As posted in the VB Forum:
Finally got to the bottom of the issue after finding a few hints, pointers and bits of information at various places.

After the upgrade from Catalina to Big Sur, networking caused several issues in VB windows instances.
I've always used bridged mode with no issues for both wired and wireless connections before the upgrade.

My symptoms , In bridge mode DHCP in windows failed to obtain a valid IP address, starting with duplicate found and quickly followed with a 192.168.1 address that would not give a proper connection , I use 192.168.0 subdomain. Could not get neither the wired nor the wireless connection to work.

When setting NAT mode the VB windows instance, VB would fatally crash the VB windows instance, so not windows but VB crashed.

I concluded that the last issue must have been caused by VB drivers being messed up after the Catalina to Big Sur transition.

I downloaded the 6.1.16 VB version and used the uninstall script ( available in the finder window when opening the vb.dmg file) to remove VB from the mac.
Don't worry it only removes the drivers and VB itself, not any of your configs or VB disks and client images.
Then re-installed VB. This got NAT back working.

Bridged mode still had same issues for windows clients, it has something to do with change in behaviour of how big sure handles MAC addresses by the looks of it.
The fix is that you have to give the network adapter in VB that is mapped on your mac network adapter the same MAC address as the MAC address for the adapter on your MAC.
This is not a good permanent fix as you this prevents you to have more than one VB client run on your MAC as all you would get duplicated MAC addresses on your system. Be aware of that. Also if you use DHCP with preset IP addresses, each VB windows client will get the same IP address.",pbvbox
20228,Don't start VM with vagrant instruction,VirtualBox 6.1.18,other,2021-02-28T08:53:27Z,2021-02-28T08:53:27Z,2021-02-28T08:53:27Z,"Hi,

I would like to use vagrant for initializing a docker environment (just for context).

And the vm does not start because it has a problem at the network level, which configured with nat and bridge adapter.
The nat is ok but the bridge does not start with an error code 0X80004005 (VERR_INTNET_FLT_IF_NOT_FOUND).

I need help solving my problem.

Thank

Thank",FredC
20279,Long-timeout TCP Sessions,VirtualBox 6.1.18,Windows,2021-03-28T20:53:11Z,2021-03-28T20:53:11Z,2021-03-28T20:53:11Z,"I have a case with long time-out TCP sessions that come from VirtualBox NAT network mode. When I created half-open TCP sessions from the VM to an external TCP Host (by sending SYN packets but not reply the SYN/ACK with ACK packets). After 10 seconds, the external TCP Host proceeded to close the connections by sending FIN packets. This put the port VirtualBox used for those connections to CLOSE_WAIT state. As I observed, the current VirtualBox's CLOSE_WAIT timeout is about 10 minutes.

I have a theory that, if I can generate enough number (maybe 40,000?) of CLOSE_WAIT state TCP sessions, I can occupy all of the port VirtualBox can use for transmitting, which make the internal VM can not create new connection with external hosts, for 10 minutes. 

I suggest that the CLOSE_WAIT timeout should be lowered to 2 minutes to counter the possible problem.",nds21
15144,BSOD - Windows 10 host VBoxNetLwf.sys,VirtualBox 5.0.14,Windows,2016-02-12T16:56:54Z,2021-03-31T21:56:18Z,2021-03-31T21:56:18Z,"I have had a handful of intermittent Windows 10 'blue screen of death' host crashes of type PAGE FAULT IN NONPAGED AREA which mention VBoxNetLwf.sys over the last few weeks. This has been observed with multiple minor releases of VirtualBox since version 5.0 and multiple releases of Windows 10 Professional. 

I suspect this may not be a VirtualBox bug and more likely an issue with our security software (Symantec Endpoint Protection) or the host Windows OS (as I only noticed this issue since updating from Win 8.1 Pro). 

Happy to provide any more info that might help, attached a screen grab of the crash. ",kpm
19231,Network interface not found error after upgrading to 6.1.0,VirtualBox 6.1.2,Mac OS X,2020-01-15T23:03:04Z,2021-04-02T10:33:02Z,2021-04-02T10:33:02Z,"After upgrading to VB 6.1.0 and still with 6.1.2 I get the following error when trying to start both Windows and Linux VMs: 

Could not start the machine Linux OBI 7.2.64.0 because the following physical network interfaces were not found:
en4: Thunderbolt Ethernet Slot 2 (adapter 1)
You can either change the machine's network settings or stop the machine.

This always worked before. This is a MacOS Catalina host (10.15.2) using a wired ethernet connection off a Thunderport dock. The interface name is ""en4: Thunderbolt Ethernet Slot 2"". I am using this in bridge mode. Switching to NAT works fine.


",Stooxie
20311,Failed to create a host network interface.,VirtualBox 6.1.20,Windows,2021-04-21T16:58:04Z,2021-04-21T16:59:18Z,2021-04-21T16:59:18Z,"Failed to create a host network interface.

SetupDiCallClassInstaller (DIF_INSTALLDEVICE) failed (0x00000002).

Result Code: E_FAIL (0x80004005)
Component: HostNetworkInterfaceWrap
Interface: IHostNetworkInterface {455f8c45-44a0-a470-ba20-27890b96dba9}

",TH
20302,Client ID prevails over MAC based mapping with the NAT Network DHCP server,VirtualBox 6.1.18,Linux,2021-04-13T09:35:05Z,2021-04-22T14:00:30Z,2021-04-22T14:00:30Z,"I've got two Ubuntu (though what matters here is Systemd-Network) guest VMs connected to a NAT Service network with the DHCP service enabled.
I have added a static mapping between the guests NIC MAC addresses and their assigned IPs. The NatNetwork-Dhcpd.config file shows what I mean:

    <Config MACAddress=""08:00:27:00:00:01"" name=""59c98231-ac44-4e62-8bfe-1bd937c3fff1/0"" fixedAddress=""192.168.40.101""/>

    <Config MACAddress=""08:00:27:00:00:02"" name=""824e3a1b-2542-454d-bfee-c8aad2ad1c90/0"" fixedAddress=""192.168.40.102""/>

The same information is reflected in `VirtualBox.xml` (the global config file) though when using `VBoxManage` to set up the mapping I did use the first NIC of each guest to set the mapping hence the `/0` after the guest VM UUID:


    <Config MACAddress=""08:00:27:00:00:01"" name=""59c98231-ac44-4e62-8bfe-1bd937c3fff1/0"" fixedAddress=""192.168.40.101""/>

    <Config MACAddress=""08:00:27:00:00:02"" name=""824e3a1b-2542-454d-bfee-c8aad2ad1c90/0"" fixedAddress=""192.168.40.102""/>

Now it comes the twist: DHCP Client ID in machines running Systemd-Network use /etc/machine-id to construct it but both machines have the same contents (due to cloning, you know) in this file hence the Client ID sent to the DHCP is always the same (as seen in NatService-Dhcpd.log)... and the dhcp server in the Nat Service returns the same IP address for both guests.

Is it a bug, a feature or just RFC compliance?
Thanks in advance.",jcb
20283,Network issues on Guest-VM,VirtualBox 6.1.18,Mac OS X,2021-04-02T19:41:36Z,2021-04-24T18:56:04Z,2021-04-24T18:56:04Z,"Hey,

I am using VirtualBox on macOS Big Sur and seem to have found a problem.
I am running a Linux VM with a NAT-Network or NAT adapter and whenever I run nmap on there I am unable to reach my gateway (host) anymore. 
It's either non-responsive or responding very slowly (700ms-3000ms).

[img]https://imgur.com/a/2HU4Lrk[/img]

Is there any fix for this?",Eagleo0
20337,Natnetwork loose connectivity after a while,VirtualBox 6.1.22,Linux,2021-05-04T08:29:04Z,2021-05-04T08:29:04Z,2021-05-04T08:29:04Z,"Hi,
I have created 5 VMs based on Debian 10, with Natnetwork configured (because i need to let the VMs talk to each others and access the Vpn on the host).

Each one has static IP, no specific tunning or special configuration. just Debian Vms and default natnetwork configured.

All Vms are working without any problems, i can access it with port forwarding. and after a while (one minute, 3 minutes...), the IP connectivity is suddenly cut, the ssh connections are stuck !

I must restart the natnetwork with VBoxManage ... Same result with paravirtualized network interface or Intel Pro desktop.
So, it s impossible to work in theses conditions.

it seems that problem exists for years or i missed something ?

Thanks to do something on that issue.
Francois




",Francois94130
14748,nat network hangs intermittantly,VirtualBox 5.0.8,Linux,2015-10-26T12:17:06Z,2021-05-04T20:17:25Z,2021-05-04T20:17:25Z,"Host: Ubuntu 14.04 64Bit

Virtualbox 5.0.8

Guest: Windows Server 2012, Windows XP - defect present for both guests.

Both guests are headless, used only by RDP.

Sometimes (1-2 times per day) guest network adapter stops to recieve any packets from ""media"", can't ping default gw for this network interface.

The only things that fix issue is nat network restart:

{{{
VBoxManage natnetwork stop --netname nat-int-network-2
VBoxManage natnetwork start --netname nat-int-network-2
}}}

Of course, may be there are another ways... reboot particular guest or perform ""sudo  /etc/init.d/vboxdrv restart"" (requiring all VMs stop)... But the only way I found to fix issue (while not rebooting/stopping guest is restart nat network...
 
I have two nat networks (192.168.1.0/24 and 192.168.2.0/24). They hangs indpendently:

- First one, nat-int-network (192.168.1.0/24), connected to WinXP guest (single network adapter within guest) hangs rarely - 1-2 times per month. 

- Second one, nat-int-network-2 (192.168.2.0/24), connected to Windows Server 2012 Guest (one of two network adapters within guest, second one is openvpn tap0 interface attached to guest as Bridged Adapter) and hangs more often - 1-2 times per day... sometime 1 time per 2-3 days...

Windows Server guest is a loaded by 5-10 simultaneous RDP-sessions, but average load is quite moderate... 

I understand that info provied is not enough.
Please, let me know - what kind of details should I add to?",dtgeorge
20361,vboxnet0 not working on startup,VirtualBox 6.1.22,Mac OS X,2021-05-12T15:55:22Z,2021-05-12T15:55:22Z,2021-05-12T15:55:22Z,"When I boot up, vboxnet0 isn't created which means other tools that depend on it (i.e. gns3) can't start up and load virtualbox.

I've set virtualbox to start on login, which solves that problem, but now I have the issue whereby the interface is created without an IP address.

I have to go into virtualbox network settings and change the vboxnet0 IP address in order for an IP address to be created.

A secondary effect of this is that the UI isn't updated until Virtualbox restarts, so if you change the vboxnet0 address to something else (i.e. 192.168.56.2/24), ifconfig shows it correctly but the UI reverts to the previous state (i.e. 192.168.56.1/24). This means that you can't then revert to that address without restarting virtualbox. 

This is on macos 11.3 and 11.3.1.",craigmcfly
20379,6.1.18 to 6.1.20 Intel pro/1000 changes,VirtualBox 6.1.20,Windows,2021-05-25T12:45:54Z,2021-05-30T09:54:08Z,2021-05-30T09:54:08Z,"Hello,

Current Menuet64 network driver (bridged) for i8254x works fine with 
VirtualBox 6.1.18, but not anymore with 6.1.20.

I've read from previous tickets that for example the 
RDT register and interrupts are handled differently in 6.1.20.

So could you provide some (bit-level) details about the RDT 
register (and possibly other) changes, so I can debug the driver here ?

Thank you.
",AndrewMC
20392,TCP reset on 50% of http POST,VirtualBox 6.1.22,Mac OS X,2021-06-10T14:33:15Z,2021-06-17T01:09:55Z,2021-06-17T01:09:55Z,"Since MacOS Big sur I get about 50% TCP reset's. This can be reproduced with curl:

{{{
$ curl  -d '{""request"": ""query""}' -H ""Content-Type: application/json"" -X POST http://local_network_host:21573/ >/dev/null
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
100 14668    0 14648  100    20   133k    186 --:--:-- --:--:-- --:--:--  133k
$ curl  -d '{""request"": ""query""}' -H ""Content-Type: application/json"" -X POST http://routingtestb:21573/ >/dev/null
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
100 14668    0 14648  100    20   133k    186 --:--:-- --:--:-- --:--:--  133k
curl: (56) Recv failure: Connection reset by peer
}}}


I'm not able to reproduce with a public host yet. I can provide a pcap but prefer not to make it public.

Tried:
- Only NAT network. Did not try bridge.
- Tried various adapter types.
- Multiple hosts have same issue.
- Different guests have the same issue. (Windows / Linux)

",Pieter1234
20419,NAT Port Forwarding CONN RESET ISSUES,VirtualBox 6.1.22,Windows,2021-06-16T17:42:24Z,2021-06-19T04:56:49Z,2021-06-19T04:56:49Z,"Trying to port forward port 10000-10002 between the 
windows 10 pro host OS
windows 10 enterprise guest OS

on those ports the guest contains the microsoft azure storage emulator endpoints.

I am trying to make REST API call to those endpoints from the host OS will no sucess.

So far, I have turned off the windows defender firewall in the Guest OS  and allowed for the TCP,UDP inbound outbound connections on the HOST OS. I also upgraded my VM FROM 6.1.18-142142 TO 6.1.22-144080.This happend for browser, web app API, python and C#. We know this is the case becuase the API call to MySQL on guest 3306 works sucesfully and on turning off the guest OS, the failed call indicated the MySQL server was only on the guest

The results were from a HTTP Requests that hangs to a requests that respond ""CONNECTION RESET"", this happend on both versions of virtual box
",windmillcode
20429,System crash on Windows 10 host when using vbox network adapter together with Windows 10 networking bridging feature,VirtualBox 6.1.18,Windows,2021-06-25T04:36:09Z,2021-06-25T04:36:09Z,2021-06-25T04:36:09Z,"Steps to reproduce the issue:

1) Install vbox on a Windows 10 device
2) Make sure to also enable the vbox network adapter
3) Set physical network adapter within the Windows 10 network settings to bridge mode (Control Panel\Network and Internet\Network Connections -> right click network connection -> bridge connection)
4) Leave device running as normal. In my case, the crashes seemed to happen fairly consistently after roughly 14 hours of system uptime, give or take a few hours.

Unfortunately my system settings were set to full crash dumps and not minidumps, so the full dump is likely too large to upload here. However, I will paste the information the Windows debugger was able to extract from my crash dump here:

SYSTEM_THREAD_EXCEPTION_NOT_HANDLED (7e)
This is a very common bugcheck.  Usually the exception address pinpoints
the driver/function that caused the problem.  Always note this address
as well as the link date of the driver/image that contains this address.
Arguments:
Arg1: ffffffffc0000005, The exception code that was not handled
Arg2: fffff8027f4580c3, The address that the exception occurred at
Arg3: fffffe8c1f2a2ab8, Exception Record Address
Arg4: ffffa400c67f5920, Context Record Address

Debugging Details:
------------------


KEY_VALUES_STRING: 1

    Key  : AV.Fault
    Value: Read

    Key  : Analysis.CPU.Sec
    Value: 2

    Key  : Analysis.DebugAnalysisProvider.CPP
    Value: Create: 8007007e on DESKTOP-INRFD0B

    Key  : Analysis.DebugData
    Value: CreateObject

    Key  : Analysis.DebugModel
    Value: CreateObject

    Key  : Analysis.Elapsed.Sec
    Value: 4

    Key  : Analysis.Memory.CommitPeak.Mb
    Value: 73

    Key  : Analysis.System
    Value: CreateObject


BUGCHECK_CODE:  7e

BUGCHECK_P1: ffffffffc0000005

BUGCHECK_P2: fffff8027f4580c3

BUGCHECK_P3: fffffe8c1f2a2ab8

BUGCHECK_P4: ffffa400c67f5920

EXCEPTION_RECORD:  fffffe8c1f2a2ab8 -- (.exr 0xfffffe8c1f2a2ab8)
ExceptionAddress: fffff8027f4580c3 (bridge+0x00000000000080c3)
   ExceptionCode: c0000005 (Access violation)
  ExceptionFlags: 00000000
NumberParameters: 2
   Parameter[0]: 0000000000000000
   Parameter[1]: ffffffffffffffff
Attempt to read from address ffffffffffffffff

CONTEXT:  ffffa400c67f5920 -- (.cxr 0xffffa400c67f5920)
rax=0000000000000000 rbx=0000000000000000 rcx=b2a29e05584ac880
rdx=0000000000000000 rsi=ffffb8880f8ee2c0 rdi=ffffb888098a48e0
rip=fffff8027f4580c3 rsp=fffffe8c1f2a2cf0 rbp=fffffe8c1f2a2e00
 r8=0000000000000001  r9=0000000000000001 r10=0000000000000002
r11=fffffe8c1f2a2b90 r12=0000000000000000 r13=0000000000000000
r14=ffffb8880f8ee4f0 r15=0000000000000000
iopl=0         nv up ei ng nz na pe nc
cs=0010  ss=0000  ds=002b  es=002b  fs=0053  gs=002b             efl=00010282
bridge+0x80c3:
fffff802`7f4580c3 488b4918        mov     rcx,qword ptr [rcx+18h] ds:002b:b2a29e05`584ac898=????????????????
Resetting default scope

BLACKBOXBSD: 1 (!blackboxbsd)


BLACKBOXNTFS: 1 (!blackboxntfs)


BLACKBOXPNP: 1 (!blackboxpnp)


BLACKBOXWINLOGON: 1

PROCESS_NAME:  System

READ_ADDRESS:  ffffffffffffffff 

ERROR_CODE: (NTSTATUS) 0xc0000005 - The instruction at 0x%p referenced memory at 0x%p. The memory could not be %s.

EXCEPTION_CODE_STR:  c0000005

EXCEPTION_PARAMETER1:  0000000000000000

EXCEPTION_PARAMETER2:  ffffffffffffffff

EXCEPTION_STR:  0xc0000005

BAD_STACK_POINTER:  ffffa400c67f50e8

STACK_TEXT:  
fffffe8c`1f2a2cf0 fffff802`7f458786 : 00000094`00000000 00000000`00000003 fffffe8c`1f2a2e80 00000000`00000003 : bridge+0x80c3
fffffe8c`1f2a2d80 fffff802`674f53b5 : ffffb888`08528040 ffffb888`08528040 fffff802`7f458550 00000000`00000003 : bridge+0x8786
fffffe8c`1f2a3c10 fffff802`675fe278 : ffffa400`c67b3180 ffffb888`08528040 fffff802`674f5360 00000000`00000000 : nt!PspSystemThreadStartup+0x55
fffffe8c`1f2a3c60 00000000`00000000 : fffffe8c`1f2a4000 fffffe8c`1f29e000 00000000`00000000 00000000`00000000 : nt!KiStartSystemThread+0x28


SYMBOL_NAME:  bridge+80c3

MODULE_NAME: bridge

IMAGE_NAME:  bridge.sys

STACK_COMMAND:  .cxr 0xffffa400c67f5920 ; kb

BUCKET_ID_FUNC_OFFSET:  80c3

FAILURE_BUCKET_ID:  AV_STACKPTR_ERROR_bridge!unknown_function

OS_VERSION:  10.0.19041.1

BUILDLAB_STR:  vb_release

OSPLATFORM_TYPE:  x64

OSNAME:  Windows 10

FAILURE_ID_HASH:  {7c978e5a-5f78-1ec3-8e3c-e245486b5eda}

Followup:     MachineOwner
---------
",Andazeus
20451,Bridged adapter list is empty (with NDIS5 drivers),VirtualBox 6.1.22,Windows,2021-07-09T10:35:18Z,2021-07-09T10:35:18Z,2021-07-09T10:35:18Z,"As a workaround for #15060 I tried installing VirtualBox using the old NDIS 5 network drivers, by running the installer with the option `-msiparams NETWORKTYPE=NDIS5`

After installation, attempting to configure a bridged network interface is impossible because the list of adapters to bridge to is empty (see attached screenshot).

There are no other error messages from VirtualBox about a the failure to enumerate network adapters. It looks like the NDIS5 drivers are active, given...

{{{
PS > get-windowsdriver -online | Where-Object -property ProviderName -Like *oracle* | format-list

Driver           : oem16.inf
OriginalFileName : C:\Windows\System32\DriverStore\FileRepository\vboxnetadp.inf_amd64_a4e9db3f071a0883\vboxnetadp.inf
Inbox            : False
ClassName        : Net
BootCritical     : False
ProviderName     : Oracle Corporation
Date             : 28/04/2021 00:00:00
Version          : 6.1.22.44080

Driver           : oem22.inf
OriginalFileName : C:\Windows\System32\DriverStore\FileRepository\vboxnetflt.inf_amd64_1ca009f9c76e42da\vboxnetflt.inf
Inbox            : False
ClassName        : NetService
BootCritical     : False
ProviderName     : Oracle Corporation
Date             : 28/04/2021 00:00:00
Version          : 6.1.22.44080

Driver           : oem56.inf
OriginalFileName : C:\Windows\System32\DriverStore\FileRepository\vboxnetfltm.inf_amd64_4f271f5e54b849f3\vboxnetfltm.inf
Inbox            : False
ClassName        : Net
BootCritical     : False
ProviderName     : Oracle Corporation
Date             : 28/04/2021 00:00:00
Version          : 6.1.22.44080

Driver           : oem9.inf
OriginalFileName : C:\Windows\System32\DriverStore\FileRepository\vboxusb.inf_amd64_721cfc8f354e0c0c\vboxusb.inf
Inbox            : False
ClassName        : USB
BootCritical     : True
ProviderName     : Oracle Corporation
Date             : 28/04/2021 00:00:00
Version          : 6.1.22.44080
}}}
",Sam Morris
20460,host freeze in bridge network mode,VirtualBox 6.1.22,other,2021-07-15T23:54:29Z,2021-07-15T23:56:14Z,2021-07-15T23:56:14Z,"I used to use bridge network mode with no issues... but now with my new laptop I faced this issue immediately after start up any host with bridge network mode 


in NAT everything is fine

I'm wondering it's because of wifi card 

",mohdforever
20470,Enabled VB Host Only Network adapter causes Internet Connection Icon to show No Internet on Windows 10,VirtualBox 6.1.24,Windows,2021-07-23T08:26:45Z,2021-07-23T08:31:45Z,2021-07-23T08:31:45Z,"When having VirtualBox Host Only Network adapter enabled across reboots on Windows 10, the Internet Connection Icon soon (time varies somewhat) starts to show no internet connection even though the internet connection works correctly.

Took me some time to find out that the adapter was the cause for this problem. Now I always disable the adapter before rebooting.",loxia_01
20462,VBoxNetLwf and EventID 12 on Windows,VirtualBox 6.1.22,Windows,2021-07-18T05:33:59Z,2021-07-29T11:04:38Z,2021-07-29T11:04:38Z,"I am aware that this has been posted already but I cannot find an open ticket! In reference to:
https://forums.virtualbox.org/viewtopic.php?f=6&t=87971
I would like to mention that all solutions are not working and the issue is permanent:

Randomly, the VBoxNetLwf driver crashes and causes an event log entry with ID 12. Unfortunately this also causes the WiFi connection to disconnect and it takes some time until Windows recovers internet connection.

I've attached two of these log entries in a file.

Is there anything that can be done about it? Is there already any knowledge when this happens and where (in the source code) this issue occurs? I also read it maybe related to energy management. But I doubt that since it happens for me also when I am actively working on the computer e.g. connected to a remote machine via VPN (which gets disconnected in that case, obviously).",Slimfast
5747,Bridged Networking on Ethernet and Wireless Bonded interface fails,VirtualBox 3.1.0,Linux,2009-12-14T04:44:54Z,2021-08-11T16:19:10Z,2021-08-11T16:19:10Z,"I am using bonding to enslave eth0 and wlan0 together on a Debian Linux Host.

if the ethernet interface is operating and is the primary (which is what I have as default) the Guest is able to access the network.  if the the wireless interface if the primary the guest cannot access the network.

using NAT works but I need to use a PPTP VPN from the guest but Virtualbox does not support GRE via NAT setup.

My network interfaces looks like this on the host to setup bonding between the wireless and ethernet.


# The loopback network interface[[BR]]
auto lo[[BR]]
iface lo inet loopback[[BR]]
[[BR]]
# Bonding interface[[BR]]
auto bond0[[BR]]
iface bond0 inet dhcp[[BR]]
  bond_mode active-backup[[BR]]
  bond_primary eth0[[BR]]
  bond_miimon 100[[BR]]
  bond_downdelay 200[[BR]]
  bond_updelay 200[[BR]]
  wpa-ssid wifi[[BR]]
  wpa-ap-scan 1[[BR]]
  wpa-psk password[[BR]]
  wpa-scan-ssid 1[[BR]]
  wpa-iface wlan0[[BR]]
  slaves eth0 wlan0[[BR]]",James Robertson
20514,Networking is not functional under OPENSTEP 4.2/Mach for Intel,VirtualBox 6.1.26,other,2021-08-20T03:26:00Z,2021-09-02T11:21:01Z,2021-09-02T11:21:01Z,"Being the lead developer of GNUstep it is sometimes useful to have OPENSTEP on hand.  Recently I installed OPENSTEP on virtualbox 6.1.97 (not sure why this is not listed in the versions dropdown).   The AMD PCNet 32 adapter which VirtualBox presents is detected, but it is not usable.   Oddly, under VMware it is useable but VMware doesn't support VESA display modes so networking works, but little else does on VMware.

The files you will need to install OPENSTEP are here...

https://openstep.bfx.re/

I would prefer to keep using VirtualBox as it is open source.  Please see if you guys can fix this. I have not tried 6.1.26, but I am certain it is not functioning there either.",GNUstepLeadDev
20533,Network card error after deleting Virtual Machine,VirtualBox 6.1.26,Windows,2021-09-03T10:51:19Z,2021-09-03T14:34:08Z,2021-09-03T14:34:08Z,"Hi,

As I wrote in the summary, after removing a VM from VirtualBox I can not change my network properties in the host for all networks cards I have.

I'm hosting from a Windows PC with Windows 10 Pro.

The error appears after removing a Debian VM. Just to notice it did the same issue with a CentOS VM, and to go back to normal it was necessary to execute a factory reset on my PC.

Also it is not possible to desactivate or reactivate the connection.

My computer is my principal tool to work and I frequently use this parameters.

Thanks for any help and solution. ",ddag
14374,Network adapters not working after host returns from sleep Win 7 host Linux Mint 17.2 guest,VirtualBox 5.0.0,Windows,2015-08-02T17:02:25Z,2021-09-09T03:59:02Z,2021-09-09T03:59:02Z,"Host is Dell E7440 laptop running Windows 7 SP1 Enterprise 64 bit. VirtualBox version 5.0.0 r101573. Wireless NIC is Intel Dual Band AC 7260 as a bridged adapter virtualized as Intel PRO 1000 MT desktop. Guest is ""Linux Mint 17.2 Rafaela built on Ubuntu 14.04.2 LTS Trusty Tahr and kernel is 3.13.0-37-generic. The guest additions have been installed

Issue started appearing after the 5.0 update recently. After my host has returned from sleep my network connection is lost on my guest until i completely shutdown. I have tried switching the host adapter to other adapters. Disconnecting and reconnecting the cable in Devices>Network Settings. I have also tried just rebooting. The VM has to be completely powered off and back on for the adapter to work again. The network connection icon in the task bar stays discontented the entire time. No error message is given at any time.",Johnny Kilo
20547,Promiscuous Mode Does Not Work on macOS 11.5.2,VirtualBox 6.1.26,Mac OS X,2021-09-14T05:03:41Z,2021-09-16T15:26:56Z,2021-09-16T15:26:56Z,"Regardless of the network adapter type and other settings, selecting Bridge Adapter and either Allow VMs or Allow All for the Promiscuous Mode does not provide the expected result. Linux VMs have no issues passing network traffic normally, but if a bridge is setup incoming packets do not reach the VM. I see the packets generated on the VirtualBox Guest VM and nested VMs on the VM interfaces, the Mac, and my router, but the return traffic does not make it to the VirtualBox Guest VMs. I found the following ticket that has gone ignored for many years with some information that may help isolate the issue.

https://www.virtualbox.org/ticket/10811

This also fails running VirtualBox as root.

I can say that I'm able to enable Promiscuous Mode in other software without issue, so the issue is not macOS or my setup.

Given that this issue is quite old, my guess is we have one of two issues since some change in an old macOS and every release since. It's broken or there are added steps to make it work.

If you're not going to support Promiscuous Mode, then please remove the options so people don't waste time troubleshooting something that is not going to work.

If more setup is required to make this work with VirtualBox, then please provide the documentation necessary.",Myrddyn
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
20589,"NAT TFTP: leading slash in path cause ""Access violation""",VirtualBox 6.1.26,Windows,2021-10-01T18:22:50Z,2021-10-05T20:34:25Z,2021-10-05T20:34:25Z,"I was trying to boot Grub2 using the built-in NAT TFTP. However, after being successfully loaded by iPXE Grub fails to load the additional files (/boot/grub/i386-pc/normal.mod, etc.) printing: error: Access violation

Same error is returned by NAT TFTP when using a tftp client on a booted Gust OS when the requested path has a leading forward slash.

Workaround: switch to an alternative TFTP server on localhost:
{{{
VBoxManage modifyvm SLESInst --nattftpserver1 10.0.2.2
}}}
Steps to reproduce:

- Generate Grub dir without grub.cfg or vmlinuz/initrd (they're not needed for testing)
{{{
[root@reallin il]# grub-mknetdir --net-directory=/srv/tftp --subdir=/boot/grub -d /usr/lib/grub/i386-pc
Netboot directory for i386-pc created. Configure your DHCP server to point to /srv/tftp/boot/grub/i386-pc/core.0
}}}
- Copy the files to the default TFTPPrefix
{{{
cp -rT /srv/tftp/boot ~/.VirtualBox/TFTP/boot
}}}
- point the VBox DHCP server to the right file
{{{
# If I use leading slash here boot fails sooner
VBoxManage modifyvm MyVM --nattftpfile1=boot/grub/i386-pc/core.0
}}}
- Boot a guest from Network

Expected: Grub loads in ""Normal"" mode

Actual: Grub loads in ""Rescue"" mode.

Additional info:
{{{
[il@reallin ~]$ atftp 10.0.2.4
tftp> get boot/grub/i386-pc/core.0
Overwrite local file [y/n]? y
tftp> get /boot/grub/i386-pc/core.0
Overwrite local file [y/n]? y
tftp: error received from server <Access violation>
tftp: aborting
tftp> 
}}} 
",lfmeloman
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
20669,Multicast originating from different subnet does not reach Guest only on Ubuntu(Linux?) Host,VirtualBox 6.1.28,Linux,2021-11-15T17:07:49Z,2021-11-17T19:07:55Z,2021-11-17T19:07:55Z,"Hello,

I have run into an issue that I now believe is a bug.

Basically, I am receiving status updates from various devices on the network in my VM. They use multicast on 224.0.0.50.
The devices are on a different subnet from the Host and the Guest (the host and the guest are on the same subnet), but everyone can communicate between each other just fine.
This works on Host Windows 10 but not on Host Ubuntu 18.04. 
Using Virtualbox 6.1.28. 

Also, tried:
- 6.1.26
- 6.1.29 revision 148164 test build
- 6.1.97 development revision 148162

All the above w/ extpack

The guest is using bridged networking.
On Windows it's using Intel PRO/1000 MT Desktop (82540EM). 
On the Ubuntu host I've tried them all with no luck.
On Windows promiscuous mode is set to Deny and greyed out, on the Ubuntu host I tried enabling it to Allow-All, no luck.

Both hosts receive the multicast packet (used wireshark on windows and tcpdump on linux to verify on both the hosts and the guests), but only on the Windows 10 host will it manage to be picked up by the Guest.
I'm attaching a screenshot from a packet capture from inside the Guest with Windows 10 as a host. These two packets are the expected behavior. On Ubuntu Host, only the first one (the direct reply) makes it all the way to the Guest. The multicast packet is lost.

It is worth mentioning that it's the exact same VM copied from Windows to Linux to make this test as good as possible.

Multicast packets originating from the same subnet are well-received.
I also tried mimicking network routes on the Ubuntu host as seen on the Windows host but to no avail.
I tried nuking the routes on the windows host to see if it affected the Windows Guest receiving it but it did not.
",idmistir
20715,"VirtualBox 6.1.30: ""vboxmanage natnetwork"" lacks of options to set IPv6 prefix and enable/disable router advertisements",VirtualBox 6.1.30,other,2021-12-03T18:14:14Z,2021-12-03T18:14:14Z,2021-12-03T18:14:14Z,"VirtualBox 6.1.30: ""vboxmanage natnetwork"" lacks of options to set IPv6 prefix and enable/disable router advertisements.

Example:
vboxmanage natnetwork add --netname ISP-Alpha \
   --network 172.31.255.0/24 \
   --enable \
   --dhcp no \
   --ipv6 yes

""--network"" only allows to configure the IPv4 network. There is no corresponding option for IPv6. It is only possible to turn IPv6 on/off, and the prefix gets configured automatically. Documentation about how the IPv6 prefix is computed is missing! (And there is a bug in this automatic configuration as well: https://www.virtualbox.org/ticket/20714)

DHCP can be enabled with ""--dhcp"", but there is no option to turn on ICMPv6 router advertisements and/or DHCPv6.",Thomas Dreibholz
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
15438,Guest can't access host network after resume from hibernation (hybrid sleep).,VirtualBox 5.0.20,Windows,2016-05-23T13:05:56Z,2022-01-18T05:02:12Z,2022-01-18T05:02:12Z,"Host : Windows Server 2008 R2 SP1.[[BR]]
Guest : 64-bit Arch Linux with kernel 4.5.4-1-ARCH.[[BR]]
Network : Bridged with host network card (VirtualBox NDIS6 Bridged Networking Driver).[[BR]]

After resume from hibernation, guest can't access host network. No ping packets reach host. Rebooting guest doesn't help. Only totally powering off and then turning it on helps and guest can access host again.

Maybe related to bug ticket [https://www.virtualbox.org/ticket/14457]",hotjava1231
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
20778,Game crashing when VirtualBox Host-Only Adapter is present and enabled,VirtualBox 6.1.32,Windows,2022-01-19T19:05:56Z,2022-01-21T23:19:25Z,2022-01-21T23:19:25Z,"The game XIII from GoG crashes on startup when the VirtualBox Host-Only adapter is installed and enabled.  This is 100% reproducible on my system, and has been confirmed on another system.  The game is installed and running on the host, not VirtualBox.  VirtualBox doesn't have to be running for the crash to occur.

When the game starts, it apparently enumerates all of the active network adapters and attempts to check something on each one.  The response from the VirtualBox Host-Only Adapter results in the game crashing.

This was determined by launching the game in a debugger and stepping backward from the crash with time-travel debugging.  The code just before the crash was making network related calls.

I don't know if this is a defect in the game, or a defect in the adapter, just that disabling the adapter fixes the problem, and enabling it causes the issue to return.",g051051
20799,Duplicate packages in the guest OS when bridging to the LACP adapter in Windows,VirtualBox 6.1.32,Windows,2022-01-31T16:13:58Z,2022-01-31T17:17:23Z,2022-01-31T17:17:23Z,"In VirtualBox version 6.1.32, when using a bridge to the LACP adapter in Windows Server 2012 R2, duplicate packages appear in the guest OS.

Tested on Debian 11 using ping.



The host PC running Windows Server 2012 R2 is connected to the router via a Zyxel GS1900-8 switch using the LACP protocol via 2 Intel I350 NICs.
If you send a ping from any guest OS, for example, to a router, then several packets will be returned in response - 1 + 3 duplicates.
At the same time, there is an increase in the load on the CPU and RAM of both the guest OS and the host OS, respectively.





Previous versions of VirtualBox did not have this problem, including 6.1.30.

The versions of the expansion packs used were the corresponding versions of VirtualBox.



VMware Workstation had the same problem for a long time, and now it has reached VirtualBox. :(

I tested this effect earlier in VMware Workstation Pro 16 with Linux and Windows guest OS - the result is the same, there are duplicates.",Konstantin.P
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
20717,networking is dropped on Linux guests under Monterey,VirtualBox 6.1.30,Mac OS X,2021-12-07T17:54:39Z,2022-02-16T04:17:42Z,2022-02-16T04:17:42Z,"Under Monterey, I'm seeing this behavior where when starting a virtual Linux guest in bridged mode some of the time, the system can't talk to the Ethernet to obtain a DHCP address. 

Windows guests don't appear to be affected. NAT mode is not affected at all. ",mauricev1
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
20833,Linux Guest VM Crashes If Bridged Network Is Selected,VirtualBox 6.1.32,Windows,2022-02-18T04:15:58Z,2022-02-18T04:15:58Z,2022-02-18T04:15:58Z,"I just installed VB onto my Windows 10 PC and tried to install Oracle Linux 8 onto it.  If Bridged Network is selected, the VM crashes.",jawale
20838,Discovered 2 vulnerabilities in VirtualBox,VirtualBox 6.1.32,other,2022-02-22T19:08:52Z,2022-02-23T19:58:31Z,2022-02-23T19:58:31Z,"Hi, 
In the last couple of months I discovered 2 vulnerabilities in E1000 emulated device. I disclose it to you in order to fix them.
I provide a zip file which contains a README.md file, which is highly documented description of the vulnerabilities. It also describes other files in the zip file. I will be happy to be in touch with you to help you resolve this issues. In addition, I would be happy if you can create a CVE number for each one of these vulnerabilities. 

Thank you and hope to hear from you soon,
Adi

e1000_vulnerabilites.zip: md5 
",nick1
20943,Latest Win 11 updates causing total fault of Virtualbox ver.6.1.34,VirtualBox 6.1.34,Windows,2022-05-15T06:06:30Z,2022-05-15T06:06:30Z,2022-05-15T06:06:30Z,"Environment: PC HP EliteDesk 800 G8 Tower PC
Processor	11th Gen Intel(R) Core(TM) i7-11700 @ 2.50GHz   2.50 GHz
Installed RAM	16,0 GB (15,7 GB usable)
System type	64-bit operating system, x64-based processor

OS Windows 11 (upgrade from Win 10 on day of first installation 11-04-2022)
Edition	Windows 11 Pro
Version	21H2
Installed on	‎11/‎04/‎2022
OS build	22000.593
Experience	Windows Feature Experience Pack 1000.22000.593.0

Network private IP 192.168.0.x
Network Adapter Intel Ethernet Connection (14) I219-LM

VirtualBox Oracle ver.6.1.34
with Bridged Adapter attached to Intel Ethernet Connection (14) I219-LM
Adapter Type Intel PRO/1000 MT Desktop (82540EM)

Total fault description:

After start of VM (Debian10 iso image) in early starting phase entire process stoped with VM total failure. 
Until 26-04-2022 (before Win11 update) was this VM running without any problem as well as several other Debian 8, 9, 10 VMs.
After updates on 26-04-2022 with:
Cumulative Update for Windows 11 for x64-based Systems (KB5012643)
Cumulative Update for Windows 11 for x64-based Systems (KB5012592)
total fault appears as
collision in net drivers - VirtualBox Host-Only Ethernet Adapter) Cumulative Update for Windows 11 for x64-based Systems (KB5012643) 

After uninstall of updates the VM is working without any problem.

Supposed fault source:
VirtualBox driver 'Host-Only Ethernet Adapter' is unable to run with newest Win 11 updates.

Remarks: 
When fault occurs I done plenty of tests with different VirtualBox Network settings (NAT,..) and Intel drivers but no solution found. Only uninstall of latest Win updates allowed fault-free run. 
New updates of Win11 published in May 2022 are causing the same problem with VirtualBox.",jotcomponents
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
20994,PXE UNDI driver transmit seems to be mapping existing transmit buffer instead of making a copy,VirtualBox 6.1.34,Linux,2022-06-19T04:07:03Z,2022-06-19T04:07:03Z,2022-06-19T04:07:03Z,"To be fair, haven't dug that far into VirtualBox code (don't really use SVN, and don't have an easy web interface to search the code for what I'm looking for) but, the most recent code I could find on GitHub for VBox seems to suggest it's mapping the supplied transmit buffer and not copying it before return: https://github.com/TedHartDavis/VBoxMirror/blob/3d7f37ab5b248566e1dc17df8ee495628bb007e5/src/VBox/Devices/EFI/FirmwareNew/OptionRomPkg/UndiRuntimeDxe/Decode.c#L1214, https://github.com/TedHartDavis/VBoxMirror/blob/3d7f37ab5b248566e1dc17df8ee495628bb007e5/src/VBox/Devices/EFI/Firmware/OptionRomPkg/UndiRuntimeDxe/E100b.c#L1100

Given that, I'm currently the following behavior running GRUB in VirtualBox and it sending DNS:

1. GRUB (2.06) allocates a single, fixed scratch-space buffer for sending packets via PXE UNDI; this buffer is reused for every packet send. (See https://github.com/rhboot/grub2/blob/ef36b3c93d27bdfc7a68469be33bd8be95630e6a/grub-core/net/drivers/i386/pc/pxe.c#L259)
2. When running in VirtualBox, I can get GRUB to send DNS requests manually with the net_nslookup command.
3. When GRUB is in prefer-ipv4 mode (default), it tries to send one A DNS request followed by an IPv6 AAAA request.
4. Looking in Wireshark, I can see it just sending two AAAA requests instead (seems like the AAAA query contents are somehow clobbering the A query), separated by about 0.2ms.
5. When I set debug=dns in GRUB, the delay of debug-print-to-console seems to introduce enough delay that I see separate A and AAAA requests in Wireshark (now separated by about 1ms).

The best explanation I have for these observations is that VirtualBox's UNDI/PXE implementation is not mixing well with GRUB's extreme transmit buffer reuse, and causing a sufficiently quick sequence of transmits to clobber previous packets' contents.

I'm not that familiar with PXE or UNDI API requirements, but it seems like the driver should not return without at least making a copy of the data buffer, even if it doesn't transmit the packet immediately? In any case, would hope someone can take a look at the spec and determine whether this is actually a bug on VirtualBox's side or GRUB's.

Thanks in advance!",henryptung
21006,DHCP provides wrong DNS server address if DNS server address is not requested,VirtualBox 6.1.34,other,2022-06-23T13:15:35Z,2022-06-23T13:15:35Z,2022-06-23T13:15:35Z,"VirtualBox 6.1 on Fedora Linux with NAT networking:

If the DHCP client in the VM does not provide option 55 -  Parameter Request List - or does provide one, but does not provide Item 6 - Domain Name Sever - in DCHDISCOVER, then the VirtualBox builtin DHCP server will respond with a DHCPOFFER containing a DNS Sever option, anyway.

But the address specified in this option will be invalid. More specifically, instead of providing 10.0.2.3, it will provide whatever is in /etc/hosts. This may go unnoticed if the DNS sever listed in /etc/hosts has a routable address.

On a Fedora Linux the DNS server in /etc/hosts has the address 127.0.0.53, which is not routable and as such when the VM tries to talk to it, it fails (it has no such local address configured).

Interestingly, if I manually configure the DNS server address in the guest OS to 10.0.2.3, the VirtualBox DNS server does not respond on that address.

I can reproduce this on HelenOS as of Git revision 52214a2d97559c2396ecbcd3de80863dab438fb3. Unfortunately this cannot be tested with a binary release (e.g. the latest, HelenOS 0.11.2) as it misses a fix for another problem that HelenOS DHCP has in VirtualBox.
",JiriS
20996,No guest connection with bridged adapter,VirtualBox 6.1.34,Mac OS X,2022-06-20T14:41:41Z,2022-06-24T17:02:33Z,2022-06-24T17:02:33Z,"I recently upgraded my iMac to Monterey 12.4 and updated VBox to 6.1.14.

I've noticed that I'm not able to connect a Linux guest I had running in Catalina with a bridged adapter. It seems to try to connect but it doesn't work at all. (I tried to change the adapter too and MAC address but no success so far.)

NAT with port-forwarding works well.",rpijoan_lsw
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
21062,BUG in updating Nat Network configuration: parameter Network CIDR,VirtualBox 6.1.36,Linux,2022-08-14T19:28:06Z,2022-08-14T19:28:06Z,2022-08-14T19:28:06Z,"Changing the parameter Network CIDR does not affect the correct configuration of the DHCP server active on the NAT network.
The IP address of the DHCP server and the range of addresses served are not updated.

For the walkthrough see my post on Forum

https://forums.virtualbox.org/viewtopic.php?f=7&t=106799 ",sagypt
21075,Bridged network doesn't work on WiFi interface on Ubuntu jammy with kernel 5.15.0-46,VirtualBox 6.1.36,Linux,2022-08-24T08:30:11Z,2022-08-24T08:30:11Z,2022-08-24T08:30:11Z,"Upon upgrading to jammy and using latest kernel 5.15.0-46 the bridged networking on WiFi interface stopped working - host (Windows 10 ENT 64bit). It works fine if I manually switch to 5.13.0-52 kernel.

The difference I spotted is when I list interfaces is that the WiFi is listed as not WiFi:

{{{
vboxmanage list bridgedifs
Name:            wlp3s0
GUID:            33706c77-3073-4000-8000-340286543f76
DHCP:            Disabled
IPAddress:       192.168.1.9
NetworkMask:     255.255.255.0
IPV6Address:     fe80::2421:bd44:a0a3:b042
IPV6NetworkMaskPrefixLength: 64
HardwareAddress: 34:02:86:54:3f:76
MediumType:      Ethernet
Wireless:        No
Status:          Up
VBoxNetworkName: HostInterfaceNetworking-wlp3s0

Name:            enp0s25
GUID:            30706e65-3273-4035-8000-68f7289e3ac5
DHCP:            Disabled
IPAddress:       0.0.0.0
NetworkMask:     0.0.0.0
IPV6Address:     
IPV6NetworkMaskPrefixLength: 0
HardwareAddress: 68:f7:28:9e:3a:c5
MediumType:      Ethernet
Wireless:        No
Status:          Up
VBoxNetworkName: HostInterfaceNetworking-enp0s25
}}}
",rskolnik
21076,virtual box 6.34 fail host only adapter after deleting network adapters in windows 10,VirtualBox 6.1.34,Windows,2022-08-25T14:16:03Z,2022-08-25T14:16:03Z,2022-08-25T14:16:03Z,virtual box 6.34 fail host only adapter after deleting network adapters in windows 10,ignasi
15060,Can't start virtual machine with bridged interfaces,VirtualBox 5.0.14,Windows,2016-01-21T12:37:02Z,2022-09-28T19:15:41Z,2022-09-28T19:15:41Z,"When resuming a saved virtual machine, I get the message:

{{{
Failed to open/create the internal network 'HostInterfaceNetworking-Realtek PCIe GBE Family Controller' (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 is on Windows 10.0.10586, but didn't start when upgrading to this version... I've been using Virtualbox fine for the last couple of weeks until this morning.

I did some searching and it seems that others were able to resolve the same issue by enabling the 'VirtualBox NDIS6 Bridged Networking Driver' for their network adapters, but I checked each adapter and it's already enabled for them all.

The virtual machine logs contain:

{{{
00:00:03.187772 IntNet#0: szNetwork={HostInterfaceNetworking-Realtek PCIe GBE Family Controller} enmTrunkType=3 szTrunk={\DEVICE\{CA0A5FEA-99B8-4F54-89CC-C3F81004A5FF}} fFlags=0x14000 cbRecv=325632 cbSend=196608 fIgnoreConnectFailure=false
00:00:03.187821 VMSetError: F:\tinderbox\win-5.0\src\VBox\Devices\Network\DrvIntNet.cpp(1753) int __cdecl drvR3IntNetConstruct(struct PDMDRVINS *,struct CFGMNODE *,unsigned int); rc=VERR_INTNET_FLT_IF_NOT_FOUND
00:00:03.187846 VMSetError: Failed to open/create the internal network 'HostInterfaceNetworking-Realtek PCIe GBE Family Controller'
00:00:03.187879 VMSetError: F:\tinderbox\win-5.0\src\VBox\Devices\Network\DevE1000.cpp(7715) int __cdecl e1kR3Construct(struct PDMDEVINS *,int,struct CFGMNODE *); rc=VERR_INTNET_FLT_IF_NOT_FOUND
00:00:03.187883 VMSetError: Failed to attach the network LUN
00:00:03.187893 PDM: Failed to construct 'e1000'/0! VERR_INTNET_FLT_IF_NOT_FOUND (-3600) - The networking interface to filter was not found.
00:00:03.190010 AIOMgr: Preparing flush failed with VERR_NOT_SUPPORTED, disabling async flushes
00:00:03.197890 AIOMgr: Preparing flush failed with VERR_NOT_SUPPORTED, disabling async flushes
00:00:03.204536 AIOMgr: Preparing flush failed with VERR_NOT_SUPPORTED, disabling async flushes
00:00:03.211773 GIM: KVM: Resetting MSRs
00:00:03.341518 ERROR [COM]: aRC=E_FAIL (0x80004005) aIID={872da645-4a9b-1727-bee2-5585105b9eed} aComponent={ConsoleWrap} aText={Failed to open/create the internal network 'HostInterfaceNetworking-Realtek PCIe GBE Family Controller' (VERR_INTNET_FLT_IF_NOT_FOUND).
00:00:03.341550 Failed to attach the network LUN (VERR_INTNET_FLT_IF_NOT_FOUND)}, preserve=false aResultDetail=0
00:00:03.341693 Console: Machine state changed to 'PoweredOff'
00:00:03.352282 Power up failed (vrc=VERR_INTNET_FLT_IF_NOT_FOUND, rc=E_FAIL (0X80004005))
}}}",Sam Morris
21121,second network interface cannot talk to network,VirtualBox 6.1.38,other,2022-10-09T16:33:38Z,2022-10-09T16:33:38Z,2022-10-09T16:33:38Z,"I added a second interface to a Linux (Ubuntu) VM, bridged, and it does not talk to the network at all. It's supposed to get an IP address via DHCP, but it fails. It's the same class as the first interface, which means that ceteris paribus should work in identical ways.",philip orleans
20924,IPv6 not working out of the box with bridged WiFi and Linux guests,VirtualBox 6.1.34,Windows,2022-05-02T08:32:36Z,2022-10-16T00:31:25Z,2022-10-16T00:31:25Z,"When using a bridge WiFi interface, IPv6 doesn't work out of the box on Linux guests. IPv6 becomes operational only after issuing ""ip -6 neigh del <gateway-linklocal-ipv6> dev <dev>"" as proposed in this gist: https://gist.github.com/0xquad/6090af4fe2c5b5fc6299 (although I found issuing it one single time suffices. No need to issue it repeatedly as the gist suggests).

This problem occurs only with Linux guests. Windows (10?) guests can use IPv6 just fine without any additional steps. Several WiFi NICs (Intel, Realtek) were tested, as well as several routers (FritzBox, Compal, generic OpenWrt). Confirmed also by different people, with different distros, including at least Ubuntu 20.04, 21.10, 22.04, Linux Mint 19.x, Mint 20.x, ArchLinux, Kali 2021. I don't have a Linux host to test with, but it's at least a bug with Windows hosts.

The bug appears similar to https://www.virtualbox.org/ticket/5503 (supposedly fixed) and https://www.virtualbox.org/ticket/14212. However, the latter mentions broken promiscuous mode as problematic. Since Windows guests aren't affected, I think that this is a different bug. The bug exists at least since VirtualBox 5.x, probably earlier versions affected as well.",treysis
21185,"After upgrade to 7.0.2, VM will not launch",VirtualBox-7.0.2,other,2022-10-21T13:43:10Z,2022-10-21T16:25:51Z,2022-10-21T16:25:51Z,"I've been running virtualbox on a Windows 10/11 machine for several years and this is the first issue I've ran in to like this. After upgrading from 7.0.0 to 7.0.2, the issue started. Here is the error I get:
I'll also mention I have uninstalled, rebooted, and reinstalled 7.0.2.
I have uninstalled, rebooted, and reinstalled 6.1.38 but the issue persists.
I did not have this issue when I was running 7.0.0 or 6.1.38, or 6.1.40

Failed to open a session for the virtual machine myserver.
Failed to open/create the internal network 'HostInterfaceNetworking-Realtek Gaming GbE Family Controller' (VERR_SUPDRV_COMPONENT_NOT_FOUND).
Failed to attach the network LUN (VERR_SUPDRV_COMPONENT_NOT_FOUND).
Result Code: E_FAIL (0x80004005)
Component: ConsoleWrap
Interface: IConsole {872da645-4a9b-1727-bee2-5585105b9eed}",vboxuser1001
21269,Unable to use more than 1 host-only adapter using Virtualbox 7.x,VirtualBox-7.0.2,Windows,2022-11-13T18:51:17Z,2022-11-13T18:51:17Z,2022-11-13T18:51:17Z,"Updated to VB 7.02.  I had 2 host-only adapters set up.  After upgrading BOTH host-only adapters were invalid. I would get an error stating that the host-only adapter was unable to open/load.  Create a NEW host-only adapter - same issue.

After deleting BOTH host-only adapters, the app created it's OWN host-only adapter.  I can use this one.  However, I am unable to use ANY OTHER host-only adapter.  I can change the config host-only adapter that the app created, and it works.  However, if I try to create my own (doesn't matter the config), I get an error when trying to load the VM. This DOES NOT happen with vitrualbox 6.x

My laptop is running Windows 11 Pro (latest updates).  The VM is Windows 10 ENT EVAL, but it doesn't matter what OS I use for the VM.
",Fenderluvr
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
21201,FreeBSD 12.3 and pfSense 2.6.0 networking no longer works with upgrade to VB 7.0.2 => fixed in SVN,VirtualBox-7.0.2,Linux,2022-10-24T17:12:33Z,2023-01-12T15:03:06Z,2023-01-12T15:03:06Z,"Hi,

After a recent upgrade from VirtualBox 6.1.40 to 7.0.2 on Arch Linux, all of my pfSense virtual machines hang at ""Configuring WAN interface"" during the boot process. Reverting VirtualBox back to 6.1.40 fixes it.

The pfSense VM (CE 2.6.0) is configured with EFI enabled and the WAN interface is a NAT virtual network adapter with ""virtio-net"". I've tried changing the adapter to either of the Intel PRO/1000 Server options and it does eventually boot after a 5 minute hang at the same point, but it is unable to get an IP and therefore doesn't work either.

I've also tried to create a brand new pfSense VM using the same settings as our currently running ones and while it installs properly, after the reboot it is stuck on ""Default interfaces not found -- Running interface assignment option."". This also works properly in 6.1.40. I've also tried setting the network interface to bridge mode and no change.

Edit: All other VM work properly, including other FreeBSD 13.1 virtual machines but same behavior with FreeBSD 12.3.

Any suggestions?",rickga
19358,VMs lose bridged network connection after host suspend/resume,VirtualBox 6.1.4,Windows,2020-02-28T15:20:54Z,2023-01-29T17:33:29Z,2023-01-29T17:33:29Z,"This doesn't happen every time, but often enough to become frustrating: when I suspend/resume the host, '''all''' of the guests (Windows ''and'' Linux) are unable to communicate over the bridged network.

What does '''not''' work:
 - suspending/resuming the guest
 - restarting the guest OS network services
 - restarting the guest OS
 - disabling/enabling the guest's network adapter
 - disabling/enabling the host's network adapter that is bridged
 - disabling/enabling the vbox bridging driver on the host's network adapter

One thing that did work:
 - connect alternate network adapter on host (eg.: wireless) and set as bridge for VM

Aside from that, the only thing that fully works is to reboot the host, but I have several passwords to enter and dozens of applications to run in order to get my environment setup, which makes frequent rebooting untenable.

This may also provide a clue: when I enabled the host's wireless adapter, the host was not able to receive an IP lease from the router's DHCP server, I had to key in a static IP for the host.

Is there a service or executable I can restart or run to kickstart the bridged networking?",VeHav2GoVeeper
21447,VirtualBox 7.x + | DNS / Name resolution problem,VirtualBox-7.0.6,Windows,2023-01-30T14:20:10Z,2023-01-31T13:57:24Z,2023-01-31T13:57:24Z,"When trying to install a VM with Linux as guest OS under VirtualBox 7.x, the installation fails at the name resolution of the online repo.
This was tested with Debian and Arch Linux. 
The installation gives an error at the moment when the name resolution to the repo is needed.
To exclude an error in the images, Debian was installed from a full image, for this no online repo is necessary during the installation.
In the freshly started OS, however, the error of the non-existent name resolution occurs again, SSH via port forwarding does not work either.
A ping to ""google.de"" is unsuccessful. 
A ping to ""8.8.8.8"", is successful.
During the installation all default values of the installer were taken over.

'''When performing the same installations on VirtualBox 6.1.42, this error does not occur and the name resolution works, likewise SSH works without problems.'''

'''Host: Windows 10 Pro 22H2'''

'''Guest: Debian Stable Bullseye 11.6.0 (Kernel 5.10)
Arch Linux Rolling (Kernel 6.1)'''",carcap
21488,Crash when i change network settings in Ubuntu => fixed in SVN next/7.0.x maintenance,VirtualBox-7.0.6,other,2023-02-09T17:43:54Z,2023-02-10T10:42:41Z,2023-02-10T10:42:41Z,"In my windows host and ubuntu guest I have crashed VM, logs will attached",seven_vb
15308,guest does not regain network connectivity if cable unplugged for for 5+ secs,VirtualBox 5.0.16,Windows,2016-04-14T10:49:47Z,2023-02-11T00:27:22Z,2023-02-11T00:27:22Z,"Host = Windows 10 Version 1151 (Build 10586.164)
Guest = CentOS7.2.1511 x86_64 (Kernel 3.10.0-327.el7.x86_64)

VirtualBox VM has 2 adapters
- 1 = Host-only Adapter (VirtualBox Host-Only Ethernet Adapter)
- 2 = Bridged Adapter (Intel Ethernet Connection I219-LM)

Networking functions 100% between the VM and LAN if I power on the VM with the Ethernet cable plugged in to the bridged interface (Intel Ethernet Connection I219-LM). The VM can communicate with my LAN and vice versa.

If I start a ping from within the Linux VM and disconnect the Ethernet cable from the bridged interface (Intel Ethernet Connection I219-LM) and plug it back in within 5 seconds, the ping picks back up where it left off.

If it takes more than 5 seconds for me to plug the cable back in, the ping does not pick back up and I need to shut down the VM and cold boot it in order to restore networking between the VM and LAN. Restarting the guest Linux networking, a VM reboot, or a disable/enable of all Windows' interfaces does not regain network connectivity to the Linux VM. Only a shutdown and cold boot of the VM.

I've tried the various ""Adapter Types"" in VirtualBox to no avail.

I run static IPs in the guest.

Virtual LAN = 192.168.184.0/24
VirtualBox NIC in PC = 192.168.184.1/24
Linux enp0s8 = 192.168.184.2/24 (default gw 192.168.184.1)

Physical LAN = 10.70.0.0/24
Windows physical NIC = 10.70.8.139/16
Linux enp0s17 = 10.70.8.130/16

Note: If I put the PC to sleep (tested up to 5 mins) and wake it back up, pings pick back up. It's just when I disconnect the cable to more than 5 seconds and plug it back in, the pings do not pick back up.",Tim Riley
