Date: Tue, 23 Aug 2005 22:15:55 +0200 From: Pieter de Boer <pieter@thedarkside.nl> To: Matthew Grooms <mgrooms@shrew.net> Cc: freebsd-net@freebsd.org Subject: Re: odd tcpdump output w/ 6.0-BETA2 ... Message-ID: <430B83FB.6020008@thedarkside.nl> In-Reply-To: <430B75DC.9050003@shrew.net> References: <430B5680.1060506@shrew.net> <430B6785.7040209@thedarkside.nl> <430B75DC.9050003@shrew.net>
next in thread | previous in thread | raw e-mail | index | archive | help
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. > 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. I've made quite some changes, yes: removing drivers I don't need, adding pf.. Doubt it's a problem in the kernel configuration, sounds more like a problem in libpcap or bpf.. -- Pieter
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?430B83FB.6020008>