From owner-freebsd-bugs Wed Jun 21 15: 0: 5 2000 Delivered-To: freebsd-bugs@freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.ORG [204.216.27.21]) by hub.freebsd.org (Postfix) with ESMTP id B280137B61E for ; Wed, 21 Jun 2000 15:00:02 -0700 (PDT) (envelope-from gnats@FreeBSD.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.9.3/8.9.2) id PAA81043; Wed, 21 Jun 2000 15:00:02 -0700 (PDT) (envelope-from gnats@FreeBSD.org) Date: Wed, 21 Jun 2000 15:00:02 -0700 (PDT) Message-Id: <200006212200.PAA81043@freefall.freebsd.org> To: freebsd-bugs@FreeBSD.org Cc: From: Udo Erdelhoff Subject: Re: bin/19377: tcpdump and tun-Device Reply-To: Udo Erdelhoff Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org The following reply was made to PR bin/19377; it has been noted by GNATS. From: Udo Erdelhoff To: freebsd-gnats-submit@FreeBSD.org Cc: Subject: Re: bin/19377: tcpdump and tun-Device Date: Wed, 21 Jun 2000 23:55:27 +0200 Some additional datapoints: - the problem also exists in both 4.0-RELEASE and RELENG-4 as of 08-JUN - "postive" filtering (e.g. tcpdump -i tun0 port foo) works as expected - Doing a tcpdump -i tun0 -w file and then tcpdump -r file not port foo show the same symptoms. Using the same commandline on a file captured from an ethernet device works as expected To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message