CVS log entries from 17.11.2005 (Thu) 10:07:09 - 24.11.2005 (Thu) 05:04:15 GMT
=
Summary by authors
=
=
Log entries
===
Evan Hughes wrote:
Regarding return values: I'll make the changes that you suggested.
I'm using -3 to indicate that a stream [can't be seeked on]. Would it be
acceptable to create a define for that value? It's a pain to memorize
those negative values...
Yes, #defines for the various return
On Wed, 2005-11-23 at 23:49 +0100, David Rosal wrote:
> Gianluca Varenni wrote:
> > The minimum ethernet frame length is 64 bytes *if* you include the FCS.
> > Unfortunately, most of the network cards strip the FCS before the packet
> > reaches the host, so the actual minimum frame length that yo
David Rosal wrote:
Yes it does. Thanks.
But a question arises: If my network card is stripping the FCS (and it
seems to do so), may I suppose that this is done for all packets?
On that particular adapter, yes.
You can't suppose that it's done on all adapters on all platforms,
however; in pa
richard wrote:
I am using tcpdump version 3.8.3, with libpcap 0.8.3. This has
worked for me on various versions of solaris, aix, and linux,
but crashes when I use it in Fedora Linux
version 2.6.13-1.1532_FC4smp.
Perhaps there's a compiler bug in FC4. Libpcap isn't crashing on other
platforms
Gianluca Varenni wrote:
The minimum ethernet frame length is 64 bytes *if* you include the FCS.
Unfortunately, most of the network cards strip the FCS before the packet
reaches the host, so the actual minimum frame length that you see with
libpcap is actually 60 bytes.
Hope it helps
Yes it
On 11/22/05, Guy Harris <[EMAIL PROTECTED]> wrote:
> Evan Hughes wrote:
> >I can do some timings on the cost of the fgetpos(), but I don't
> > have a large number of platforms available to test on, just debian
> > boxes and windows machines.
> I could test on Solaris 7, assorted versions of Deb
Libpcap workers,
My copy of tcpdump is seg faulting whenever I use any packet
filter expression command line argument. Any simple filter,
like:
tcpdump host foo
or
tcpdump port 23
It crashes even if I use the no optimize -O flag.
Some version background:
I am using tcpdump version 3.8.3, with li
David Rosal wrote:
[ ... ]
But what's is very strange is that
everytime I make a capture session with tcpdump I get *many* packets of
60 bytes that are not originated in my own machine nor are them sent to it.
Here's an example of the output of tcpdump:
$ tcpdump -c5 '(host not 193.145.45.23
- Original Message -
From: "David Rosal" <[EMAIL PROTECTED]>
To:
Sent: Wednesday, November 23, 2005 5:26 AM
Subject: [tcpdump-workers] Paquets smaller than 64 bytes
Hello.
I'm monitoring an Ethernet link with tcpdump-3.9.4.
I've read that when packets are generated by the same machi
Hello.
I'm monitoring an Ethernet link with tcpdump-3.9.4.
I've read that when packets are generated by the same machine as tcpdump
is run, those packets may be smaller than the minimum ethernet frame
lenght, which is of 64 bytes. AFAIK, this is because the kernel "sends"
the packets to pcap
11 matches
Mail list logo
