From owner-freebsd-net Fri Nov 16 6:27:51 2001 Delivered-To: freebsd-net@freebsd.org Received: from willers.employees.org (willers.employees.org [128.107.241.167]) by hub.freebsd.org (Postfix) with ESMTP id 452DE37B417 for ; Fri, 16 Nov 2001 06:27:50 -0800 (PST) Received: from localhost (cjtt@localhost) by willers.employees.org (8.11.5/8.11.5) with SMTP id fAGERQP22022; Fri, 16 Nov 2001 06:27:26 -0800 (PST) Date: Fri, 16 Nov 2001 06:27:25 -0800 (PST) From: CJTT To: Brooks Davis Cc: freebsd-net@FreeBSD.ORG Subject: Re: ti driver, vlan and tcpdump In-Reply-To: <20011115134207.A26868@Odin.AC.HMC.Edu> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-net@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org On Thu, 15 Nov 2001, Brooks Davis wrote: > For the moment, on stable hosts, that will work. Driver vlan support is > no longer optional in current and that change will be MFC'd just as soon > as I get it tested. The right answer is probably to modify the > VLAN_INPUT_TAG macro to do the bpf stuff. (I'll temporarily remove the VLAN support from the kernel). But when this is MFC'd, what will I need to do in order to continue seeing all traffic on the main interface (while using libpcap (tcpdump))? Will the VLAN_INPUT_TAG macro just handle it automatically? This is important for our protocol testing. We use IPDIVERT, libpcap, and libnet for lots of our tools. It saves us lot of money. Thanks, To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-net" in the body of the message