From nobody Tue Apr 26 10:08:31 2022 X-Original-To: freebsd-net@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 1C6CA1A9C25F for ; Tue, 26 Apr 2022 10:08:43 +0000 (UTC) (envelope-from benoitc@enki-multimedia.eu) Received: from mail-4323.proton.ch (mail-4323.proton.ch [185.70.43.23]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "protonmail.com", Issuer "R3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4KnczG22QZz4SJj for ; Tue, 26 Apr 2022 10:08:41 +0000 (UTC) (envelope-from benoitc@enki-multimedia.eu) Date: Tue, 26 Apr 2022 10:08:31 +0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=enki-multimedia.eu; s=protonmail; t=1650967713; bh=gDf1M9Jb62nrmZjjiEy0olxLABfdG+vTQZrHJTmgGyM=; h=Date:To:From:Cc:Reply-To:Subject:Message-ID:In-Reply-To: References:Feedback-ID:From:To:Cc:Date:Subject:Reply-To: Feedback-ID:Message-ID; b=Y2wbNVRYJK7EG+3FTKvqO6Fq/K7k2BiTLvqhNOCGpVbWODIgJwXIZKpSEcC0f1df4 4hkD94pjJRiM53axDySfXI0RLOf6s7l8OCYdWDXB+jYJU/xC/IIBuRkZv/0ztrHdAN mL1fiuEp9YXMmf7pSGqjBgRia1HP9wgBtfhmVmSI= To: Lutz Donnerhacke From: Benoit Chesneau Cc: "Patrick M. Hausen" , "freebsd-net@FreeBSD.org" Reply-To: Benoit Chesneau Subject: Re: how to bridge "native" vlan? Message-ID: In-Reply-To: <20220423212002.GC3774@belenus.iks-jena.de> References: <8E5C5DFB-B029-4B32-A67B-D09042ACCEE3@punkt.de> <20220423212002.GC3774@belenus.iks-jena.de> Feedback-ID: 9066678:user:proton List-Id: Networking and TCP/IP with FreeBSD List-Archive: https://lists.freebsd.org/archives/freebsd-net List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-net@freebsd.org MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-Rspamd-Queue-Id: 4KnczG22QZz4SJj X-Spamd-Bar: - Authentication-Results: mx1.freebsd.org; dkim=pass header.d=enki-multimedia.eu header.s=protonmail header.b=Y2wbNVRY; dmarc=pass (policy=none) header.from=enki-multimedia.eu; spf=pass (mx1.freebsd.org: domain of benoitc@enki-multimedia.eu designates 185.70.43.23 as permitted sender) smtp.mailfrom=benoitc@enki-multimedia.eu X-Spamd-Result: default: False [-1.37 / 15.00]; HAS_REPLYTO(0.00)[benoitc@enki-multimedia.eu]; TO_DN_EQ_ADDR_SOME(0.00)[]; R_DKIM_ALLOW(-0.20)[enki-multimedia.eu:s=protonmail]; REPLYTO_EQ_FROM(0.00)[]; FROM_HAS_DN(0.00)[]; RCPT_COUNT_THREE(0.00)[3]; TO_DN_SOME(0.00)[]; R_SPF_ALLOW(-0.20)[+ip4:185.70.43.0/24]; MIME_GOOD(-0.10)[text/plain]; NEURAL_SPAM_SHORT(0.59)[0.593]; ARC_NA(0.00)[]; NEURAL_HAM_LONG(-1.00)[-1.000]; TO_MATCH_ENVRCPT_SOME(0.00)[]; DKIM_TRACE(0.00)[enki-multimedia.eu:+]; DMARC_POLICY_ALLOW(-0.50)[enki-multimedia.eu,none]; NEURAL_HAM_MEDIUM(-0.96)[-0.962]; MLMMJ_DEST(0.00)[freebsd-net]; RCVD_COUNT_ZERO(0.00)[0]; FROM_EQ_ENVFROM(0.00)[]; MIME_TRACE(0.00)[0:+]; SUBJECT_ENDS_QUESTION(1.00)[]; ASN(0.00)[asn:62371, ipnet:185.70.43.0/24, country:CH]; MID_RHS_MATCH_FROM(0.00)[] X-ThisMailContainsUnwantedMimeParts: N I am trying `mkpeer vlan0: bridge 100`but so fat it is returningan error. Should I crea= te the node first? Beno=C3=AEt Chesneau Sent with ProtonMail secure email. ------- Original Message ------- On Saturday, April 23rd, 2022 at 23:20, Lutz Donnerhacke wrote: > On Thu, Apr 21, 2022 at 02:11:54PM +0200, Patrick M. Hausen wrote: > > > > Am 21.04.2022 um 11:29 schrieb Benoit Chesneau benoitc@enki-multimedi= a.eu: > > > I have an interface on which multiple vlans are connected. I would li= ke to bridge the vlan 100 and 200 but also have a bridge for the "native" v= lan 1. I Can setup a bridge for vlan 100 and 200 the way below I think but = how to create a bridge for the "native" vlan? > > > > I don't have any experience with netgraph but I do know that > > you cannot do that with if_bridge(4). If you make the physical > > interface the member of a bridge, you cannot use additional > > VLANs on that interface, anymore. > > > > Does anybody know if the same restriction applies to ng_bridge(4)? > > > ng_bridge does not inspect the ethertypes only the mac addresses of the f= rames. > So you can split the VLANs using ng_vlan and connect them to the three br= idges: > > : mkpeer em0: vlan lower downstream > : name em0:lower vlan0 > : mkpeer vlan0: bridge 100 0 > : mkpeer vlan0: bridge 200 0 > : mkpeer vlan0: bridge nomatch 0 > : msg vlan0: addfilter { vid=3D100 hook=3D"100" } > : msg vlan0: addfilter { vid=3D200 hook=3D"200" } > : name vlan0:100 bridge100 > : name vlan0:200 bridge200 > > : mkpeer em1: vlan lower downstream > : name em1:lower vlan1 > : connect vlan1: bridge100: 100 1 > : connect vlan1: bridge200: 200 1 > : connect vlan1: bridge_untagged: nomatch 1 > : msg vlan1: addfilter { vid=3D100 hook=3D"100" } > : msg vlan1: addfilter { vid=3D200 hook=3D"200" } > > : mkpeer em2: vlan lower downstream > : name em2:lower vlan2 > : connect vlan2: bridge100: 100 2 > : connect vlan2: bridge200: 200 2 > : connect vlan2: bridge_untagged: nomatch 2 > : msg vlan2: addfilter { vid=3D100 hook=3D"100" } > : msg vlan2: addfilter { vid=3D200 hook=3D"200" }