From owner-freebsd-bugs@freebsd.org Fri Sep 28 07:50:50 2018 Return-Path: Delivered-To: freebsd-bugs@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 E457B10A8ECD for ; Fri, 28 Sep 2018 07:50:49 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id 2600489CBF for ; Fri, 28 Sep 2018 07:50:48 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: by mailman.ysv.freebsd.org (Postfix) id EA97A10A8ECB; Fri, 28 Sep 2018 07:50:47 +0000 (UTC) Delivered-To: bugs@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 C888210A8ECA for ; Fri, 28 Sep 2018 07:50:47 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mxrelay.ysv.freebsd.org (mxrelay.ysv.freebsd.org [IPv6:2001:1900:2254:206a::19:3]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mxrelay.ysv.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 7E29A89C43 for ; Fri, 28 Sep 2018 07:50:46 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mxrelay.ysv.freebsd.org (Postfix) with ESMTPS id 44C091840 for ; Fri, 28 Sep 2018 07:50:45 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id w8S7oj4m026948 for ; Fri, 28 Sep 2018 07:50:45 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id w8S7ojqr026947 for bugs@FreeBSD.org; Fri, 28 Sep 2018 07:50:45 GMT (envelope-from bugzilla-noreply@freebsd.org) X-Authentication-Warning: kenobi.freebsd.org: www set sender to bugzilla-noreply@freebsd.org using -f From: bugzilla-noreply@freebsd.org To: bugs@FreeBSD.org Subject: [Bug 231773] Nested jails: "IPv4 addresses clash" Date: Fri, 28 Sep 2018 07:50:45 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: CURRENT X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Some People X-Bugzilla-Who: kp@freebsd.org X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: bugs@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: bug_id short_desc product version rep_platform op_sys bug_status bug_severity priority component assigned_to reporter Message-ID: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-bugs@freebsd.org X-Mailman-Version: 2.1.27 Precedence: list List-Id: Bug reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 28 Sep 2018 07:50:50 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D231773 Bug ID: 231773 Summary: Nested jails: "IPv4 addresses clash" Product: Base System Version: CURRENT Hardware: Any OS: Any Status: New Severity: Affects Some People Priority: --- Component: kern Assignee: bugs@FreeBSD.org Reporter: kp@freebsd.org I recently upgraded one of my stable/11 machines to head (so what will be stable/12 soon), and ran into an issue with my nested jails setup. I run standard (i.e. non-vnet) jails, by assigning e.g. 172.16.4.2 to the parent jail, and starting a jail with that IP address from within that jail (basically, so I can delegate a jailed setup to other people). That used to work on stable/11, but now it failed with =E2=80=98IPv4 addres= ses clash=E2=80=99. To the extent that I understand the relevant code it looks like we try to verify that no other jail uses the address we=E2=80=99re trying to assign t= o the new jail. I think this block tries to ensure we start at either the host system or the vnet jail that=E2=80=99s hosting us. I suspect that=E2=80=99s just wrong, b= ecause we don=E2=80=99t do that if VIMAGE is not enabled (and there=E2=80=99s no need either, because = this check will already have been done for the parent jail). #ifdef VIMAGE for (; tppr !=3D &prison0; tppr =3D tppr->pr_parent) if (tppr->pr_flags & PR_VNET) break; #endif I can work around the problem by resetting 'tppr =3D ppr;' just before the FOREACH_PRISON_DESCENDANT() loop. (The IPv6 code has exactly the same problem.) Presumably the trigger for this is the enabling of VIMAGE in CURRENT. --=20 You are receiving this mail because: You are the assignee for the bug.=