Skip site navigation (1)Skip section navigation (2)
Date:      Tue, 23 Aug 2005 14:15:40 -0500
From:      Matthew Grooms <mgrooms@shrew.net>
To:        Pieter de Boer <pieter@thedarkside.nl>
Cc:        freebsd-net@freebsd.org
Subject:   Re: odd tcpdump output w/ 6.0-BETA2 ...
Message-ID:  <430B75DC.9050003@shrew.net>
In-Reply-To: <430B6785.7040209@thedarkside.nl>
References:  <430B5680.1060506@shrew.net> <430B6785.7040209@thedarkside.nl>

next in thread | previous in thread | raw e-mail | index | archive | help
Pieter de Boer wrote:
> Matthew Grooms wrote:
> 
> 
>>Is anyone else seeing this issue? I get useless output from tcpdump ( no
>>header or protocol decode ) but only when I specify a filter on the
>>command line.
> 
> 
>>listening on xl0, link-type EN10MB (Ethernet), capture size 96 bytes
>>11:33:32.920031 [|ether]
>>11:33:35.203998 [|ether]
> 
> 
> I've seen this too and heard from someone else with the same problem.
> Both 6.0-BETA2 systems. I upgraded mine to a newer version of 6.0-BETA2,
> using cvsup, but can't remember nor test (at least during this week) if
> that fixed the problem.
> 
> Both tcpdump and libpcap are in contrib/, but ENOCLUE if only those
> sources (together with the kernel-sources and the makefiles) would be
> enough to build a new tcpdump...
> 

Did you make modifications or are were you running GENERIC? The only 
modifications I made to my kernel were to disable IPV6 and to enable pf, 
pflog, ALTQ and FAST_IPSEC.

Could someone with a stock BETA2 kernel try a tcpdump with a simple 
filter and see if it they get normal output?

-Matthew



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?430B75DC.9050003>