From nobody@FreeBSD.org  Tue Sep 20 06:02:26 2005
Return-Path: <nobody@FreeBSD.org>
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id 8AB9916A41F
	for <freebsd-gnats-submit@FreeBSD.org>; Tue, 20 Sep 2005 06:02:26 +0000 (GMT)
	(envelope-from nobody@FreeBSD.org)
Received: from www.freebsd.org (www.freebsd.org [216.136.204.117])
	by mx1.FreeBSD.org (Postfix) with ESMTP id 5780943D55
	for <freebsd-gnats-submit@FreeBSD.org>; Tue, 20 Sep 2005 06:02:26 +0000 (GMT)
	(envelope-from nobody@FreeBSD.org)
Received: from www.freebsd.org (localhost [127.0.0.1])
	by www.freebsd.org (8.13.1/8.13.1) with ESMTP id j8K62Ooj082387
	for <freebsd-gnats-submit@FreeBSD.org>; Tue, 20 Sep 2005 06:02:24 GMT
	(envelope-from nobody@www.freebsd.org)
Received: (from nobody@localhost)
	by www.freebsd.org (8.13.1/8.13.1/Submit) id j8K62NrY082386;
	Tue, 20 Sep 2005 06:02:23 GMT
	(envelope-from nobody)
Message-Id: <200509200602.j8K62NrY082386@www.freebsd.org>
Date: Tue, 20 Sep 2005 06:02:23 GMT
From: Peter Jeremy <peter.jeremy@alcatel.com.au>
To: freebsd-gnats-submit@FreeBSD.org
Subject: bridge(4) does not work with VLAN trunks
X-Send-Pr-Version: www-2.3

>Number:         86361
>Category:       kern
>Synopsis:       [bridge] bridge(4) does not work with VLAN trunks
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    thompsa
>State:          closed
>Quarter:        
>Keywords:       
>Date-Required:  
>Class:          sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Tue Sep 20 06:10:05 GMT 2005
>Closed-Date:    Tue Oct 02 06:18:06 GMT 2007
>Last-Modified:  Tue Oct 02 06:18:06 GMT 2007
>Originator:     Peter Jeremy
>Release:        5.3-RELEASE-p5
>Organization:
Alcatel Australia Limited
>Environment:
FreeBSD aalp02.alcatel.com.au 5.3-RELEASE-p5 FreeBSD 5.3-RELEASE-p5 #4: Fri Feb 25 10:13:13 EST 2005     root@aalp02.alcatel.com.au:/var/obj/usr/src/sys/wansim  i386

The code has not changed in 7-CURRENT so the problem is still
presumably present.

>Description:
      bridge(4) includes code to detect network topology loops by
monitoring the MAC addresses that it sees on each bridged interface and
isolating the interface if the same source MAC address is seen on more
than one interface more than 10 times in 10 seconds.

In the case of a VLAN trunk, this check is incorrect as the MAC
addresses only need to be unique within each VLAN.  With protocols
like DECnet as well as the Cassini (ce) adaptor on Solaris, it is
normal for the same MAC address to appear in multiple VLANs,
potentially on different switches.  The behaviour of bridge(4) causes
the interfaces to be muted when this occurs.

like DECnet

simple 
>How-To-Repeat:
      Configure a host with the same MAC address on two or more NICs.
Connect the NICs to different VLANs configured on different switches.
Configure trunks on each switch containing all VLANs and connect them
to separate NICs on the FreeBSD box.

On the FreeBSD box, enable bridging between the two NICs (the NICs need
to be up but do not need to be configured with VLAN pseudo-interfaces).

Generate ethernet broadcast traffic (eg ARP requests) from all the test
interfaces and verify that the FreeBSD box reports loops.
>Fix:
      The simplest solution would seem to be to include provision for a
VLAN tag in bdg_hash_table.  This would need to be extracted from the
received packet and included in HASH_FN.
>Release-Note:
>Audit-Trail:
Responsible-Changed-From-To: freebsd-bugs->thompsa 
Responsible-Changed-By: thompsa 
Responsible-Changed-When: Tue Nov 8 20:33:56 GMT 2005 
Responsible-Changed-Why:  
Grab. 

http://www.freebsd.org/cgi/query-pr.cgi?pr=86361 
State-Changed-From-To: open->suspended 
State-Changed-By: thompsa 
State-Changed-When: Wed Apr 12 20:55:52 UTC 2006 
State-Changed-Why:  
The layer2 rationalization needs to happen first, merging the vlan code into ethersubr. 

http://www.freebsd.org/cgi/query-pr.cgi?pr=86361 

From: Andrew Thompson <thompsa@FreeBSD.org>
To: bug-followup@FreeBSD.org, peter.jeremy@alcatel.com.au
Cc:  
Subject: Re: kern/86361: [bridge] bridge(4) does not work with VLAN trunks
Date: Thu, 14 Jun 2007 07:02:52 +1200

 Hi Peter,
 
 This has been a long time coming but vlan bridging has finally been
 committed to HEAD. I dont know if you still care about this but you are
 more than welcome to test it out.
 
 
 regards,
 Andrew
State-Changed-From-To: suspended->closed 
State-Changed-By: thompsa 
State-Changed-When: Tue Oct 2 06:17:23 UTC 2007 
State-Changed-Why:  
Implemented in FreeBSD7, there is no plan to MFC. 

http://www.freebsd.org/cgi/query-pr.cgi?pr=86361 
>Unformatted:
