Re: odd tcpdump output w/ 6.0-BETA2 ...
From: Pieter de Boer (pieter_at_thedarkside.nl)
Date: 08/23/05
- Previous message: Brooks Davis: "Re: [Fwd: assigning an address to ng_fec(4) iface causes panic]"
- In reply to: Matthew Grooms: "odd tcpdump output w/ 6.0-BETA2 ..."
- Next in thread: Matthew Grooms: "Re: odd tcpdump output w/ 6.0-BETA2 ..."
- Reply: Matthew Grooms: "Re: odd tcpdump output w/ 6.0-BETA2 ..."
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Date: Tue, 23 Aug 2005 20:14:29 +0200 To: Matthew Grooms <mgrooms@shrew.net>
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...
-- Pieter _______________________________________________ freebsd-net@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to "freebsd-net-unsubscribe@freebsd.org"
- Previous message: Brooks Davis: "Re: [Fwd: assigning an address to ng_fec(4) iface causes panic]"
- In reply to: Matthew Grooms: "odd tcpdump output w/ 6.0-BETA2 ..."
- Next in thread: Matthew Grooms: "Re: odd tcpdump output w/ 6.0-BETA2 ..."
- Reply: Matthew Grooms: "Re: odd tcpdump output w/ 6.0-BETA2 ..."
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Relevant Pages
|
|