From owner-freebsd-hackers@FreeBSD.ORG  Tue Nov 23 01:30:59 2004
Return-Path: <owner-freebsd-hackers@FreeBSD.ORG>
Delivered-To: freebsd-hackers@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id 6ECA116A4CE
	for <freebsd-hackers@freebsd.org>;
	Tue, 23 Nov 2004 01:30:59 +0000 (GMT)
Received: from mail.otel.net (gw3.OTEL.net [212.36.8.151])
	by mx1.FreeBSD.org (Postfix) with ESMTP id B4C1643D5F
	for <freebsd-hackers@freebsd.org>;
	Tue, 23 Nov 2004 01:30:58 +0000 (GMT)	(envelope-from tbyte@OTEL.net)
Received: from dragon.otel.net ([212.36.8.135])
	by mail.otel.net with esmtp (Exim 4.30; FreeBSD)
	id 1CWPWC-0003LU-7o
	for freebsd-hackers@freebsd.org; Tue, 23 Nov 2004 03:30:56 +0200
Message-ID: <41A292D8.4050904@OTEL.net>
Date: Tue, 23 Nov 2004 03:31:04 +0200
From: Iasen Kostov <tbyte@OTEL.net>
User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.7.3) Gecko/20041117
X-Accept-Language: bg, en-us, en
MIME-Version: 1.0
To: freebsd-hackers@freebsd.org
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Subject: setting promisc mode kills vlans on devices with hwtagging (em, re
 ...)
X-BeenThere: freebsd-hackers@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
List-Id: Technical Discussions relating to FreeBSD
	<freebsd-hackers.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-hackers>,
	<mailto:freebsd-hackers-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-hackers>
List-Post: <mailto:freebsd-hackers@freebsd.org>
List-Help: <mailto:freebsd-hackers-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-hackers>,
	<mailto:freebsd-hackers-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Tue, 23 Nov 2004 01:30:59 -0000

    Hi,
if you setup a vlan devices with parent one of emX or reX (this what I 
have at the moment)
which has hardware vlan tagging just try to run tcpdump (without -p) and 
the vlans will
die :). That doesn't happen with parent devices not supporting 
hwtagging. And this totally
excludes possibility to run a bridge over vlans with parent device which 
support hwtaggs.
And something else was observed with re driver - it is impossible to 
disable hwtaggs by
-vlanhwtag neither you can disable vlan mtu :).