From owner-freebsd-net@FreeBSD.ORG  Fri May 12 19:18:35 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 [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id 5002416B8C6
	for <freebsd-net@freebsd.org>; Fri, 12 May 2006 19:18:35 +0000 (UTC)
	(envelope-from ambrisko@ambrisko.com)
Received: from mail.ambrisko.com (mail.ambrisko.com [64.174.51.43])
	by mx1.FreeBSD.org (Postfix) with ESMTP id 675DD43D6D
	for <freebsd-net@freebsd.org>; Fri, 12 May 2006 19:18:30 +0000 (GMT)
	(envelope-from ambrisko@ambrisko.com)
Received: from server2.ambrisko.com (HELO www.ambrisko.com) ([192.168.1.2])
	by mail.ambrisko.com with ESMTP; 12 May 2006 12:17:32 -0700
Received: from ambrisko.com (localhost [127.0.0.1])
	by www.ambrisko.com (8.12.11/8.12.11) with ESMTP id k4CJITf8090719;
	Fri, 12 May 2006 12:18:29 -0700 (PDT)
	(envelope-from ambrisko@ambrisko.com)
Received: (from ambrisko@localhost)
	by ambrisko.com (8.12.11/8.12.11/Submit) id k4CJITpR090718;
	Fri, 12 May 2006 12:18:29 -0700 (PDT) (envelope-from ambrisko)
From: Doug Ambrisko <ambrisko@ambrisko.com>
Message-Id: <200605121918.k4CJITpR090718@ambrisko.com>
In-Reply-To: <4464BCA0.3010500@ispro.net>
To: Evren Yurtesen <yurtesen@ispro.net>
Date: Fri, 12 May 2006 12:18:29 -0700 (PDT)
X-Mailer: ELM [version 2.4ME+ PL94b (25)]
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset=US-ASCII
Cc: freebsd-net@freebsd.org
Subject: Re: vlan/bridge problems..
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, 12 May 2006 19:18:37 -0000

Evren Yurtesen writes:
| I tried to bridge vlan with ethernet but I am having troubles.
| 
| net.link.ether.bridge_cfg: fxp0:2,fxp3:2,fxp2:3,vlan0:3
| net.link.ether.bridge: 1
| net.link.ether.bridge_ipfw: 0
| net.link.ether.bridge_ipf: 0
| net.link.ether.bridge_ipfw_drop: 0
| net.link.ether.bridge_ipfw_collisions: 0
| 
| fxp0 - fxp3 bridge works fine
| vlan0 is attached to fxp3 (trunk)
| 
| vlan0 - fxp2 bridge doesnt work! I can ping IP of fxp2 but not to any 
| host connected to fxp2.
| 
| Can this be because I am using fxp3 as a normal interface + a vlan trunk 
| at the same time?

It wouldn't work for me since the if_vlan device call the device driver's 
output mechanism direct and the SW input path would ignore handling of VLAN
packets ... or atleast this used to be issues.  My machine's that I needed
this for are patched locally to make it work.

I don't know the current state of this.  It gets to be a bit of
a mess re-injection the packet into the stack on output with loops etc.
The ordering of post netgraph/bridge has some issues.  It probably
should be tagged and use that to prevent loops.

Doug A.