Hyper - v virtual machine // internet access
While I am not an expert, I still cannot understand why the default network (Virtual Switch) is internal and not external. I could not get to the internet through the internal even though it is supposed to do NAT.
The easy solution, without a lot of abrakadabra, is to create another virtual switch, which is external, and use that instead to connect the virtual machine's network interface card.
And unless you are one of those abrakadabra writing masters of powershell, the GUI should be suitable for your needs.
- Open Hyper V Manager
- Go to Virtual Switch Manager
- Create a (new) virtual switch, it does not matter what you select here as...
- You will have to select the type in the next window, select the external network interface through which you have internet access (as this is the whole point of this little hint blog).
- Name it something that is wise or not, you can call it Bravado or whatever.
- Apply and save it.
- Open the settings page for your virtual machine, probably a linux beast, and choose your network to be connected to the newly created virtual switch.
Good luck.
ps.
When you will find yourselves on a hotel with some kind of internet access restriction, which would block two MAC addresses (this is what happens if you use the above technique) I devised a trick to avoid this.
The host is connected with one network interface, in this case the wireless, on windows I would then go through with the registration process via a browser.
The client was instead wired to the hotel's network, and inside the client the registration process was carried out.
No comments:
Post a Comment