Skip site navigation (1)Skip section navigation (2)
Date:      Fri, 16 Nov 2001 06:27:25 -0800 (PST)
From:      CJTT <cjtt@employees.org>
To:        Brooks Davis <brooks@one-eyed-alien.net>
Cc:        freebsd-net@FreeBSD.ORG
Subject:   Re: ti driver, vlan and tcpdump
Message-ID:  <Pine.GSO.3.96.1011116062425.21430B-100000@willers.employees.org>
In-Reply-To: <20011115134207.A26868@Odin.AC.HMC.Edu>

next in thread | previous in thread | raw e-mail | index | archive | help
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




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.GSO.3.96.1011116062425.21430B-100000>