Ed Maste wrote:
1) Add a new pcap API function pcap_set_bufsize that can be used
to set the size used for following pcap_open_live calls (by setting
a libpcap global variable).
The global variable is a bit ugly. If you're going to have API changes...
2) Add a new function like pcap_open_live that
Guy Harris wrote:
(Blah blah blah defeat duplicate detector blah blah blah once again I
forgot to send with my alum.mit.edu address in the from line blah blah
blah Thunderbird blah blah blah time to pester Bugzilla.)
Travis wrote:
Is it not correct that pcap_compile takes in a filter program wit
(Blah blah blah defeat duplicate detector blah blah blah once again I
forgot to send with my alum.mit.edu address in the from line blah blah
blah Thunderbird blah blah blah time to pester Bugzilla.)
Travis wrote:
Is it not correct that pcap_compile takes in a filter program with
tcpdump syntax?
(I just subscribed to the list so don't have the original
message to reply to.) I have some more comments on the recent
thread about the pcap buffer size code in pcap-bpf.c.
The code to try smaller and smaller buffer sizes until a valid size
is found has the following comment:
/*
Hello list,
Is it not correct that pcap_compile takes in a filter program with
tcpdump syntax? If so then why is it that when I try to compile the
program "host 129.244.241.XXX", where XXX is an actual number, does the
compile function fail on me? I'm assuming this is something really
stupid bu
CVS log entries from 12.10.2004 (Tue) 09:06:38 - 13.10.2004 (Wed) 09:06:32 GMT
=
Summary by authors
=
Author: hannes
File: tcpdump/nlpid.c; Revisions: 1.2
File: tcpdump/print-fr.c