From owner-freebsd-stable@FreeBSD.ORG Sat Mar 4 13:36:19 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 12FDE16A420 for ; Sat, 4 Mar 2006 13:36:19 +0000 (GMT) (envelope-from mv@roq.com) Received: from p4.roq.com (ns1.ecoms.com [207.44.130.137]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7A15843D55 for ; Sat, 4 Mar 2006 13:36:18 +0000 (GMT) (envelope-from mv@roq.com) Received: from p4.roq.com (localhost.roq.com [127.0.0.1]) by p4.roq.com (Postfix) with ESMTP id 6F9874CAB0 for ; Sat, 4 Mar 2006 13:36:20 +0000 (GMT) Received: from [192.168.0.6] (ppp157-158.static.internode.on.net [150.101.157.158]) by p4.roq.com (Postfix) with ESMTP id C8C444CA4C for ; Sat, 4 Mar 2006 13:36:19 +0000 (GMT) Message-ID: <440997D1.8070002@roq.com> Date: Sun, 05 Mar 2006 00:36:17 +1100 From: Michael Vince User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.7.12) Gecko/20060213 X-Accept-Language: en-us, en MIME-Version: 1.0 To: freebsd-stable@freebsd.org Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: ClamAV using ClamSMTP Subject: 6-stable and Tcpdump problems X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 04 Mar 2006 13:36:19 -0000 I am using the latest FreeBSD 6-stable and I am still having trouble dumping tcpdump in clear text data. In FreeBSD 5.x using 'tcpdump -A -s 0 -i sk0' I would always give me a full screen Ascii dump of current network data to the screen but now it just shows everything in Hex. I submitted a send-pr on this sometime around 6.0 release but it never got anywhere. If you use the same command on 5.x it works fine. I found the closest thing I can get is using tcpdump -XX -s 0 -i sk0 which dumps both Hex and Acsii anything with the '-A' which is normally the important flag always results in Hex dumps. Installing ngrep from ports and doing 'ngrep -d sk0' gives me the result I want but I have found over time that ngrep often fails to work depending on when I track 6-stable, I would prefer to use tcpdump always working. Can any one agree with me there is a bug here? I have the same result on multiple machines. Cheers, Mike