Guy Harris wrote:
This leads me to another question. I've seen recommendations to roll
your
own structs for IP/TCP headers, hinting that there might be slight
differences
in the definitions between platforms. Is this really true?
Yes. For example, if I remember correctly, not all platforms' "
Robert Lowe wrote:
Well, I was reporting this from memory. Let me back up a bit. When I first
looked at pcap, I went through Tim Carsten's tutorial, referenced from the
tcpdump.org website. Using that code (sniffer.c) on Linux with a downed eth0
i/f (forcing the dev to any) results in very weird
Guy Harris wrote:
On Dec 1, 2004, at 3:31 PM, Robert Lowe wrote:
In testing a small app using libpcap, I noticed differences in
behaviour when
using the loopback interface vs. using a hardware interface. In
particular,
it seems the packets coming in over the loopback interface are still
in host
On Dec 1, 2004, at 3:31 PM, Robert Lowe wrote:
In testing a small app using libpcap, I noticed differences in
behaviour when
using the loopback interface vs. using a hardware interface. In
particular,
it seems the packets coming in over the loopback interface are still
in host
byte order (littl
Hi!
In testing a small app using libpcap, I noticed differences in behaviour when
using the loopback interface vs. using a hardware interface. In particular,
it seems the packets coming in over the loopback interface are still in host
byte order (little endian, in this case). Is that typical, or
