Hello,
I have an urgent problem: Is there any way to get the
lost/resent packets information. I need to get the
specific information, like the original sender for
lost/resent packets. I didn't find any clue from the
tcp header.
Thanks a lot,
Best,
Shaofeng
___
Hi
I've sent a small patch to freebsd-net that enables bpf writes for all
DLT_NULL devices in the tree in a consistent way. I'm about to look
into doing the same for netbsd / openbsd / etc. Before I do this, I
want to establish consensus that this is ok, or have a solid reason
why not to do this
On Jun 7, 2005, at 3:49 AM, Bruce M Simpson wrote:
1) Compatibility of WinPcap vs libpcap -- it would be nice if we
could build both Win32 and UNIX versions from the same libpcap
tree,
but this is something we can work around at XORP makefile level;
Build Win32 and UNIX versions o
Hi,
This is a bit of a long mail, so I'll address some of the points raised
in a previous thread, and raise some of my own.
MSVCRT.DLL
--
MinGW uses MSVCRT.DLL explicitly. The newer MS VC++ compilers do not. They may
be configured to do so. The rule is -- don't mix runtime versions, and
CVS log entries from 06.06.2005 (Mon) 09:07:05 - 07.06.2005 (Tue) 09:07:02 GMT
=
Summary by authors
=
Author: hannes
File: libpcap/gencode.c; Revisions: 1.248, 1.221.2.22
===
On Tue, Jun 07, 2005 at 12:26:11AM -0700, Guy Harris wrote:
> >Personally, I never use CRTDLL.LIB/MSVCRT.LIB, because in this case I'm
> >forced to distribute my application with tons of DLL (MSVC*.DLL), which are
> >far bigger than the application itself.
> >Therefore, I'm always using the standar
Fulvio Risso wrote:
Personally, I never use CRTDLL.LIB/MSVCRT.LIB, because in this case I'm
forced to distribute my application with tons of DLL (MSVC*.DLL), which are
far bigger than the application itself.
Therefore, I'm always using the standard C library.
The difference here, for the benef
