From owner-freebsd-bugs@freebsd.org Wed Apr 14 14:56:36 2021 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 00CA55DCA0F for ; Wed, 14 Apr 2021 14:56:36 +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 4FL5CR6T7lz3MhB for ; Wed, 14 Apr 2021 14:56:35 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: by mailman.nyi.freebsd.org (Postfix) id DE1F45DC910; Wed, 14 Apr 2021 14:56:35 +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 DDE715DCA0E for ; Wed, 14 Apr 2021 14:56:35 +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 "R3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4FL5CR5ss8z3Mm3 for ; Wed, 14 Apr 2021 14:56:35 +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 BCA101FDAD for ; Wed, 14 Apr 2021 14:56:35 +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 13EEuZPT052611 for ; Wed, 14 Apr 2021 14:56:35 GMT (envelope-from bugzilla-noreply@freebsd.org) Received: (from www@localhost) by kenobi.freebsd.org (8.15.2/8.15.2/Submit) id 13EEuZvb052610 for bugs@FreeBSD.org; Wed, 14 Apr 2021 14:56:35 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 255054] jng fails to run ngctl msg vtnet0: setpromisc 1 Date: Wed, 14 Apr 2021 14:56:36 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: misc X-Bugzilla-Version: 13.0-STABLE X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Some People X-Bugzilla-Who: timf@puroto.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.34 Precedence: list List-Id: Bug reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 14 Apr 2021 14:56:36 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D255054 Bug ID: 255054 Summary: jng fails to run ngctl msg vtnet0: setpromisc 1 Product: Base System Version: 13.0-STABLE Hardware: Any OS: Any Status: New Severity: Affects Some People Priority: --- Component: misc Assignee: bugs@FreeBSD.org Reporter: timf@puroto.org Having recently upgraded to 13.0-STABLE, I found that none of my jng-enabled jails were coming up after boot. root@puroto:/ # service jail start pupuru Starting jails: cannot start jail "pupuru": ngctl: send msg: Operation not supported jail: pupuru: jng bridge pupuru vtnet0: failed . root@puroto:/ # In this case the jails.conf entry was: pupuru { exec.prestart +=3D "jng bridge pupuru vtnet0"; exec.poststop +=3D "jng shutdown pupuru"; } Digging into what jng was doing, we were trying to switch the parent interf= ace to promiscuous mode, failing, and then bailing out: # ngctl msg vtnet0: setpromisc 1 ngctl: send msg: Operation not supported Just commenting out that line in jng seemed to be sufficient, though I don't know what side effects that might have. My jails all came up ok after that, and = were at least able to send/recv traffic, ping the jail host, etc. 306 # Set promiscuous mode and don't overwrite src addr 307 # ngctl msg $iface: setpromisc 1 || return 308 ngctl msg $iface: setautosrc 0 || return I checked that my copy of /usr/sbin/jng wasn't significantly different to t= he one being shipped in /usr/share/examles/jails. --=20 You are receiving this mail because: You are the assignee for the bug.=