From owner-freebsd-net@FreeBSD.ORG  Sat May 13 02:52:29 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 10A2416A400
	for <freebsd-net@freebsd.org>; Sat, 13 May 2006 02:52:29 +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 9198943D48
	for <freebsd-net@freebsd.org>; Sat, 13 May 2006 02:52:28 +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 19:51:30 -0700
Received: from ambrisko.com (localhost [127.0.0.1])
	by www.ambrisko.com (8.12.11/8.12.11) with ESMTP id k4D2qReb014904;
	Fri, 12 May 2006 19:52:28 -0700 (PDT)
	(envelope-from ambrisko@ambrisko.com)
Received: (from ambrisko@localhost)
	by ambrisko.com (8.12.11/8.12.11/Submit) id k4D2qRkl014903;
	Fri, 12 May 2006 19:52:27 -0700 (PDT) (envelope-from ambrisko)
From: Doug Ambrisko <ambrisko@ambrisko.com>
Message-Id: <200605130252.k4D2qRkl014903@ambrisko.com>
In-Reply-To: <44652E3C.4010704@elischer.org>
To: Julian Elischer <julian@elischer.org>
Date: Fri, 12 May 2006 19:52:27 -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: Evren Yurtesen <yurtesen@ispro.net>, 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: Sat, 13 May 2006 02:52:29 -0000

Julian Elischer writes:
| Evren Yurtesen wrote:
| > Doug Ambrisko wrote:
| >
| >> 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.
| >
| > Well, I think vlans do not bridge on 4.x
| 
| that may or may not be true.. I think I have seen it working..
| I think netgraph bridging should work.

Only if doing netgraph vlan.  Not if_vlan.
 
| it may depend of whether you are doing hardware vlan tagging.

I disable HW vlan support.

Doug A.