From owner-freebsd-net@freebsd.org Sat Apr 28 12:10:24 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 B40BAFAD31C for ; Sat, 28 Apr 2018 12:10:24 +0000 (UTC) (envelope-from ab.tariq90@gmail.com) Received: from mail-io0-x231.google.com (mail-io0-x231.google.com [IPv6:2607:f8b0:4001:c06::231]) (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 427117591F for ; Sat, 28 Apr 2018 12:10:24 +0000 (UTC) (envelope-from ab.tariq90@gmail.com) Received: by mail-io0-x231.google.com with SMTP id f21-v6so5416876iob.13 for ; Sat, 28 Apr 2018 05:10:24 -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=IjJu6EXc/X7sI6CC9HOMJfEtxbWKDNlS1Rdr1Kc1xd0=; b=jNwLj4h/kr4aLw7+KKD+KKosI+iHUiCC+YHrBAkMfg3xs1XEIXoqp8sxw4ezK1PULE NiAdVJS3Wb1iVP/3pvac3XFxdUZdwsLvklfR4/0uO+ISeTITwUIQloYmrpxxmJiWLy2d cOZCfiIZXLGKfeQqBACgVh3d81F8vOKkMCI1QuMLm5w1fGzUHMqz0N+riBp7r7YQtEyD FcMLQEfUgcjQbSRuXDRwDv04M2ExGVTsRldKTS0DlLw2K4mQEnKL3U/Tn1YhGdWa665J syNXkf91TSpHdwgQQzfXo3ipEpzIv6OWA+4Ex+RqiqVJHEilGpiXZwi409hVziJAL2C8 98yA== 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=IjJu6EXc/X7sI6CC9HOMJfEtxbWKDNlS1Rdr1Kc1xd0=; b=gqrleyaOz9ZqSo/slyMlSDdgDu2yeuA7CaGuHLSge3sKUfRz1jCH+GQYoqdF0xOMpJ 3P5/DKO2+sTefMUZld0MOPTxG9ogeKmkmo9K+DgwaeqbGxdH9Mp+Wyng5eR2mWniv48Q hvh3Q9NNpgERlsZPWHAGDjwL48pu+bVXH3ln90yd44/fiiGa9OuxsHwCJ5Vk6imEIHrn wIVtCRxS0iVfV2wyw6vO2h9ayiEUIvxQPRxqpz4L/7vJ6CoCOhdtiKWA/VIUE/VqE4Ks d4y28De1C7pnXMV8IHq6YdP6th92nmK7Z2xFWsIoIAgOtus2MuBLq+nP9f8YUnPhsgNs zKyw== X-Gm-Message-State: ALQs6tBxOQr6LqwqRLcEqm8Qz+eY7HwbEmdKE3rkYZNGAKlmI/CO5LbJ xH1u2BytdXIG0/4iwL3gNC4y3+S5Ezql3lfvK8foK83a X-Google-Smtp-Source: AB8JxZrVzTAAaPmqq/Yq5oXH6bN8DjYacsdBL7s9GhAhQinANkvyGrkRjf2pVW3oliFaRNXpJocHS8lSSiWaBGfrLd0= X-Received: by 2002:a6b:9509:: with SMTP id x9-v6mr5851317iod.35.1524917423641; Sat, 28 Apr 2018 05:10:23 -0700 (PDT) MIME-Version: 1.0 Received: by 2002:a02:4a93:0:0:0:0:0 with HTTP; Sat, 28 Apr 2018 05:10:23 -0700 (PDT) In-Reply-To: <5AE44ADD.7020302@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> From: Abdullah Tariq Date: Sat, 28 Apr 2018 17:10:23 +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" Content-Transfer-Encoding: quoted-printable 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 12:10:24 -0000 > > You are still ignoring requests to not top-post and I'm getting tired to > fix it for you. > I may just stop responding. > Apologies again, last i thought i had replied to all after your first pointing out=F0=9F=98=B7 If you really want to bridge 802.1q trunks, you should be stating so from > the beginning. > Sorry if i couldnt make you understand properly. 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? If not, can you please give some instructions/guidelines for ng_vlan+ng_bridge? Thanks On Sat, Apr 28, 2018 at 3:20 PM, Eugene Grosbein wrote= : > 28.04.2018 16:26, Abdullah wrote: > > You are still ignoring requests to not top-post and I'm getting tired to > fix it for you. > I may just stop responding. > > >> You still top-posting. Please don't. > >> It is possible to replicate *behaviour* but not configuration styl= e. > >> Unless you have real embedded switching chip in your system like > many ARM or MIPS-based routers do, > >> in which case you can use etherswitch(4) and etherswitchcfg(8) to > create vlans and configure > >> ports of such chip similar to L2 switches. > > > Configuration style doesn't really matter. > > I am trying to figure out how to make tagged traffic talk in a bridge. > > I have always had good support from bsd people over the last 4 5 years > since i started using it, maybe it's time to add something to it :) > > What gives me hope is that linux (cumulus linux, openswitch, ONL) are > doing so, i dont see why BSD can't do it. I haven't searched much other b= sd > flavors though. > > Traffic of virtual lan (vlan) is not the same as tagged traffic, you know= . > You described a task where all vlan's ports are untagged and this is > easily doable > by bridging NIC interfaces without creation of syntetic vlan interface > that is useless in case of untagged-only ports. > > If you really want to bridge 802.1q trunks, you should be stating so from > the beginning. > if_bridge(8) does not support tagged frames currently. > > It is generally bad idea to build full-blown switch out of FreeBSD unless > you have mentioned > companion switching chip. 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. > >