From owner-freebsd-net@FreeBSD.ORG  Fri Dec 22 01:14:13 2006
Return-Path: <owner-freebsd-net@FreeBSD.ORG>
X-Original-To: freebsd-net@freebsd.org
Delivered-To: freebsd-net@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52])
	by hub.freebsd.org (Postfix) with ESMTP id 9EABF16A412
	for <freebsd-net@freebsd.org>; Fri, 22 Dec 2006 01:14:13 +0000 (UTC)
	(envelope-from julian@elischer.org)
Received: from outH.internet-mail-service.net (outH.internet-mail-service.net
	[216.240.47.231])
	by mx1.freebsd.org (Postfix) with ESMTP id 8436213C469
	for <freebsd-net@freebsd.org>; Fri, 22 Dec 2006 01:14:13 +0000 (UTC)
	(envelope-from julian@elischer.org)
Received: from shell.idiom.com (HELO idiom.com) (216.240.47.20)
	by out.internet-mail-service.net (qpsmtpd/0.32) with ESMTP;
	Thu, 21 Dec 2006 16:44:19 -0800
Received: from [10.251.18.229] (nat.ironport.com [63.251.108.100])
	by idiom.com (8.12.11/8.12.11) with ESMTP id kBM10MT0082130
	for <freebsd-net@freebsd.org>; Thu, 21 Dec 2006 17:00:24 -0800 (PST)
	(envelope-from julian@elischer.org)
Message-ID: <458B2E19.2040708@elischer.org>
Date: Thu, 21 Dec 2006 17:00:09 -0800
From: Julian Elischer <julian@elischer.org>
User-Agent: Thunderbird 1.5.0.8 (Macintosh/20061025)
MIME-Version: 1.0
To: FreeBSD Net <freebsd-net@freebsd.org>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Subject: bridging ethernets containing vlans, 
X-BeenThere: freebsd-net@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Networking and TCP/IP with FreeBSD <freebsd-net.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-net>,
	<mailto:freebsd-net-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-net>
List-Post: <mailto:freebsd-net@freebsd.org>
List-Help: <mailto:freebsd-net-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-net>,
	<mailto:freebsd-net-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Fri, 22 Dec 2006 01:14:13 -0000

If I bridge two ethernets, one with HW_vlan tagging and the other 
without, and there are vlans active on that network, am I right in 
assuming that it requires that the two ethernets need to both have their
HW_vlan capabilities on or off, but that it won't work if they are mixed?

The bridging code seems to turn on and off promiscuous mode for the 
interfaces and bridge_mutecaps() seems to turn on the HX Checksup 
capacity, but there doesn't seem to be any code whereby the
VLAN tagging is enabled or disabled.

This means that bridging a HW-VLAN interface with one that
doesn't support HW vlans will result in just the base packet being
transmitted and the vlan header being dropped.

Am I reading this right?
shouldn't the function bridge_mutecaps() also turn off HW vlan handling?
and is it just a case of adding it to BRIDGE_IFCAPS_MASK?