Hi, GV I try to send jumbo packet through windows xp's loopback interface. Does it support the way I do? If not, could I try the 1G ethernet interface and enable the jumbo capability?
Regards. xfma 2013-01-31 马晓飞 工作电话：02759100279 手机：15071274654 烽火通信网络产出线IP协议组 [email protected] 发件人： [email protected] 发送时间： 2013-01-31 06:17:44 收件人： [email protected] 抄送： 主题： Winpcap-users Digest, Vol 94, Issue 8 Send Winpcap-users mailing list submissions to [email protected] To subscribe or unsubscribe via the World Wide Web, visit https://www.winpcap.org/mailman/listinfo/winpcap-users or, via email, send a message with subject or body 'help' to [email protected] You can reach the person managing the list at [email protected] When replying, please edit your Subject line so it is more specific than "Re: Contents of Winpcap-users digest..." Today's Topics: 1. Missing pcap_start_oem()? (Rich Chomiczewski) 2. Re: Missing pcap_start_oem()? (Gianluca Varenni) 3. Re: Missing pcap_start_oem()? (Rich Chomiczewski) 4. Re: Windows 8 (Gianluca Varenni) 5. Re: question about the api 'PacketSendPacket' (Gianluca Varenni) ---------------------------------------------------------------------- Message: 1 Date: Wed, 30 Jan 2013 16:12:02 -0500 From: Rich Chomiczewski <[email protected]> To: [email protected] Subject: [Winpcap-users] Missing pcap_start_oem()? Message-ID: <caf2xbyxkgckbkcsvuhgs9vmrh5pqb+68_6tazsbfd5nwini...@mail.gmail.com> Content-Type: text/plain; charset="iso-8859-1" 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. What was the original purpose of that API? Why was it removed? -- Rich -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://www.winpcap.org/pipermail/winpcap-users/attachments/20130130/aa0db18a/attachment-0001.html> ------------------------------ Message: 2 Date: Wed, 30 Jan 2013 22:01:52 +0000 From: Gianluca Varenni <[email protected]> To: "[email protected]" <[email protected]> Subject: Re: [Winpcap-users] Missing pcap_start_oem()? Message-ID: <8a9226c4990bf648bd21174a6f44bdfd73ea1...@365exch-mbx-p3.nbttech.com> Content-Type: text/plain; charset="us-ascii" That API is not part of the standard WinPcap library. It was part of WinPcap Professional, which is no longer on sale. Have a nice day GV From: [email protected] [mailto:[email protected]] On Behalf Of Rich Chomiczewski Sent: Wednesday, January 30, 2013 1:12 PM To: [email protected] Subject: [Winpcap-users] Missing pcap_start_oem()? 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. What was the original purpose of that API? Why was it removed? -- Rich -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://www.winpcap.org/pipermail/winpcap-users/attachments/20130130/eb75bc25/attachment-0001.html> ------------------------------ Message: 3 Date: Wed, 30 Jan 2013 17:08:24 -0500 From: Rich Chomiczewski <[email protected]> To: [email protected] Subject: Re: [Winpcap-users] Missing pcap_start_oem()? Message-ID: <caf2xbyvorsprtt_irkpcvwp3s8k1s-yz+ynssq2bzwmo083...@mail.gmail.com> Content-Type: text/plain; charset="iso-8859-1" What functionality have we lost with its removal? On Wed, Jan 30, 2013 at 5:01 PM, Gianluca Varenni < [email protected]> wrote: > That API is not part of the standard WinPcap library. It was part of > WinPcap Professional, which is no longer on sale.**** > > ** ** > > Have a nice day**** > > GV**** > > ** ** > > *From:* [email protected] [mailto: > [email protected]] *On Behalf Of *Rich Chomiczewski > *Sent:* Wednesday, January 30, 2013 1:12 PM > *To:* [email protected] > *Subject:* [Winpcap-users] Missing pcap_start_oem()?**** > > ** ** > > 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.**** > > ** ** > > What was the original purpose of that API?**** > > ** ** > > Why was it removed?**** > > ** ** > > -- > Rich**** > > _______________________________________________ > Winpcap-users mailing list > [email protected] > https://www.winpcap.org/mailman/listinfo/winpcap-users > > -- Rich -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://www.winpcap.org/pipermail/winpcap-users/attachments/20130130/27254071/attachment-0001.html> ------------------------------ Message: 4 Date: Wed, 30 Jan 2013 22:12:24 +0000 From: Gianluca Varenni <[email protected]> To: "[email protected]" <[email protected]> Subject: Re: [Winpcap-users] Windows 8 Message-ID: <8a9226c4990bf648bd21174a6f44bdfd73ea1...@365exch-mbx-p3.nbttech.com> Content-Type: text/plain; charset="us-ascii" Chris, 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. 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. The advantages of migrating to NDIS6 would be - 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 - support for RT (although I'm not sure if just supporting NDIS6 would be enough) - cleanup of the driver sources Have a nice day GV -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of [email protected] Sent: Wednesday, January 30, 2013 1:58 AM To: [email protected] Subject: Re: [Winpcap-users] Windows 8 > There will be, most probably by mid/end February. > > GV > Do you have plans to make a NDIS 6 version? 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. http://www.osronline.com/showthread.cfm?link=220627 According to this link, NDIS 6 is required if you want the driver to run on Windows RT: http://www.osronline.com/showThread.cfm?link=237365 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. Regards Chris Troester _______________________________________________ Winpcap-users mailing list [email protected] https://www.winpcap.org/mailman/listinfo/winpcap-users ------------------------------ Message: 5 Date: Wed, 30 Jan 2013 22:15:25 +0000 From: Gianluca Varenni <[email protected]> To: "[email protected]" <[email protected]> Subject: Re: [Winpcap-users] question about the api 'PacketSendPacket' Message-ID: <8a9226c4990bf648bd21174a6f44bdfd73ea1...@365exch-mbx-p3.nbttech.com> Content-Type: text/plain; charset="gb2312" The limit comes directly from the underlying NIC driver. Are you trying to transmit on a 1G/10G Ethernet port? Did you enable support for jumbo frames in your NIC properties? Have a nice day GV From: [email protected] [mailto:[email protected]] On Behalf Of ??? Sent: Wednesday, January 30, 2013 6:52 AM To: winpcap-users Subject: [Winpcap-users] question about the api 'PacketSendPacket' [cid:[email protected]] [cid:[email protected]] hi, 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. Thanks!!! 2013-01-30 ________________________________ ??? ?????02759100279 ???15071274654 ?????????IP??? [email protected]<mailto:[email protected]> [cid:[email protected]] [cid:[email protected]] -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://www.winpcap.org/pipermail/winpcap-users/attachments/20130130/e387e70b/attachment.html> -------------- next part -------------- A non-text attachment was scrubbed... Name: image001.png Type: image/png Size: 183 bytes Desc: image001.png URL: <http://www.winpcap.org/pipermail/winpcap-users/attachments/20130130/e387e70b/attachment.png> -------------- next part -------------- A non-text attachment was scrubbed... Name: image002.png Type: image/png Size: 183 bytes Desc: image002.png URL: <http://www.winpcap.org/pipermail/winpcap-users/attachments/20130130/e387e70b/attachment-0001.png> -------------- next part -------------- A non-text attachment was scrubbed... Name: image003.png Type: image/png Size: 183 bytes Desc: image003.png URL: <http://www.winpcap.org/pipermail/winpcap-users/attachments/20130130/e387e70b/attachment-0002.png> ------------------------------ _______________________________________________ Winpcap-users mailing list [email protected] https://www.winpcap.org/mailman/listinfo/winpcap-users End of Winpcap-users Digest, Vol 94, Issue 8 ********************************************
_______________________________________________ Winpcap-users mailing list [email protected] https://www.winpcap.org/mailman/listinfo/winpcap-users
