From owner-freebsd-net@freebsd.org Sun Apr 29 16:41:16 2018 Return-Path: Delivered-To: freebsd-net@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 701D0FB17ED for ; Sun, 29 Apr 2018 16:41:16 +0000 (UTC) (envelope-from julian@freebsd.org) Received: from vps1.elischer.org (vps1.elischer.org [204.109.63.16]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "vps1.elischer.org", Issuer "CA Cert Signing Authority" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 057FF7883D for ; Sun, 29 Apr 2018 16:41:15 +0000 (UTC) (envelope-from julian@freebsd.org) Received: from Julian-MBP3.local (220-253-154-11.dyn.iinet.net.au [220.253.154.11]) (authenticated bits=0) by vps1.elischer.org (8.15.2/8.15.2) with ESMTPSA id w3TGf4fW095070 (version=TLSv1.2 cipher=DHE-RSA-AES128-SHA bits=128 verify=NO); Sun, 29 Apr 2018 09:41:07 -0700 (PDT) (envelope-from julian@freebsd.org) Subject: Re: NETGRAPH- bridge vlans using netgraph help To: Eugene Grosbein , Abdullah Tariq Cc: freebsd-net@freebsd.org References: <5AE216DC.7010905@grosbein.net> <5AE33513.1000001@grosbein.net> <5AE34754.6040905@grosbein.net> <5AE34CFA.7000207@grosbein.net> <5AE437C1.8010706@grosbein.net> <5AE44ADD.7020302@grosbein.net> <5AE468D5.9030702@grosbein.net> From: Julian Elischer Message-ID: Date: Mon, 30 Apr 2018 00:40:58 +0800 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.13; rv:52.0) Gecko/20100101 Thunderbird/52.7.0 MIME-Version: 1.0 In-Reply-To: <5AE468D5.9030702@grosbein.net> Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit Content-Language: en-US X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 29 Apr 2018 16:41:16 -0000 On 28/4/18 8:28 pm, Eugene Grosbein wrote: > 28.04.2018 19:10, Abdullah Tariq wrote: > >> However, we still have several ways to bridge tagged traffic >> by means of creation multiple bridges (one per vlan) or using ng_vlan+ng_bridge to do the same. >> >> bridge1 will contain vlan 1 >> bridge2 will containn vlan2 >> >> and bridge3 should have bridge1 and bridge2? > No, its simplier: single bridge contains all interfaces corresponting to ports of single vlan. > You can bridge plain igb* interfaces for untagged ports; or bridge interface igbX with interface vlanY > when one port carries untagged frames of vlan and another ports carries tagged frames of the same vlan; > or bridge interface vlans together when all of them carry tagged frames of the vlan. > >> If not, can you please give some instructions/guidelines for ng_vlan+ng_bridge? > I still think you should not dive into building complex netgraph structures > while the task can be solved simplier. But if you want to take that path, start by > reading man ng_vlan, man ng_ether, man ng_bridge and man ng_eiface and try examples therein. and read this: https://people.freebsd.org/~julian/netgraph.html > > _______________________________________________ > freebsd-net@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-net > To unsubscribe, send any mail to "freebsd-net-unsubscribe@freebsd.org" >