On Wed, Mar 31, 2010 at 11:00:25AM -0700, Guy Harris wrote:
>
> On Mar 31, 2010, at 9:15 AM, Michael Richardson wrote:
>
> > Two questions:
> > 1) is there anything preventing us from processing pflog
> > format pcap files on any system (i.e. a header I'm missing
> > on non-BSD system
> "Guy" == Guy Harris writes:
Guy> On Mar 31, 2010, at 6:41 AM, Wesley Shields wrote:
>> Looks like commit e8b523758959c1854689d71c7a4686c631e5501c broke
>> tcpdump on FreeBSD (and probably any other system with PF). The attached
>> patch fixes the build.
Guy> Checked in
On Mar 31, 2010, at 6:41 AM, Wesley Shields wrote:
> Looks like commit e8b523758959c1854689d71c7a4686c631e5501c broke
> tcpdump on FreeBSD (and probably any other system with PF). The attached
> patch fixes the build.
Checked into the main branch and, it appears, into the 4.1 branch - I did, in
On Mar 31, 2010, at 9:15 AM, Michael Richardson wrote:
> Two questions:
> 1) is there anything preventing us from processing pflog
> format pcap files on any system (i.e. a header I'm missing
> on non-BSD systems)?
The fact that the header for packets in a DLT_PFLOG file can be (and
> "Wesley" == Wesley Shields writes:
Wesley> Looks like commit e8b523758959c1854689d71c7a4686c631e5501c
Wesley> broke tcpdump on FreeBSD (and probably any other system with
Wesley> PF). The attached patch fixes the build.
Two questions:
1) is there anything preventing us from
Looks like commit e8b523758959c1854689d71c7a4686c631e5501c broke
tcpdump on FreeBSD (and probably any other system with PF). The attached
patch fixes the build.
-- WXS
--- ./print-pflog.c.orig 2010-03-31 00:12:46.197152894 -0400
+++ ./print-pflog.c 2010-03-31 00:13:00.429070083 -0400
@@ -42,6 +42,
