Re: [tcpdump-workers] pcap_data vs payload

On 07/10/2011 05:10 PM, Alokat wrote: > On 07/10/11 00:53, Guy Harris wrote: >> On Jul 9, 2011, at 7:50 PM, Alokat wrote: >> >>> Just for sure: >>> >>> *Ethernet packet* >>> >>> means a layer 2 (OSI / ISO model) packet right? >> Yes. >> - >> This is the tcpdump-workers list. >> Visit https://cod.sa

Re: [tcpdump-workers] Proposal for a new web design

a copy of the old site at http://www.tcpdump.org/oldweb. Regards, Luis. On 09/19/2010 08:32 PM, Luis MartinGarcia. wrote: > Hi, > > I've trying to redesign tcpdump's web page. I've desgined a simple > logo and changed the aspect of the whole web. I admit it's no

[tcpdump-workers] [Pcap] setsockopt(optval) points to uninitialised byte(s)

tation specific). Also, I have tracked down the problem to pcap-linux.c::pcap_setfilter_linux_common(). By adding a simple memset() call, I am able to get rid of the message. I attach a patch that fixes this issue. Please, consider integrating it into mainstream. Regards, Luis MartinGarcia. diff --git a

[tcpdump-workers] Proposal for a new web design

Hi, I've trying to redesign tcpdump's web page. I've desgined a simple logo and changed the aspect of the whole web. I admit it's not the most elegant and clean design but I hope it looks decent enough. I've uploaded a copy to . Please, check it out and

Re: [tcpdump-workers] tcp sequence and ack number with libpcap

On 08/19/2010 04:23 PM, Andrej van der Zee wrote: > Hi, > > I am trying to get the TCP sequence and ack number of TCP packets. Somehow I > get different values than "tcpdump -vv" does. The numbers are way too big > all the time. Source and destination ports are just fine. Below the relevant > code.

Re: [tcpdump-workers] 4.1.1/1.1.1

27;t they be relative? > > I logged in to fix this but I see you've done it already. I saw that the link to "Packet Capture With libpcap and other Low Level Network Tricks." was broken, so I've pointed it to another copy of the same resource. I also added a link to