networking - Windows 8.1 NIC Exists in Two Networks at once
2014-07
TechMedicNYC
My ethernet adapter is showing in two windows network locations at once. How is this possible and how do I remedy it?
The ethernet adapter is configured:
IP: 192.168.10.100
subnet: 255.255.0.0
gateway: 192.168.10.102
The virtualbox network is configured:
IP: 192.168.20.1
subnet: 255.255.255.0
gateway: 192.168.20.1
The ethernet is used for a peer-peer direct connect network via a crossover cable. So the gateway is simply the ip of the other machine. Regardless, I have configured the two nics on the same machine to have different subnets so they won't conflict.
TechMedicNYC
Because windows 8 is so user friendly I took the easy route and just uninstalled all the networking drivers. Went into the registry per this answer and deleted all network locations. Then I uninstalled the bridged virtualbox virtual adapter. Disabled the virtualbox host-only virtual adapter. Installed the intel ethernet drivers. Then because there is no "right-click" on network connections I did: charms > settings > change pc settings > network > connections THEN left click the connection, turn on Find devices so that the network goes private. Then I re-enabled the virtualbox host-only adapter. Windows 8 is such a PO$.
End result:
As you can see now the adapters are on separate networks and not duplicated.
Update: I'm sure this will all break when I re-install the virtualbox bridged network adapter. :-)
rhololkeolke
I'm attempting to test out a piece of networking software that simulates delay between different network segments. In order to simulate the delays the software creates a bridge between two of its Ethernet ports with the specified delay. We've ordered hardware that this software (or some other software with similar functions) will be running on. However, it will be a few weeks before the hardware gets here and I need to know that the software that is chosen will work as expected. Hence I had the idea to make a virtual network with VM's using VirtualBox.
Right now I have 3 VMs: Client1 is on the first network segment, Client2 is on the second network segment, Channel Software sits between the two segments. I've configured the NICs of each VM using the following commands:
VBoxManage modifyvm client1 --nic1 intnet
VBoxManage modifyvm client1 --intnet1 seg1
VBoxManage modifyvm client2 --nic1 intnet
VBoxManage modifyvm client2 --intent1 seg2
VBoxManage modifyvm channel --nic1 intnet
VBoxManage modifyvm channel --nic2 intnet
VBoxManage modifyvm channel --intnet1 seg1
VBoxManage modifyvm channel --intnet2 seg2
When I put a set of IPs on the NICs in seg1 and a different set of IPs on the NICs in seg2 I can ping either segment from the channel VM. However, after setting the two clients to use the same IP network and bridging the virtual connections on the channel VM everything stops working. I've even tried assigning different IP networks to each client, just for the heck of it, but it doesn't work.
I was going to try using something a little fancier like VDE which has native support for VirtualBox. The problem is that if I want to use that I have to compile VirtualBox myself and it appears as if I have to run all of this on Linux. Normally that wouldn't be a problem but I only have access to a Windows machine at work.
I would like to know have I set something up wrong in the virtual network? If so what? If not do I have any alternatives to VDE or do I have to go meta and use VirtualBox to run a Ubuntu VM that runs VirtualBox with VDE and my client VMs?
rhololkeolke
I didn't realize that when I created the bridge it created an entirely separate interface. When I ran ifconfig -a I saw that it created a new interface. When I brought the interface up using ifconfig <bridge name> up Everything worked as expected.