From owner-freebsd-jail@freebsd.org Mon Feb 12 08:43:01 2018 Return-Path: Delivered-To: freebsd-jail@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 20216F03275; Mon, 12 Feb 2018 08:43:01 +0000 (UTC) (envelope-from ohartmann@walstatt.org) Received: from mout.gmx.net (mout.gmx.net [212.227.17.22]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "mout.gmx.net", Issuer "TeleSec ServerPass DE-2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 7AC4D872E3; Mon, 12 Feb 2018 08:43:00 +0000 (UTC) (envelope-from ohartmann@walstatt.org) Received: from freyja.zeit4.iv.bundesimmobilien.de ([87.138.105.249]) by mail.gmx.com (mrgmx102 [212.227.17.168]) with ESMTPSA (Nemesis) id 0MV30j-1fIwHx0WGT-00YRAT; Mon, 12 Feb 2018 09:37:48 +0100 Date: Mon, 12 Feb 2018 09:37:47 +0100 From: "O. Hartmann" To: Olivier =?ISO-8859-1?Q?Cochard-Labb=E9?= Cc: "O. Hartmann" , freebsd-jail@freebsd.org, freebsd-current Subject: Re: VIMAGE: vnet, epair and lots of jails on bridgeX - routing Message-ID: <20180212093747.20024e5f@freyja.zeit4.iv.bundesimmobilien.de> In-Reply-To: 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> Organization: Walstatt MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-Provags-ID: V03:K0:J4ZmmFcj0ZX5QXQJkpi7TzdFxvRbabQZ1FysksWkVhUYmlRgp6O zrx4I368uHPPzsha0adbaxqMvtzgD9uulwqZ91sbypYSTabJxkW9nuIeXjsxuz1d7/3Tkad Jei4HvJ2lN+WfeNKAjyf0pLissyNncVkUsEmhcMMQ61/mYM8la8oQh6OR2WA6u3kMZy/c5z 1ERXfSnxqRbNRzQY+Co4Q== X-UI-Out-Filterresults: notjunk:1;V01:K0:LtV6hFVb1Ek=:KGhazDgW8ZHrCpQtsvw7Gi V46jdJSTKS8FkGfeEPmfuyovX6koCCth7XagGf/a4AR8FvARvISmxIGDOSSsPRnOMj5SkwJhi cbs316mVFT9YIy4dx99ApcG/RN2L79aYetTPO4fJXKWXRytdd0S3p6eoUVIGfZjI/5tscAz+P b3nfGJcI3KFHK9pQMXEpgwTbv5U4ReWAMYQSUay53aY8d+/h5QaPzljcdcd+5dJ33EJWsQtF2 oODJQeTO1WvzzOUXm1X10tkeMsISUEM/sqzC8rvPDVQXSb3ZXZwURSOD5dP3eactUaC4V50bF wVhDcII5DLfpiAIWRDu6uGBWkiWQqmvLNaPoIv1xpFYv1P4cQNApZl3PyBgEloOXr1/yxbZrf 1uGjEZHvhPnWAuyC1jZcpa1xv6lzFzRjH4ma+wQkUypKTHexEJSLOBlEFv5LOA/Ll3uzRDLN3 lXqAvYKcmpSTXWv+UHK3WGLD0uvq8fW+vzi97Fn76chv1ZdgMDiUGdZM1x0zI4BYip+///+3l 9PR3Xl660QSMt11af0zFJK57vGIxHbO6JK5VyMSmIFr55KplNVVJ1xjjf9hE5CnTEIqNCjEgw 8z1DTvZuCFh4T1LyiL3Lk9oAIIKg9MkdLeE72xNoxhoz7hNNfo2G+8gGihCPsxrEQOcj/Ct5s w4w+8Pa6a9Gg3HwypfbEXumfVLgXOArxtwMSYXe3tDS0f9IeZK8aXEaMyIW8afxzm9l+FqYFg OJGfMRrbuQsXejUnMJlcfUvP4TJ8EJKwuKXniCbqAT9czoun9YWzC5dFIjHTLy/TAodX5H1bL mgfMMaiYnKDcM3424W+IeYDZbnDCTIpINcaZRiOhfq2u82QYgg= X-BeenThere: freebsd-jail@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: "Discussion about FreeBSD jail\(8\)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 12 Feb 2018 08:43:01 -0000 On Sat, 10 Feb 2018 11:52:18 +0100 Olivier Cochard-Labb=C3=A9 wrote: > On Sat, Feb 10, 2018 at 8:52 AM, O. Hartmann wro= te: >=20 > > > > 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. > > > > =20 > =E2=80=8BFirst idea: > Did you try with a more simple setup, like with just 3 jails members of o= ne > bridge ? > =3D> I've tried it on a -head, and all 4 members (3 jails and the host) = =20 > reach to communicate. >=20 > 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 Wow, that PR is from 2013(!) and it is still not solved? >=20 > Regards, >=20 > Olivier > _______________________________________________ > freebsd-current@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org"