From owner-freebsd-net@FreeBSD.ORG Sat May 13 12:42:54 2006 Return-Path: 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 99DF416A402 for ; Sat, 13 May 2006 12:42:54 +0000 (UTC) (envelope-from yurtesen-dated-1148388170.e91b6b@ispro.net) Received: from smtp.ispro.net.tr (smtp.ispro.net.tr [62.244.220.178]) by mx1.FreeBSD.org (Postfix) with SMTP id 8BACD43D46 for ; Sat, 13 May 2006 12:42:53 +0000 (GMT) (envelope-from yurtesen-dated-1148388170.e91b6b@ispro.net) Received: (qmail 35176 invoked by uid 89); 13 May 2006 12:42:50 -0000 Received: from [80.221.144.106] (dsl-aur-fe90dd00-106.dhcp.inet.fi [80.221.144.106]) by localhost.my.domain (tmda-ofmipd) with ESMTP; Sat, 13 May 2006 15:42:45 +0300 (EEST) Message-ID: <4465D438.30506@ispro.net> Date: Sat, 13 May 2006 15:42:32 +0300 User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.12) Gecko/20050915 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Doug Ambrisko References: <200605130252.k4D2qRkl014903@ambrisko.com> In-Reply-To: <200605130252.k4D2qRkl014903@ambrisko.com> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Delivery-Agent: TMDA/1.0.3 (Seattle Slew) From: Evren Yurtesen X-Primary-Address: yurtesen@ispro.net.tr Cc: freebsd-net@freebsd.org, Julian Elischer 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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 13 May 2006 12:42:54 -0000 Doug Ambrisko wrote: > 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. I have to admit. ng_vlan seems much more difficult to use somehow. I have been going through the manual pages of netgraph but it somehow doesnt make sense to read bits and pieces. Not that I am blaming anybody for bad documentation, I need to sit down and read slowly :) I would prefer to use 5.x or 6.x instead. The fact is that my needs are so simple that it is not worth messing with netgraph (I think) Thanks anyway, Evren