When you set up an internal network in VirtualBox 4.0.4, it seems to work by default like a hub, so that all unicast traffic can be captured from a packet sniffer installed on any guest.
Is it possible to configure the virtual switch to work like a switch and set up private circuits rather than working like a hub?
Packet sniffing
-
ElevenAngryMen
- Posts: 1
- Joined: 15. Mar 2011, 13:18
- Primary OS: MS Windows 7
- VBox Version: VirtualBox+Oracle ExtPack
- Guest OSses: Linux, Server 2008, Windows XP
-
Sasquatch
- Volunteer
- Posts: 17798
- Joined: 17. Mar 2008, 13:41
- Primary OS: Debian other
- VBox Version: VirtualBox+Oracle ExtPack
- Guest OSses: Windows XP, Windows 7, Linux
- Location: /dev/random
Re: Packet sniffing
Unless other VMs need to be able to access the two VMs as well, give the connections different names. E.g. VM1 and VM2 are connected to intnet1, VM3 and VM4 are connected to intnet2. This is of course only when VM1 or VM2 doesn't need access to, or be accessed by, VM3 or 4.
Read the Forum Posting Guide before opening a topic.
VirtualBox FAQ: Check this before asking questions.
Online User Manual: A must read if you want to know what we're talking about.
Howto: Install Linux Guest Additions
Howto: Use Shared Folders on Linux Guest
See the Tutorials and FAQ section at the top of the Forum for more guides.
Try searching the forums first with Google and add the site filter for this forum.
E.g. install guest additions site:forums.virtualbox.org
Retired from this Forum since OSSO introduction.
VirtualBox FAQ: Check this before asking questions.
Online User Manual: A must read if you want to know what we're talking about.
Howto: Install Linux Guest Additions
Howto: Use Shared Folders on Linux Guest
See the Tutorials and FAQ section at the top of the Forum for more guides.
Try searching the forums first with Google and add the site filter for this forum.
E.g. install guest additions site:forums.virtualbox.org
Retired from this Forum since OSSO introduction.