• Some users have recently had their accounts hijacked. It seems that the now defunct EVGA forums might have compromised your password there and seems many are using the same PW here. We would suggest you UPDATE YOUR PASSWORD and TURN ON 2FA for your account here to further secure it. None of the compromised accounts had 2FA turned on.
    Once you have enabled 2FA, your account will be updated soon to show a badge, letting other members know that you use 2FA to protect your account. This should be beneficial for everyone that uses FSFT.

Hyper-V and span ports

jadams

2[H]4U
Joined
Mar 14, 2010
Messages
4,086
In the phone recording business that I'm in the easiest way to record IP phones is by setting up a span port on the interface of a switch the phoen is connected to and span it to our "logger"

Currently if you span to a nic Hyper-V is using it will not get to any of the VM's. There is no fix for this as of right now. Its just a limitation.

VMWare does this with promiscuous mode I believe. With Windows Server 8 coming out. Anyone know if this is resolved?
 
You are going to have to use a proxy to direct that traffic to your logger.
 
the proxy would sitll have to be a physical machine. thus defeating the purpose. if i had to have a physical machine then I'd just stick with a physical logger.
 
the proxy would sitll have to be a physical machine. thus defeating the purpose. if i had to have a physical machine then I'd just stick with a physical logger.

Lots of organizations already have proxies for other purposes, so it was just an idea...realize its not ideal.

Not sure we will be able to do this in Win Server 8 either.
 
I'll keep that in mind if there is a proxy in place.

However I'm having a hard time seeing how that will work too. Or maybe my knowledge of proxies is lacking.

The traffic on the span is a complete copy of other traffic. The loggers identify different phones/extensions by filtering by IP on the source and destination of the packets. Wouldnt running it through a proxy mess all that up?
 
Proxy wouldnt mess that up. Your packets still contain that information.

Think about a web proxy, it just redirects your traffic, still has source/destination otherwise your web request would never load.
 
Last edited:
The way I think of a web proxy.... and it very well might be wrong...

My pc contacts the proxy directly,
The proxy contacts the external website for me
The external website replies to the proxy
the proxy replies to me
 
Just thinking out loud:

What if you created a bridge on the host? You have to dedicate a physical NIC to a Hyper-V Virtual Network.

New Virtual Network: Span
Then on the host bridge the physical nic and the virtual nic.
In an elevated command prompt, execute the following:
<netsh bridge show adapter>
For each Hyper-V virtual NIC, execute the following, replacing {number} with the number of the NIC:
<netsh bridge set adapter {number} forcecompatmode=enable>
 
Back
Top