Date: Mon, 19 Jun 2000 17:46:58 +0200 (CEST) From: Udo Erdelhoff <ue@nathan.ruhr.de> To: FreeBSD-gnats-submit@freebsd.org Subject: bin/19377: tcpdump and tun-Device Message-ID: <200006191546.RAA08024@nathan.ruhr.de>
next in thread | raw e-mail | index | archive | help
>Number: 19377 >Category: bin >Synopsis: tcpdump -i tun0 not port/host x shows incoming traffic for that host/port >Confidential: no >Severity: non-critical >Priority: medium >Responsible: freebsd-bugs >State: open >Quarter: >Keywords: >Date-Required: >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Mon Jun 19 08:50:01 PDT 2000 >Closed-Date: >Last-Modified: >Originator: Udo Erdelhoff >Release: FreeBSD 5.0-CURRENT i386 >Organization: private User >Environment: -current as of 18-JUN-2000 buildworld/installworld/new kernel ppp-connections over PPPoE and "conventional" modems with and without nat >Description: According to manpage, ``tcpdump not port X'' should not display traffic from or to that port. Likewise, ``tcpdump not host X'' should not display traffic from or to that host. tcpdump works "as advertised" when I'm snooping on a conventional interface (tested with bofh ed and fxp). If I'm sniffing on the tun device, tcpdump will still capture and display the incoming traffic. Using ``tcpdump not ( port X ) '' or ``tcpdump not ( src port X )'' doesn't change anything. >How-To-Repeat: use tcpdump not port X on a tun device with traffic for that port >Fix: >Release-Note: >Audit-Trail: >Unformatted: To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200006191546.RAA08024>