On 15/05/2012 02:53, John wrote:
That's not necessary unless you want those VLANs visible to the outside world - The Virtualbox Internal Interfaces work just as VLANs do - a broadcast domain. You only need NICs for interfaces / subnets that require external visibility for that subnet / VLAN."Ingo Strüwing"<[email protected]> wrote in message news:[email protected]...Unfortunately, mac addresses can be forged. A VLAN, base on MAC addresses (also called a dynamic VLAN) is not is not as secure as a static VLAN, which is based on switch ports. For a statc VLAN you would need two network interfaces in your computer, bridge the VM to one of them and use the other for the host. Having two NICs is easily enough to arrange. I think I will take a look at this option. I have some pointers now for further investigation. Thank you, again.
If your physical interfaces support dot1Q tagging then you can still use a single interface in trunk mode to your switch, and bridge to the sub-interface to provide the connectivity.
smime.p7s
Description: S/MIME Cryptographic Signature
------------------------------------------------------------------------------ Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
_______________________________________________ VBox-users-community mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/vbox-users-community
