From owner-freebsd-net Wed Jul 19 16: 8: 3 2000 Delivered-To: freebsd-net@freebsd.org Received: from prioris.im.pw.edu.pl (pf39.warszawa.sdi.tpnet.pl [213.25.209.39]) by hub.freebsd.org (Postfix) with ESMTP id 69B5437B824 for ; Wed, 19 Jul 2000 16:08:00 -0700 (PDT) (envelope-from zaks@prioris.im.pw.edu.pl) Received: by prioris.im.pw.edu.pl (Postfix, from userid 1000) id 46E1A6394E; Thu, 20 Jul 2000 01:07:44 +0200 (CEST) Content-MD5: 1e4beeb86459ecb5f370ceaf4ca248d2 From: Slawek Zak To: freebsd-net@freebsd.org Subject: tcpdump on tun0 strangeness Organization: Ministerstwo smierci na wojnie Date: 20 Jul 2000 01:07:43 +0200 Message-ID: <878zux7m80.fsf@localhost.localnet> Lines: 24 User-Agent: Gnus/5.0807 (Gnus v5.8.7) XEmacs/21.1 (Bryce Canyon) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I've found a strange bahaviour of tcpdump in 4.1-RC (and 4.0) when listening on tun0 interface. When I specify the protocol to filter, tcpdump shows only packets going out. Without the filter I see all the packets. # tcpdump -i tun0 Shows all packets when pinging any remote host # tcpdump -i tun0 icmp Shows only packets going out. # tcpdump -i fxp0 icmp (Ethernet link) Works just fine too. Any ideas?? -- `When any government, or any church for that matter, undertakes to say to its subjects, "This you may not read, this you must not see, this you are forbidden to know," the end result is tyranny and oppression no matter how holy the motives' -- Robert A Heinlein, "If this goes on --" Suavek Zak / PGP: finger://zaks@prioris.mini.pw.edu.pl To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message