From owner-freebsd-amd64@FreeBSD.ORG Tue Dec 14 07:48:44 2004 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id F239616A4CE for ; Tue, 14 Dec 2004 07:48:44 +0000 (GMT) Received: from sophia3.e-shell.net (sophia3.e-shell.net [64.246.46.12]) by mx1.FreeBSD.org (Postfix) with ESMTP id C7E5443D6B for ; Tue, 14 Dec 2004 07:48:44 +0000 (GMT) (envelope-from loox@e-shell.net) Received: from dsl-201-137-127-114.prod-infinitum.com.mx (unknown [201.137.127.114]) by sophia3.e-shell.net (Postfix) with ESMTP id AE39F656833; Tue, 14 Dec 2004 01:47:46 -0600 (CST) From: Axel Gonzalez To: "Conrad J. Sabatier" Date: Tue, 14 Dec 2004 01:48:42 -0600 User-Agent: KMail/1.7.1 References: <200412132302.50539.loox@e-shell.net> <20041214000810.1472b6a5@dolphin.local.net> In-Reply-To: <20041214000810.1472b6a5@dolphin.local.net> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200412140148.43099.loox@e-shell.net> cc: freebsd-amd64@freebsd.org Subject: Re: tcpdump port xx bug ? - only happens on interface connected to pppoe X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 14 Dec 2004 07:48:45 -0000 Ok, found the 'bug'.. maybe it helps someone ;) It only happens on the interface connected to DSL modem note the: > tcpdump: WARNING: rl0: no IPv4 address assigned when accessing the interface rl0 and specify a port, it can't capture packets, but it can capture packets with no problems on tun0 (tun0 is the interface that actually has the ip) still is weird how it can capture packages when no port is specified, but then maybe its the way its suposed to be :) On Tuesday 14 December 2004 00:08, Conrad J. Sabatier wrote: > On Mon, 13 Dec 2004 23:02:50 -0600, Axel Gonzalez wrote: > > is anyone able to confirm or deny this (before a PR is filled)? > > > > # tcpdump port xx > > > > doesnt seem to work: > > > > su-2.05b# tcpdump port http > > tcpdump: WARNING: rl0: no IPv4 address assigned > > tcpdump: verbose output suppressed, use -v or -vv for full protocol > > decode listening on rl0, link-type EN10MB (Ethernet), capture size 68 > > bytes ^C > > 0 packets captured > > 503 packets received by filter > > 0 packets dropped by kernel > > > > > > if no port is specified, it works fine: > > > > su-2.05b# tcpdump | grep freeb > > tcpdump: WARNING: rl0: no IPv4 address assigned > > tcpdump: verbose output suppressed, use -v or -vv for full protocol > > decode listening on rl0, link-type EN10MB (Ethernet), capture size 68 > > bytes 22:57:30.768184 PPPoE [ses 0xc744] IP > > xxxx.prod-infinitum.com.mx.55842 > www.freebsd.org.http: S > > 564552288:564552288(0) win 65535 > > 22:57:30.843127 PPPoE [ses 0xc744] IP www.freebsd.org.http > > > xxx.prod-infinitum.com.mx.55842: S 3276387435:3276387435(0) ack 564552289 > > win 57344 > > > > [... tons of this] > > > > > > system: > > FreeBSD moonlight.e-shell.net 5.3-STABLE FreeBSD 5.3-STABLE #0: Sun Dec > > 5 22:57:54 CST 2004 > > root@moonlight.e-shell.net:/usr/obj/usr/src/sys/LXAMD64 amd64 > > Works fine under CURRENT. Perhaps you should try updating your sources and > rebuilding.