I am successfully getting my internet to my Windows Host from a source inside a Virtualbox VM (a passed-through usb dongle), through the Virtualbox Host-Only Ethernet Adapter.
But Windows thinks I'm "Not connected" "You aren't connected to any networks" "No connections are available". Even though windows has internet.
Perfmon knows I'm getting internet and reports the network activity graphs etc.
The problem is some software (e.g. Unity game engine) will also believe I am not connected to the internet, and will be unable to run due to phoning home / license checks. What do?
[EDIT]
Don't know why it's relevant, but my VB Host-Only Network is set to static IP, subnet mask, and gateway; and the DNS server is also manually specified. The values are the values of the shared network connection from inside linux and they're correct since it works flawlessly. There are no other network connections in Windows for security raisins.
Why I'm getting my internet from a Linux VM: again, not relevant, but it's because I need an actually working vpn killswitch, and otherwise want to / like to manage all my network stuff inside of Linux and not Windows.
[EDIT2]
Everything in my ipconfig -all
:
Ethernet adapter VirtualBox Host-Only Network:
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : VirtualBox Host-Only Ethernet Adapter
Physical Address. . . . . . . . . : 0A-00-27-00-00-03
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
Link-local IPv6 Address . . . . . : fe80::c1d3:ae9:4ae6:2e40%3(Preferred)
IPv4 Address. . . . . . . . . . . : 10.42.0.208(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 10.42.0.1
DHCPv6 IAID . . . . . . . . . . . : 554303527
DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-22-5A-EB-20-00-0E-C6-C6-C5-50
DNS Servers . . . . . . . . . . . : 10.42.0.1
NetBIOS over Tcpip. . . . . . . . : Enabled
ipconfig /all
. Why are you using a VM?ipconfig -all
? The gateway is the IP of the Linux ethernet adapter which is shared through VirtualBox. That same IP is used for the DNS server. Subnet mask is irrelevant etc. It works. It's about the only way to set it up, apart from just using DHCP.ipconfig -all
. Don't know how it'll help solve what's likely a driver compatibility issue.