[tcpdump-workers] [PATCH] Updated time-based dumpfile rotation (against 3.9.1)

Hi All - I've recently rewritten the patch I submitted last November which allows tcpdump to automagically rotate dump files based on some time in seconds specified by the -G argument. I rewrote the patch to have less impact on the tcpdump code in hopes that this patch will be better received. T

Re: [tcpdump-workers] lpcap not capturing non-accepted connections?

[EMAIL PROTECTED] wrote: > Heya everyone, I'm trying to build a port knocker for fun using pcap and > basic C > sockets. I've set up 10 sockets listenning on ports 4000-4010 but not actually > accepting. > > I then set up a pcap filter for port 4000 (just to test it) to see if it would > grab any

[tcpdump-workers] lpcap not capturing non-accepted connections?

Heya everyone, I'm trying to build a port knocker for fun using pcap and basic C sockets. I've set up 10 sockets listenning on ports 4000-4010 but not actually accepting. I then set up a pcap filter for port 4000 (just to test it) to see if it would grab anything. When I try to telnet to port 40

Re: [tcpdump-workers] pcap captures null packets?

Thanks! i JUST tried that and it is working fine now... appreciate the response. -Thinh On 7/19/05, Christian Kreibich <[EMAIL PROTECTED]> wrote: > and memcpy the packet data -- Thinh Ho University of Virginia Engineering School C: 571-594-1473 - This is the tcpdump-workers list. Visit https://

Re: [tcpdump-workers] pcap captures null packets?

Hi there, I'm not sure if it's the cause of the problem but you definitely need to copy out the values passed into packet_handler instead of assigning the pointers. You can just assign the pcap_pkthdr; in order to copy the packet data, obtain the caplen from the header, allocate a chunk of memory

[tcpdump-workers] pcap captures null packets?

Hello, I am writing a sniffer and storing the pakets in a vector of nodes. Is it possible to capture NULL packets? because I ran it over night to capture 1000 packets and when prompted to display the information of the packets from a specified source and destination ip, after scanning about 400 pac

Re: [tcpdump-workers] 64-bit pcap timestamp problems

Phil Wood wrote: I scanned through an ethereal-dev list of Auguest 1999 about 64-bit pcap timestamp problems. It appears that the consensus was such that pcap files written on 64 bit machines will not be readable on 32 bit machines and arsy-varsy. That was the consensus at the time in etherea