![](https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEj4YZgY1Eho9MkC58lWE1YR3rb6rVB_rFzDvcNgqT09h051T2c0TRE1uFW85GKF-EGgReCvrGrclCG7O7V-izAkBdIiywVVC6coghgqWhZEpmoBoRv_4KNcpvBRHIW5k43aDDnr/s400/solera_logo.jpg)
It looks like
Solera Networks built a
virtual tap, as I hoped someone would. I mentioned it to Solera when I visited them last year, so I'm glad to see someone built it. I told them it would be helpful for someone to create a way for virtual switches to export traffic from the VM environment to a physical environment, so that a NSM sensor could watch traffic as it would when connected to a physical tap.
This picture describes what it does:
![](https://blogger.googleusercontent.com/img/b/R29vZ2xl/AVvXsEjvGOBn4__-Jv74AVc_Q6vf8Ty3Jf372R_s8d2Y7-nMwHh-UoBLZ15JER2cURjAAvrRgpAhnyldk_CO4YPCQSMJdaxzTC9jLWpE72LjwgwxtkQEmt3B6MfiMBLYwr-PxUgKJjog/s400/virtual_tap_diagram.jpg)
You can read more in this
news post and
product description. You can download it
here. The V2P Tap requires ESX Server, which I do not run. If someone with ESX Server downloads the V2P Tap, please let me know how it works for you.
Comments
Network adapter 1 must be the Management interface.
Network adapter 2 is the V2P Tap interface.
Network adapter 3 is the Regen interface.
In the Solera-V2P directory, cat Solera-V2P.vmx should show:
tools.remindInstall = "TRUE"
ethernet0.address = "00:50:56:01:01:01"
ethernet1.address = "00:50:56:02:02:02"
ethernet2.address = "00:50:56:03:03:03"
My vmx file was missing the latter three entries preventing the dsfs kernel module from loading.
The ESX server needs to be connected to either a SPAN port on a managed switch or a hub to see all traffic.
NIC 1 is V2P Tap. Nic 2 is Management. Nic 3 is Regen.