Date: Sat, 10 Feb 2018 11:52:18 +0100 From: =?UTF-8?Q?Olivier_Cochard=2DLabb=C3=A9?= <olivier@freebsd.org> To: "O. Hartmann" <ohartmann@walstatt.org> Cc: freebsd-jail@freebsd.org, freebsd-current <freebsd-current@freebsd.org> Subject: Re: VIMAGE: vnet, epair and lots of jails on bridgeX - routing Message-ID: <CA%2Bq%2BTcqX_BxVpWRUorbnR_o_sBVxmryMND1jrw3UjYW2KQdg_w@mail.gmail.com> In-Reply-To: <20180210085248.7b9af104@thor.intern.walstatt.dynvpn.de> References: <20180208093052.7f5d7a98@freyja.zeit4.iv.bundesimmobilien.de> <20180209172259.1ec9b9f4@thor.intern.walstatt.dynvpn.de> <2D57FE3A-744A-4A44-B572-5338AB9E187D@lists.zabbadoz.net> <20180210085248.7b9af104@thor.intern.walstatt.dynvpn.de>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sat, Feb 10, 2018 at 8:52 AM, O. Hartmann <ohartmann@walstatt.org> wrote= : > > The moment any of the bridges gets an additional member epair interface > (so the bridge > has at least three members including the on reaching into the virtual > router jail) the > vbridge seems to operate unpredictable (to me). Pinging jails memeber of > that vbridge > are unreachable. > > =E2=80=8BFirst idea: Did you try with a more simple setup, like with just 3 jails members of one bridge ? =3D> I've tried it on a -head, and all 4 members (3 jails and the host) reach to communicate. Second idea: Can you check that all epairs have different MAC address each ?=E2=80=8B I hit this bug: https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D176671 Regards, Olivier
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CA%2Bq%2BTcqX_BxVpWRUorbnR_o_sBVxmryMND1jrw3UjYW2KQdg_w>