<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META content="text/html; charset=gb2312" http-equiv=Content-Type>
<META name=GENERATOR content="MSHTML 8.00.6001.19394">
<STYLE>@font-face {
font-family: 宋体;
}
@font-face {
font-family: Verdana;
}
@font-face {
font-family: @宋体;
}
@page Section1 {size: 595.3pt 841.9pt; margin: 72.0pt 90.0pt 72.0pt 90.0pt; layout-grid: 15.6pt; }
P.MsoNormal {
TEXT-JUSTIFY: inter-ideograph; TEXT-ALIGN: justify; MARGIN: 0cm 0cm 0pt; FONT-FAMILY: "Times New Roman"; FONT-SIZE: 10.5pt
}
LI.MsoNormal {
TEXT-JUSTIFY: inter-ideograph; TEXT-ALIGN: justify; MARGIN: 0cm 0cm 0pt; FONT-FAMILY: "Times New Roman"; FONT-SIZE: 10.5pt
}
DIV.MsoNormal {
TEXT-JUSTIFY: inter-ideograph; TEXT-ALIGN: justify; MARGIN: 0cm 0cm 0pt; FONT-FAMILY: "Times New Roman"; FONT-SIZE: 10.5pt
}
A:link {
COLOR: blue; TEXT-DECORATION: underline
}
SPAN.MsoHyperlink {
COLOR: blue; TEXT-DECORATION: underline
}
A:visited {
COLOR: purple; TEXT-DECORATION: underline
}
SPAN.MsoHyperlinkFollowed {
COLOR: purple; TEXT-DECORATION: underline
}
SPAN.EmailStyle17 {
FONT-STYLE: normal; FONT-FAMILY: Verdana; COLOR: windowtext; FONT-WEIGHT: normal; TEXT-DECORATION: none; mso-style-type: personal-compose
}
DIV.Section1 {
page: Section1
}
UNKNOWN {
FONT-SIZE: 10pt
}
BLOCKQUOTE {
MARGIN-TOP: 0px; MARGIN-BOTTOM: 0px; MARGIN-LEFT: 2em
}
OL {
MARGIN-TOP: 0px; MARGIN-BOTTOM: 0px
}
UL {
MARGIN-TOP: 0px; MARGIN-BOTTOM: 0px
}
</STYLE>
</HEAD>
<BODY style="MARGIN: 10px; FONT-FAMILY: verdana; FONT-SIZE: 10pt">
<DIV><FONT color=#000080 size=2 face=Verdana>Hi, GV </FONT></DIV>
<DIV style="TEXT-INDENT: 2em"><FONT color=#000080>I try to send jumbo packet
through windows xp's loopback interface.</FONT></DIV>
<DIV style="TEXT-INDENT: 2em"><FONT color=#000080>Does it support the way I
do?</FONT></DIV>
<DIV style="TEXT-INDENT: 2em"><FONT color=#000080>If not, could I try the 1G
ethernet interface and enable the jumbo capability? </FONT></DIV>
<DIV style="TEXT-INDENT: 2em"><FONT color=#000080></FONT> </DIV>
<DIV style="TEXT-INDENT: 2em"><FONT color=#000080>Regards. </FONT></DIV>
<DIV style="TEXT-INDENT: 2em"><FONT color=#000080></FONT> </DIV>
<DIV><FONT color=#000080>xfma</FONT></DIV>
<DIV><FONT color=#000080></FONT> </DIV>
<DIV><FONT color=#000080 size=2 face=Verdana></FONT> </DIV>
<DIV><FONT color=#000080 size=2 face=Verdana></FONT> </DIV>
<DIV><FONT color=#c0c0c0 size=2 face=Verdana>2013-01-31 </FONT></DIV><FONT
color=#000080 size=2 face=Verdana>
<HR style="WIDTH: 100px" align=left color=#b5c4df SIZE=1>
</FONT>
<DIV><FONT color=#c0c0c0 size=2 face=Verdana><SPAN>
<DIV>
<DIV>马晓飞</DIV>
<DIV>
<DIV>
<DIV>工作电话：02759100279</DIV></DIV>
<DIV>手机：15071274654 </DIV>
<DIV>烽火通信网络产出线IP协议组</DIV>
<DIV><A
href="mailto:xfma@fiberhome.com.cn">xfma@fiberhome.com.cn</A></DIV></DIV>
<DIV> </DIV></DIV></SPAN></FONT></DIV>
<HR color=#b5c4df SIZE=1>
<DIV><FONT size=2 face=Verdana><STRONG>发件人：</STRONG>
winpcap-users-request@winpcap.org </FONT></DIV>
<DIV><FONT size=2 face=Verdana><STRONG>发送时间：</STRONG> 2013-01-31 06:17:44
</FONT></DIV>
<DIV><FONT size=2 face=Verdana><STRONG>收件人：</STRONG> winpcap-users@winpcap.org
</FONT></DIV>
<DIV><FONT size=2 face=Verdana><STRONG>抄送：</STRONG> </FONT></DIV>
<DIV><FONT size=2 face=Verdana><STRONG>主题：</STRONG> Winpcap-users Digest, Vol
94, Issue 8 </FONT></DIV>
<DIV><FONT size=2 face=Verdana></FONT> </DIV>
<DIV><FONT size=2 face=Verdana>
<DIV>Send Winpcap-users mailing list submissions to</DIV>
<DIV>winpcap-users@winpcap.org</DIV>
<DIV></DIV>
<DIV>To subscribe or unsubscribe via the World Wide Web, visit</DIV>
<DIV>https://www.winpcap.org/mailman/listinfo/winpcap-users</DIV>
<DIV>or, via email, send a message with subject or body 'help' to</DIV>
<DIV>winpcap-users-request@winpcap.org</DIV>
<DIV></DIV>
<DIV>You can reach the person managing the list at</DIV>
<DIV>winpcap-users-owner@winpcap.org</DIV>
<DIV></DIV>
<DIV>When replying, please edit your Subject line so it is more specific</DIV>
<DIV>than "Re: Contents of Winpcap-users digest..."</DIV>
<DIV></DIV>
<DIV></DIV>
<DIV>Today's Topics:</DIV>
<DIV></DIV>
<DIV> 1. Missing pcap_start_oem()? (Rich Chomiczewski)</DIV>
<DIV> 2. Re: Missing pcap_start_oem()? (Gianluca Varenni)</DIV>
<DIV> 3. Re: Missing pcap_start_oem()? (Rich Chomiczewski)</DIV>
<DIV> 4. Re: Windows 8 (Gianluca Varenni)</DIV>
<DIV> 5. Re: question about the api 'PacketSendPacket' (Gianluca Varenni)</DIV>
<DIV></DIV>
<DIV></DIV>
<DIV>----------------------------------------------------------------------</DIV>
<DIV></DIV>
<DIV>Message: 1</DIV>
<DIV>Date: Wed, 30 Jan 2013 16:12:02 -0500</DIV>
<DIV>From: Rich Chomiczewski <rchomiczewski@gmail.com></DIV>
<DIV>To: winpcap-users@winpcap.org</DIV>
<DIV>Subject: [Winpcap-users] Missing pcap_start_oem()?</DIV>
<DIV>Message-ID:</DIV>
<DIV><CAF2XbyXkgckBKCSVUhgS9vMRH5pqB+68_6TAZSbfd5NWiNiiBw@mail.gmail.com></DIV>
<DIV>Content-Type: text/plain; charset="iso-8859-1"</DIV>
<DIV></DIV>
<DIV>I'm working on upgrading from 4.0.2 to 4.1.2 and noticed that</DIV>
<DIV>pcap_start_oem() is no longer exported from wpcap.dll.</DIV>
<DIV></DIV>
<DIV>What was the original purpose of that API?</DIV>
<DIV></DIV>
<DIV>Why was it removed?</DIV>
<DIV></DIV>
<DIV>-- </DIV>
<DIV>Rich</DIV>
<DIV>-------------- next part --------------</DIV>
<DIV>An HTML attachment was scrubbed...</DIV>
<DIV>URL: <http://www.winpcap.org/pipermail/winpcap-users/attachments/20130130/aa0db18a/attachment-0001.html></DIV>
<DIV></DIV>
<DIV>------------------------------</DIV>
<DIV></DIV>
<DIV>Message: 2</DIV>
<DIV>Date: Wed, 30 Jan 2013 22:01:52 +0000</DIV>
<DIV>From: Gianluca Varenni <Gianluca.Varenni@riverbed.com></DIV>
<DIV>To: "winpcap-users@winpcap.org" <winpcap-users@winpcap.org></DIV>
<DIV>Subject: Re: [Winpcap-users] Missing pcap_start_oem()?</DIV>
<DIV>Message-ID:</DIV>
<DIV><8A9226C4990BF648BD21174A6F44BDFD73EA1E6A@365EXCH-MBX-P3.nbttech.com></DIV>
<DIV>Content-Type: text/plain; charset="us-ascii"</DIV>
<DIV></DIV>
<DIV>That API is not part of the standard WinPcap library. It was part of WinPcap Professional, which is no longer on sale.</DIV>
<DIV></DIV>
<DIV>Have a nice day</DIV>
<DIV>GV</DIV>
<DIV></DIV>
<DIV>From: winpcap-users-bounces@winpcap.org [mailto:winpcap-users-bounces@winpcap.org] On Behalf Of Rich Chomiczewski</DIV>
<DIV>Sent: Wednesday, January 30, 2013 1:12 PM</DIV>
<DIV>To: winpcap-users@winpcap.org</DIV>
<DIV>Subject: [Winpcap-users] Missing pcap_start_oem()?</DIV>
<DIV></DIV>
<DIV>I'm working on upgrading from 4.0.2 to 4.1.2 and noticed that pcap_start_oem() is no longer exported from wpcap.dll.</DIV>
<DIV></DIV>
<DIV>What was the original purpose of that API?</DIV>
<DIV></DIV>
<DIV>Why was it removed?</DIV>
<DIV></DIV>
<DIV>--</DIV>
<DIV>Rich</DIV>
<DIV>-------------- next part --------------</DIV>
<DIV>An HTML attachment was scrubbed...</DIV>
<DIV>URL: <http://www.winpcap.org/pipermail/winpcap-users/attachments/20130130/eb75bc25/attachment-0001.html></DIV>
<DIV></DIV>
<DIV>------------------------------</DIV>
<DIV></DIV>
<DIV>Message: 3</DIV>
<DIV>Date: Wed, 30 Jan 2013 17:08:24 -0500</DIV>
<DIV>From: Rich Chomiczewski <rchomiczewski@gmail.com></DIV>
<DIV>To: winpcap-users@winpcap.org</DIV>
<DIV>Subject: Re: [Winpcap-users] Missing pcap_start_oem()?</DIV>
<DIV>Message-ID:</DIV>
<DIV><CAF2XbyVorSPRtt_iRKPCvWP3S8k1S-YZ+YNsSQ2BZWmo083vig@mail.gmail.com></DIV>
<DIV>Content-Type: text/plain; charset="iso-8859-1"</DIV>
<DIV></DIV>
<DIV>What functionality have we lost with its removal?</DIV>
<DIV></DIV>
<DIV>On Wed, Jan 30, 2013 at 5:01 PM, Gianluca Varenni <</DIV>
<DIV>Gianluca.Varenni@riverbed.com> wrote:</DIV>
<DIV></DIV>
<DIV>> That API is not part of the standard WinPcap library. It was part of</DIV>
<DIV>> WinPcap Professional, which is no longer on sale.****</DIV>
<DIV>></DIV>
<DIV>> ** **</DIV>
<DIV>></DIV>
<DIV>> Have a nice day****</DIV>
<DIV>></DIV>
<DIV>> GV****</DIV>
<DIV>></DIV>
<DIV>> ** **</DIV>
<DIV>></DIV>
<DIV>> *From:* winpcap-users-bounces@winpcap.org [mailto:</DIV>
<DIV>> winpcap-users-bounces@winpcap.org] *On Behalf Of *Rich Chomiczewski</DIV>
<DIV>> *Sent:* Wednesday, January 30, 2013 1:12 PM</DIV>
<DIV>> *To:* winpcap-users@winpcap.org</DIV>
<DIV>> *Subject:* [Winpcap-users] Missing pcap_start_oem()?****</DIV>
<DIV>></DIV>
<DIV>> ** **</DIV>
<DIV>></DIV>
<DIV>> I'm working on upgrading from 4.0.2 to 4.1.2 and noticed that</DIV>
<DIV>> pcap_start_oem() is no longer exported from wpcap.dll.****</DIV>
<DIV>></DIV>
<DIV>> ** **</DIV>
<DIV>></DIV>
<DIV>> What was the original purpose of that API?****</DIV>
<DIV>></DIV>
<DIV>> ** **</DIV>
<DIV>></DIV>
<DIV>> Why was it removed?****</DIV>
<DIV>></DIV>
<DIV>> ** **</DIV>
<DIV>></DIV>
<DIV>> --</DIV>
<DIV>> Rich****</DIV>
<DIV>></DIV>
<DIV>> _______________________________________________</DIV>
<DIV>> Winpcap-users mailing list</DIV>
<DIV>> Winpcap-users@winpcap.org</DIV>
<DIV>> https://www.winpcap.org/mailman/listinfo/winpcap-users</DIV>
<DIV>></DIV>
<DIV>></DIV>
<DIV></DIV>
<DIV></DIV>
<DIV>-- </DIV>
<DIV>Rich</DIV>
<DIV>-------------- next part --------------</DIV>
<DIV>An HTML attachment was scrubbed...</DIV>
<DIV>URL: <http://www.winpcap.org/pipermail/winpcap-users/attachments/20130130/27254071/attachment-0001.html></DIV>
<DIV></DIV>
<DIV>------------------------------</DIV>
<DIV></DIV>
<DIV>Message: 4</DIV>
<DIV>Date: Wed, 30 Jan 2013 22:12:24 +0000</DIV>
<DIV>From: Gianluca Varenni <Gianluca.Varenni@riverbed.com></DIV>
<DIV>To: "winpcap-users@winpcap.org" <winpcap-users@winpcap.org></DIV>
<DIV>Subject: Re: [Winpcap-users] Windows 8</DIV>
<DIV>Message-ID:</DIV>
<DIV><8A9226C4990BF648BD21174A6F44BDFD73EA1E97@365EXCH-MBX-P3.nbttech.com></DIV>
<DIV>Content-Type: text/plain; charset="us-ascii"</DIV>
<DIV></DIV>
<DIV>Chris,</DIV>
<DIV></DIV>
<DIV>I've been thinking about it, but it's a major effort (read it as "rewrite a good chunk of the kernel capture driver"). WHQL certification has not that important so far (we don't certify the driver, we just sign it), we install the driver in such a way that doesn't require WHQL certification.</DIV>
<DIV></DIV>
<DIV>Regarding XP, there is still a big community using it in corporate and non-corporate environments, so dropping support for it is definitely not an option. </DIV>
<DIV></DIV>
<DIV>The advantages of migrating to NDIS6 would be</DIV>
<DIV>- probably better performance (but it's not guaranteed) and in general avoiding to go thru the thunking layer between NDIS5 (what we currently use) and NDIS6</DIV>
<DIV>- support for RT (although I'm not sure if just supporting NDIS6 would be enough)</DIV>
<DIV>- cleanup of the driver sources</DIV>
<DIV></DIV>
<DIV>Have a nice day</DIV>
<DIV>GV</DIV>
<DIV></DIV>
<DIV>-----Original Message-----</DIV>
<DIV>From: winpcap-users-bounces@winpcap.org [mailto:winpcap-users-bounces@winpcap.org] On Behalf Of belinea123@gmx.de</DIV>
<DIV>Sent: Wednesday, January 30, 2013 1:58 AM</DIV>
<DIV>To: winpcap-users@winpcap.org</DIV>
<DIV>Subject: Re: [Winpcap-users] Windows 8</DIV>
<DIV></DIV>
<DIV></DIV>
<DIV>> There will be, most probably by mid/end February.</DIV>
<DIV>> </DIV>
<DIV>> GV</DIV>
<DIV>> </DIV>
<DIV></DIV>
<DIV></DIV>
<DIV>Do you have plans to make a NDIS 6 version?</DIV>
<DIV></DIV>
<DIV>According to the following link, NDIS 6 offers different possibilities for performance optimization and other features. NDIS 6 is required in order to obtain a WHQL certification.</DIV>
<DIV>http://www.osronline.com/showthread.cfm?link=220627</DIV>
<DIV></DIV>
<DIV>According to this link, NDIS 6 is required if you want the driver to run on Windows RT:</DIV>
<DIV>http://www.osronline.com/showThread.cfm?link=237365</DIV>
<DIV></DIV>
<DIV>AFAIK the NDIS 6 driver won't run on Windows XP. But Windows XP will stop receiving security updates in 2013, so the old NDIS 5 driver will not have to be maintained for a long time.</DIV>
<DIV></DIV>
<DIV></DIV>
<DIV>Regards</DIV>
<DIV>Chris Troester</DIV>
<DIV>_______________________________________________</DIV>
<DIV>Winpcap-users mailing list</DIV>
<DIV>Winpcap-users@winpcap.org</DIV>
<DIV>https://www.winpcap.org/mailman/listinfo/winpcap-users</DIV>
<DIV></DIV>
<DIV></DIV>
<DIV>------------------------------</DIV>
<DIV></DIV>
<DIV>Message: 5</DIV>
<DIV>Date: Wed, 30 Jan 2013 22:15:25 +0000</DIV>
<DIV>From: Gianluca Varenni <Gianluca.Varenni@riverbed.com></DIV>
<DIV>To: "winpcap-users@winpcap.org" <winpcap-users@winpcap.org></DIV>
<DIV>Subject: Re: [Winpcap-users] question about the api</DIV>
<DIV>'PacketSendPacket'</DIV>
<DIV>Message-ID:</DIV>
<DIV><8A9226C4990BF648BD21174A6F44BDFD73EA1EB7@365EXCH-MBX-P3.nbttech.com></DIV>
<DIV>Content-Type: text/plain; charset="gb2312"</DIV>
<DIV></DIV>
<DIV>The limit comes directly from the underlying NIC driver.</DIV>
<DIV></DIV>
<DIV>Are you trying to transmit on a 1G/10G Ethernet port? Did you enable support for jumbo frames in your NIC properties?</DIV>
<DIV></DIV>
<DIV>Have a nice day</DIV>
<DIV>GV</DIV>
<DIV></DIV>
<DIV>From: winpcap-users-bounces@winpcap.org [mailto:winpcap-users-bounces@winpcap.org] On Behalf Of ???</DIV>
<DIV>Sent: Wednesday, January 30, 2013 6:52 AM</DIV>
<DIV>To: winpcap-users</DIV>
<DIV>Subject: [Winpcap-users] question about the api 'PacketSendPacket'</DIV>
<DIV></DIV>
<DIV>[cid:image001.png@01CDFEF4.3F0CC810]</DIV>
<DIV></DIV>
<DIV></DIV>
<DIV>[cid:image002.png@01CDFEF4.3F0CC810]</DIV>
<DIV></DIV>
<DIV></DIV>
<DIV>hi,</DIV>
<DIV>I used to send packet length larger than ethernet mtu 1500 with the api 'PacketSendPacket ', and return error. So I want to know how to do it sussessfully.</DIV>
<DIV></DIV>
<DIV>Thanks!!!</DIV>
<DIV></DIV>
<DIV>2013-01-30</DIV>
<DIV>________________________________</DIV>
<DIV>???</DIV>
<DIV>?????02759100279</DIV>
<DIV>???15071274654</DIV>
<DIV>?????????IP???</DIV>
<DIV>xfma@fiberhome.com.cn<mailto:xfma@fiberhome.com.cn></DIV>
<DIV></DIV>
<DIV></DIV>
<DIV></DIV>
<DIV>[cid:image003.png@01CDFEF4.3F0CC810]</DIV>
<DIV></DIV>
<DIV></DIV>
<DIV>[cid:image001.png@01CDFEF4.3F0CC810]</DIV>
<DIV></DIV>
<DIV></DIV>
<DIV></DIV>
<DIV>-------------- next part --------------</DIV>
<DIV>An HTML attachment was scrubbed...</DIV>
<DIV>URL: <http://www.winpcap.org/pipermail/winpcap-users/attachments/20130130/e387e70b/attachment.html></DIV>
<DIV>-------------- next part --------------</DIV>
<DIV>A non-text attachment was scrubbed...</DIV>
<DIV>Name: image001.png</DIV>
<DIV>Type: image/png</DIV>
<DIV>Size: 183 bytes</DIV>
<DIV>Desc: image001.png</DIV>
<DIV>URL: <http://www.winpcap.org/pipermail/winpcap-users/attachments/20130130/e387e70b/attachment.png></DIV>
<DIV>-------------- next part --------------</DIV>
<DIV>A non-text attachment was scrubbed...</DIV>
<DIV>Name: image002.png</DIV>
<DIV>Type: image/png</DIV>
<DIV>Size: 183 bytes</DIV>
<DIV>Desc: image002.png</DIV>
<DIV>URL: <http://www.winpcap.org/pipermail/winpcap-users/attachments/20130130/e387e70b/attachment-0001.png></DIV>
<DIV>-------------- next part --------------</DIV>
<DIV>A non-text attachment was scrubbed...</DIV>
<DIV>Name: image003.png</DIV>
<DIV>Type: image/png</DIV>
<DIV>Size: 183 bytes</DIV>
<DIV>Desc: image003.png</DIV>
<DIV>URL: <http://www.winpcap.org/pipermail/winpcap-users/attachments/20130130/e387e70b/attachment-0002.png></DIV>
<DIV></DIV>
<DIV>------------------------------</DIV>
<DIV></DIV>
<DIV>_______________________________________________</DIV>
<DIV>Winpcap-users mailing list</DIV>
<DIV>Winpcap-users@winpcap.org</DIV>
<DIV>https://www.winpcap.org/mailman/listinfo/winpcap-users</DIV>
<DIV></DIV>
<DIV></DIV>
<DIV>End of Winpcap-users Digest, Vol 94, Issue 8</DIV>
<DIV>********************************************</DIV></FONT></DIV></BODY></HTML>