From owner-freebsd-net@freebsd.org Sun Apr 29 19:11:25 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 C2C67FB58E1 for ; Sun, 29 Apr 2018 19:11:24 +0000 (UTC) (envelope-from b.hawks123@gmail.com) Received: from mail-qk0-x230.google.com (mail-qk0-x230.google.com [IPv6:2607:f8b0:400d:c09::230]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 53F9F79030; Sun, 29 Apr 2018 19:11:24 +0000 (UTC) (envelope-from b.hawks123@gmail.com) Received: by mail-qk0-x230.google.com with SMTP id x22so5247081qkb.12; Sun, 29 Apr 2018 12:11:24 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=Mlq50f2zDklUP4+FbTQmRsrC3yVZVMSXsX9iJJqKRwY=; b=seR0tuP/TSvbyEKR36RbKdMjUS4lNuDHC9d6P7Hmk2deBlPZ2vy6ijOI2lvC3WWecm MbFvd2W0Rz+xqVuLiG19mBXYSA+Uq71djumw4X3zTPBhkRUjevAWEmhHXdBQRcjwX8OZ 63gpQI+Pqrrh8XZ00swNkEThc4N2+BS5dNn7s9au41wpZ950oaM7691j0dvHwGL17uM4 6BGX1Oivy5Bc42gWtcq58TvG6WXlcJ/MQyXDqGP9R1XWUmQ4CYyocLDa2RUKnqplJ27C QlxNBwl4T20a5/U4lRG+At0f99M1n1ny7fEpKRD30HcDy756o/cMEt3kIZ2z5RRmC0nk dTpw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=Mlq50f2zDklUP4+FbTQmRsrC3yVZVMSXsX9iJJqKRwY=; b=CGq3EQWWai21xTd0LcjdRLhk2naIjawTcTGz8N//8qU5mHgn2tyzvGN5JrAbxP8Oau /sd7XdZF7sHeeSdmfNP4XPhA5L8bUuWNbRnE6wBBFnS+E2OfXYTCB+Ncc2HY+m3JxMuC 8B61Aoovbkl8QALAq0oqS3MhCfkJZczXuIzjLl6UwcyUvHj3CC5obvlRcreNNvOqQraZ QsSpdznrCYyDzmkxo0zLM5yPFJWTGnLDsxhbhwiPtL2YVx2I84zO0V9ZIolrHox/Kh+b HfTgNBnQNN+w7NTSSTB73xRFFbaCVGcsi85cVzZZ9kTTAun24NrZoEwl9dIsTovGMaJ0 UV0w== X-Gm-Message-State: ALQs6tBdpBHgVAz8Ts7rfXZGwc/OPQG0S5Ty325e2WlWNjjWon0/rIfL OPTvbqs7wp0Co14bZ0m++O+04piT9utJ9krKIsMUqA== X-Google-Smtp-Source: AB8JxZrLpqRdbWNHDCJp2E2tH37C0OEx4sJup2q1b5x67HtSmw6/co7HiukGOmgPAo96upDnly70LUcqsgxXGvgiQ54= X-Received: by 10.55.19.149 with SMTP id 21mr8180381qkt.253.1525029083644; Sun, 29 Apr 2018 12:11:23 -0700 (PDT) MIME-Version: 1.0 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> In-Reply-To: From: Abdullah Date: Sun, 29 Apr 2018 19:11:13 +0000 Message-ID: Subject: Re: NETGRAPH- bridge vlans using netgraph help To: Julian Elischer Cc: Eugene Grosbein , Freebsd-net@freebsd.org Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.25 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 19:11:25 -0000 >and read this: >https://people.freebsd.org/~julian/netgraph.htm Will look into it too, thanks Julian. Regards Abdullah On Sun, Apr 29, 2018, 21:41 Julian Elischer wrote: > 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" > > > >