From owner-freebsd-current@freebsd.org Sat Jun 2 23:07:57 2018 Return-Path: Delivered-To: freebsd-current@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 8E416FF4DA5 for ; Sat, 2 Jun 2018 23:07:57 +0000 (UTC) (envelope-from truckman@FreeBSD.org) Received: from mx2.catspoiler.org (mx2.catspoiler.org [IPv6:2607:f740:16::d18]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "amnesiac", Issuer "amnesiac" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 289E77FB2B for ; Sat, 2 Jun 2018 23:07:57 +0000 (UTC) (envelope-from truckman@FreeBSD.org) Received: from gw.catspoiler.org ([76.212.85.177]) by mx2.catspoiler.org (8.15.2/8.15.2) with ESMTPS id w52N9feb097346 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=FAIL); Sat, 2 Jun 2018 23:09:43 GMT (envelope-from truckman@FreeBSD.org) Received: from mousie.catspoiler.org (mousie.catspoiler.org [192.168.101.2]) by gw.catspoiler.org (8.15.2/8.15.2) with ESMTPS id w52N0GiH088740 (version=TLSv1 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Sat, 2 Jun 2018 16:07:48 -0700 (PDT) (envelope-from truckman@FreeBSD.org) Date: Sat, 2 Jun 2018 16:07:48 -0700 (PDT) From: Don Lewis Subject: Re: rndc: connect failed: 127.0.0.1#953: permission denied To: "O. Hartmann" cc: FreeBSD CURRENT In-Reply-To: <20180602091203.146839ea@thor.intern.walstatt.dynvpn.de> Message-ID: References: <20180602091203.146839ea@thor.intern.walstatt.dynvpn.de> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=us-ascii Content-Disposition: INLINE X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.26 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 02 Jun 2018 23:07:57 -0000 On 2 Jun, O. Hartmann wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA512 > > On CURRENT, running on an APU as router/firewall service, out of the blue after an update > I receive this weird message when trying to restart "named" (BIND 9.12, latest from the > ports): > > service named restart > rndc: connect failed: 127.0.0.1#953: > permission denied rndc failed, trying kill: Waiting for PIDS: 871. > > Searching the net reveals that possible access rights issues could cause this problem, > but I do not see any. Does somebody see such problems, too and does have a solution? Do you have a firewall rule that blocks sending to UDP port 953 on 127.0.0.1?