Official doc here http://www.virtualbox.org/manual/ch06.html
An extra requirement is being able to mount an arbitrary IP alias on the NIC, to dedicate an IP (channel) to each managed server/admin. This with the certitude that this IP should not interfere with the Host network (enough of duplicate IPs causing panic in the firm).
I wonder what is the best strategy to configure the Virtual Network in the VB.
Excellent post on the different virtual networking modes in VirtualBox:
https://blogs.oracle.com/fatbloke/entry/networking_in_virtualbox1
These are the alternatives:
- Network Address Translation (NAT)
- Bridged Networking
- Internal Networking
- Host-only Networking
- Port-Forwarding with NAT Networking
I feel more inspired by an Internal Networking, since I need no access from the outside world, and actually I want to shield myself from causing trouble to the rest of the organization - for instance by mounting unwanted IPs.
more later...
No comments:
Post a Comment