From owner-freebsd-net@freebsd.org Mon Nov 27 17:25:53 2017 Return-Path: Delivered-To: freebsd-net@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 197BADBA264 for ; Mon, 27 Nov 2017 17:25:53 +0000 (UTC) (envelope-from jmg@gold.funkthat.com) Received: from gold.funkthat.com (gate2.funkthat.com [208.87.223.18]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "gate2.funkthat.com", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 588F47C20F for ; Mon, 27 Nov 2017 17:25:51 +0000 (UTC) (envelope-from jmg@gold.funkthat.com) Received: from gold.funkthat.com (localhost [127.0.0.1]) by gold.funkthat.com (8.15.2/8.15.2) with ESMTPS id vARHPfAN034118 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Mon, 27 Nov 2017 09:25:41 -0800 (PST) (envelope-from jmg@gold.funkthat.com) Received: (from jmg@localhost) by gold.funkthat.com (8.15.2/8.15.2/Submit) id vARHPeXp034106; Mon, 27 Nov 2017 09:25:40 -0800 (PST) (envelope-from jmg) Date: Mon, 27 Nov 2017 09:25:40 -0800 From: John-Mark Gurney To: Michal =?iso-8859-1?Q?Bucht=EDk?= Cc: freebsd-net@freebsd.org Subject: Re: vlans + bridging is "interesting" Message-ID: <20171127172540.GX42467@funkthat.com> Mail-Followup-To: Michal =?iso-8859-1?Q?Bucht=EDk?= , freebsd-net@freebsd.org References: <20171125014755.GN42467@funkthat.com> <7b55197b-8f9d-6a54-3db4-70d4fc52abd0@borsice.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <7b55197b-8f9d-6a54-3db4-70d4fc52abd0@borsice.net> X-Operating-System: FreeBSD 11.0-RELEASE-p7 amd64 X-PGP-Fingerprint: D87A 235F FB71 1F3F 55B7 ED9B D5FF 5A51 C0AC 3D65 X-Files: The truth is out there X-URL: https://www.funkthat.com/ X-Resume: https://www.funkthat.com/~jmg/resume.html X-TipJar: bitcoin:13Qmb6AeTgQecazTWph4XasEsP7nGRbAPE X-to-the-FBI-CIA-and-NSA: HI! HOW YA DOIN? can i haz chizburger? User-Agent: Mutt/1.6.1 (2016-04-27) X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.4.3 (gold.funkthat.com [127.0.0.1]); Mon, 27 Nov 2017 09:25:41 -0800 (PST) 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: Mon, 27 Nov 2017 17:25:53 -0000 Michal Buchtk wrote this message on Sat, Nov 25, 2017 at 10:32 +0100: > maybe i don't understand you needs, but why do you create bridge0 and > add local ip's to it?. Because I want/need to be able to run VM's also on em0's untagged domain. > When you would like to see untaged packets on VM, to this simple setup: > keep em0 as "trunk" interface > create interface em0.14 > create bridge14 and add to it interfaces tap0 and em0.14 > add local ip to bridge14 > > ifconfig em0.14 create > ifconfig em0.14 up > ifconfig bridge14 create > ifconfig bridge14 addm tap0 addm em0.14 > ifconfig bridge14 up > ifconfig bridge14 > > then your VM will can communicate (untagged) with your host system, and > you will see tagged packets on em0 (and untagged on em0.14 of course) Yes, and that prevents me running some of my VM's that I want to be able to... > Dne 25.11.2017 v 2:47 John-Mark Gurney napsal(a): > > Hello, > > > > I decided to try to run some bhyve VM's on my machine and bridge > > them to a guest vlan on my main interface. I also want to support > > running bhyve VM's on the untagged part of the interface as well > > (this is the key problem as I'll describe later). > > > > I configure it as you'd expect. Bridge the main interface em0, and > > put the local IP's on the bridge0. Then I added an interface em0.14 > > that untags packets from em0, and added it to bridge1 along w/ a tap0 > > for the VM. This does not work. Packet goes out and comes back and > > is observed on em0, but never appears on either em0.14 or bridge1. > > > > After seeing: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=139268 > > > > I decide to look on bridge0, and see the tagged vlan packet on that > > interface. I attempted to add bridge0 as the vlandev for em0.14, but > > that doesn't work: > > #ifconfig em0.14 vlan 14 vlandev bridge0 > > ifconfig: SIOCSETVLAN: Protocol not supported > > > > So, I did finally get things working by using epair. I added an epair > > to the bridge, and that allows me to untag the packet, and pass on to > > bridge1. > > > > I have not attempted to use the patch in 139268, but if people think > > it is an acceptable solution (with patch, if I set LINK0, it should work > > w/ original configuration), I'll test and commit the patch. > > > > Otherwise, please submit another fix. -- John-Mark Gurney Voice: +1 415 225 5579 "All that I will do, has been done, All that I have, has not."