Now that the problem statement is made let’s start working a really simple solution.Just in case you know about port forwarding, this issue can be solved using port forwarding. That also works but the downside of that is that if you have a laptop and wants to work on your guest at home, it might not be accessible. Maybe if you are in an organization and IPs are assigned by a DHCP server, in that case if you choose to set a bridge adapter you would have your guest OS would be a node on the network. The IP assigned to the guest is not reachable by the host(since it’s in different subnet), so there is no way to connect to the guest machine using your favorite ssh client under NAT adapter. But that will limit your access to the client virtualbox frame which is a direct access to the guest machine.
There are situations where a guest OS on vitualbox will need to have Internet connection which is by default through the NAT interface. I am specially worried because one of thwe VM I am going to backup and test is de domain controller, so I must be sure it will be correctly isolated, so it does not interfere with the active DC.The title of this post can be misleading but basically the challenge I would like us to solve is pretty simple.
I.E.: My local and my 'isolated' network should be 192.168.1.x/24. This means the isolated' network should have the same subnet addresses than the local one. > If possible, those 'test VM' should preserve its IP when added to the 'test lab' so. Even though 'isolated', they must have internet access. The idea is being able to backup a VM form my current network, and run it in my ¡'isolated envitonment' to make some tests. > I am going to run backups of some VM now running in my network. I have read about just using an internal swith with NAT ( ), but I have some doubts: I need that all VM inside will be 'isolated' (must no see any computer from my local network, and local network must not see them), but they should be able to access internet through HyperV host
I need to create a 'private test lab' in HyperV.
0 kommentar(er)
