From owner-freebsd-bugs@freebsd.org Sat Dec 5 22:19:12 2020 Return-Path: Delivered-To: freebsd-bugs@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id EAD644A9D70 for ; Sat, 5 Dec 2020 22:19:12 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mailman.nyi.freebsd.org (mailman.nyi.freebsd.org [IPv6:2610:1c1:1:606c::50:13]) by mx1.freebsd.org (Postfix) with ESMTP id 4CpPB866vBz4lyw for ; Sat, 5 Dec 2020 22:19:12 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: by mailman.nyi.freebsd.org (Postfix) id D21B54A9D6F; Sat, 5 Dec 2020 22:19:12 +0000 (UTC) Delivered-To: bugs@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id D1E634A9BE9 for ; Sat, 5 Dec 2020 22:19:12 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from mxrelay.nyi.freebsd.org (mxrelay.nyi.freebsd.org [IPv6:2610:1c1:1:606c::19:3]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "mxrelay.nyi.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4CpPB85WPFz4lfJ for ; Sat, 5 Dec 2020 22:19:12 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2610:1c1:1:606c::50:1d]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (Client did not present a certificate) by mxrelay.nyi.freebsd.org (Postfix) with ESMTPS id B065525479 for ; Sat, 5 Dec 2020 22:19:12 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org ([127.0.1.5]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id 0B5MJCRL086588 for ; Sat, 5 Dec 2020 22:19:12 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id 0B5MJCdh086587 for bugs@FreeBSD.org; Sat, 5 Dec 2020 22:19:12 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 251624] jls is unable to list IP(s) of vnet jails. Date: Sat, 05 Dec 2020 22:19:12 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: bin X-Bugzilla-Version: 12.2-RELEASE X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Many People X-Bugzilla-Who: chris@open-systems.net 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.34 Precedence: list List-Id: Bug reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 05 Dec 2020 22:19:13 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D251624 Bug ID: 251624 Summary: jls is unable to list IP(s) of vnet jails. Product: Base System Version: 12.2-RELEASE Hardware: amd64 OS: Any Status: New Severity: Affects Many People Priority: --- Component: bin Assignee: bugs@FreeBSD.org Reporter: chris@open-systems.net Im quite certain the authors and those who have had their hands in the VNET code are aware of this issue. I just could not find any discussion about th= is or any explanation of what the issue is. So my hope is this winds up as a P= R, but also hopefully someone can chime in and post a link to a discussion abo= ut this or an explanation of the issue so I can understand the rabbit hole her= e. When creating a jail with vnet only and with vnet plus DHCP (using BastilleBSD), on 12.2-RELEASE r366954, the jail's get created fine. But jls= or jls -N do not display the IP of said created jails. This is an issue when you spin up a dozen, hundreds or a thousand vnet jails and do a 'jls' or 'jls -N' and get nothing returned for the IP. It makes us= ing jls and tooling built around it like BastilleBSD... difficult.=20 I looked at how SmartOS does the output of a 'list' command and with their 'vmadm list' you simply get back the primary or first interface IP of the z= one. With a 'vmadm get' you get a JSON array returned with every interface and IP attached to it from each zone.=20 I looked at jls.c and didn't see anything regarding this issue. And again, I couldn't find any discussion about this or a blog entry anywhere. This has = to be pretty widely known, I would just like to understand what the issue is so hopefully someone familiar with the code can chime in and explain the issue. Either way I have at least filed a PR for the record. Thank you for any explanation of the issue provided. --=20 You are receiving this mail because: You are the assignee for the bug.=