From owner-freebsd-net@FreeBSD.ORG  Sat May 13 00:54:24 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 D452B16A636
	for <freebsd-net@freebsd.org>; Sat, 13 May 2006 00:54:24 +0000 (UTC)
	(envelope-from julian@elischer.org)
Received: from a50.ironport.com (a50.ironport.com [63.251.108.112])
	by mx1.FreeBSD.org (Postfix) with ESMTP id A1BA243D60
	for <freebsd-net@freebsd.org>; Sat, 13 May 2006 00:54:21 +0000 (GMT)
	(envelope-from julian@elischer.org)
Received: from unknown (HELO [10.251.19.131]) ([10.251.19.131])
	by a50.ironport.com with ESMTP; 12 May 2006 17:54:22 -0700
Message-ID: <44652E3C.4010704@elischer.org>
Date: Fri, 12 May 2006 17:54:20 -0700
From: Julian Elischer <julian@elischer.org>
User-Agent: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US;
	rv:1.7.13) Gecko/20060414
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Evren Yurtesen <yurtesen@ispro.net>
References: <200605121918.k4CJITpR090718@ambrisko.com>
	<44651F9B.9060709@ispro.net>
In-Reply-To: <44651F9B.9060709@ispro.net>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
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: Sat, 13 May 2006 00:54:25 -0000

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.
>>
>> Doug A.
>
>
> 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.

it may depend of whether you are doing hardware vlan tagging.

>
> Bridging works in 5.x/6.x but not the way that I explained here
>
> I cant bridge 1 interface and its vlan interface at the same time.
>
> Thanks,
> Evren
>
> _______________________________________________
> freebsd-net@freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-net
> To unsubscribe, send any mail to "freebsd-net-unsubscribe@freebsd.org"