<html>
<head>
<style><!--
.hmmessage P
{
margin:0px;
padding:0px
}
body.hmmessage
{
font-size: 12pt;
font-family:Calibri
}
--></style></head>
<body class='hmmessage'><div dir='ltr'>Sorry. I didn't have WinPcap 4.1.3 in the server.<BR>When I upgraded to the latest version, all network interfaces were listed.<BR> <BR>Regards,<BR>J.M.<br> <BR><div><hr id="stopSpelling">From: carpe7@hotmail.com<br>To: winpcap-users@winpcap.org<br>Date: Wed, 19 Feb 2014 14:36:40 +0000<br>Subject: [Winpcap-users] Windows Server 2012 NIC Teaming and WinPcap compatibility<br><br>
<style><!--
.ExternalClass .ecxhmmessage P {
padding:0px;
}
.ExternalClass body.ecxhmmessage {
font-size:12pt;
font-family:Calibri;
}
--></style>
<div dir="ltr">Hi,<br> <br>We plan to use WinPcap to send and receive through network interfaces created in Windows Server 2012 through the teaming feature:<br> <br><a href="http://technet.microsoft.com/en-us/library/hh831648.aspx" target="_blank">http://technet.microsoft.com/en-us/library/hh831648.aspx</a><br> <br>The teaming solution, among other things, allows us to use a single physical NIC and a single physical medium to send to and receive from several VLANs (Windows marks the datagrams as belonging to a specific VLAN and the switch port is configured in trunk mode).<br> <br>In Windows's Network Connections panel, we see the physical interfaces plus the virtual ones. The virtual ones have names that start with "Microsoft Network Adapter Multiplexor Driver". We thought each virtual interface would have its own ID that we would be able to use in pcap_open to refer to that interface.<br> <br>The problem we are facing now is that Wireshark does not offer those interfaces for capturing, so we are wondering if we will be able to capture from them and send traffic through them separately in a program that uses WinPcap (the main networking ingredient in Wireshark).<br> <br>May it be that WinPcap is placed below (in the sense of "nearer the physical NIC") Microsoft Network Adapter Multiplexor Driver (NdisImPlatform.sys) in the stack of network drivers?<br> <br>We used to use HP Teaming software to build our teams in Windows Server 2008 and earlier, but we never tested creating VLAN multiplexed scenarios. Wireshark offers HP teamed interfaces separately from the physical ones, so we assumed that with Windows Server 2012 teaming the situation would be similar.<br> <br>My questions are:<br>1. Is WinPcap 4.1.3 compatible with VLAN multiplexed interfaces through Windows Server 2012 teaming?<br>2. Is using HP teaming software a compatible alternative?<br>3. If the answer is "no" to the previous questions, is there any way to multiplex the traffic to several VLANs in a single "trunk mode" switch port with WinPcap? I mean, is it possible to set the VLANID of a datagram in the Ethernet header or anywhere else and use the physical NIC directly in WinPcap?<br> <br>Thank you very much.<br> <br>Regards,<br>J.M.<br> </div>
<br>_______________________________________________
Winpcap-users mailing list
Winpcap-users@winpcap.org
https://www.winpcap.org/mailman/listinfo/winpcap-users</div> </div></body>
</html>