From owner-freebsd-net@freebsd.org Sat Apr 28 13:16: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 506B9FAEC3D for ; Sat, 28 Apr 2018 13:16:16 +0000 (UTC) (envelope-from ab.tariq90@gmail.com) Received: from mail-io0-x229.google.com (mail-io0-x229.google.com [IPv6:2607:f8b0:4001:c06::229]) (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 BFE2A822BA for ; Sat, 28 Apr 2018 13:16:15 +0000 (UTC) (envelope-from ab.tariq90@gmail.com) Received: by mail-io0-x229.google.com with SMTP id d11-v6so5522861iof.11 for ; Sat, 28 Apr 2018 06:16:15 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=1lJEXsRxHc0Yw2GYxz+AcUPmWjEOIRtPqt03Ndp2Mmw=; b=q0uvD+Jobbk60P3TzRI70xfgx1KnegzF5m22KUDOz1DJP2mS66NbeZFFGY6nSMb3+L CIQgP3Z5O5zhYlo4KhVhT4LZfIFV4vo4qDQzFqoiWCrD/x7FG6glG125jvES9jUMc6mn fKDfM0UJANq5MSeMRVPojoscKLf+UFwYrU8gsq0dd8CbAl0WtxjOvvDvZ7X4VbGdJYFm 0JzXyEJ32lHb4fCM4TkTyM8Eca1VCdj925VSMsZ25xUi7+6SFi4M0TtIWv+fcc4MQxAh jjDetxaU+U03aFcAPRMJE8VN9rlFP+p51qinsNJMnyB2tt9Qs4zB9Fowr6bWS7pTuZ09 9HTw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=1lJEXsRxHc0Yw2GYxz+AcUPmWjEOIRtPqt03Ndp2Mmw=; b=UF2EXSIsI/ULBPBZ5/xaULmxagBx7JYpefM6x/fkBmRT7NKQlhdvazK3R+vjcyMsvP a3K0tGp8OyPAJQPJ1AEXLMd6wevjAt0ZPpKeaNu37reAcIhxj+/8rs954m46blGhjmbB NBiAw4TRt1/SMRlw/x0x7apuWq8KeEiHSak7UXyQsv7AyAPLl5IXtmtX75J7a4YFqC0M WAFNGZVYl2D2lx9kWk9v3npyVAHUOgTVgAhUoGjhn3Z4sERDuY3INsYdeMUT+8AwQRSw mlGee5ni3lal9SmYqXdSdtBxWu/xWvOeusPFPVd5GKCY/NIKRCxBEC9oTpRTXsdzvxfr w6qQ== X-Gm-Message-State: ALQs6tAK068GFDwWNCS3eO/O+wE9iKZdTQ114VtWnZYBnoulak+F3lHR ighdbZ9GxujSeMnMI9OOVcCPh0tjl0jtx3vNavUiPUVS X-Google-Smtp-Source: AB8JxZqwEIO2MB4YrXIOl6ZJT2oSjYjuHYKF1xPTlxLcF86BfDgRQUzIku/bi9Bn6dTJBBQ13i7Z95EvVrA5BPGOjwM= X-Received: by 2002:a6b:ca82:: with SMTP id a124-v6mr6128918iog.104.1524921375179; Sat, 28 Apr 2018 06:16:15 -0700 (PDT) MIME-Version: 1.0 Received: by 2002:a02:4a93:0:0:0:0:0 with HTTP; Sat, 28 Apr 2018 06:16:14 -0700 (PDT) In-Reply-To: <5AE468D5.9030702@grosbein.net> 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: Abdullah Tariq Date: Sat, 28 Apr 2018 18:16:14 +0500 Message-ID: Subject: Re: NETGRAPH- bridge vlans using netgraph help To: Eugene Grosbein Cc: 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: Sat, 28 Apr 2018 13:16:16 -0000 > > 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. > > Sorry but getting a little confused here. Lets say i have 2 interfaces igb0, igb1 and i want them to have tagged traffic. I create vlan1 tagged 10 on igb0 and vlan2 tagged 10 on igb1 Next i create bridge0, assign vlan1 and vlan2 (no IPs on either the bridge, physical interface on VLANs)? PCs connected with igb0 and igb1 have similar IP config (e.g 192.168.10.1 and 192.168.10.2) Am i correct? On Sat, Apr 28, 2018 at 5: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. > >