Date: Fri, 4 Oct 2019 12:53:16 -0700 From: John-Mark Gurney <jmg@funkthat.com> To: "Alexander N. Lunev" <lan@zato.ru> Cc: freebsd-net@freebsd.org Subject: Re: VLAN+bridge problem [was: no network between jails and host with VNET on same interface] Message-ID: <20191004195316.GF96402@funkthat.com> In-Reply-To: <c327c5af-49c4-97a2-d3cb-1779e2ddfca2@zato.ru> References: <213f9284-5ddd-4dbc-6631-f8592efa2995@zato.ru> <4A3381ED-7C78-48E2-BD1F-45B7A4A930CE@lists.zabbadoz.net> <c327c5af-49c4-97a2-d3cb-1779e2ddfca2@zato.ru>
next in thread | previous in thread | raw e-mail | index | archive | help
Alexander N. Lunev via freebsd-net wrote this message on Thu, Oct 03, 2019 at 08:18 +0300:
> 02.10.2019 12:21, Bjoern A. Zeeb wrote:
> > My best guess would be to try to create the VLAN interface on the host
> > upon the bridge and not upon the physical interface. Can you try that
> > and see if that works?
>
> You mean like this?
>
> # ifconfig vlan222 create
> # ifconfig bridge1 create
> # ifconfig vlan222 vlandev bridge1 vlan 22
> ifconfig: SIOCSETVLAN: Protocol not supported
You can create an epair, add it to the bridge, and then vlan the epair
successfully. I've had to do that myself.
--
John-Mark Gurney Voice: +1 415 225 5579
"All that I will do, has been done, All that I have, has not."
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20191004195316.GF96402>