From owner-freebsd-stable@freebsd.org  Sun Jun 17 14:58:17 2018
Return-Path: <owner-freebsd-stable@freebsd.org>
Delivered-To: freebsd-stable@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 A044B102211E
 for <freebsd-stable@mailman.ysv.freebsd.org>;
 Sun, 17 Jun 2018 14:58:17 +0000 (UTC)
 (envelope-from trashcan@ellael.org)
Received: from mx1.enfer-du-nord.net (mx1.enfer-du-nord.net
 [IPv6:2001:41d0:302:1100::7:9a96])
 (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
 (Client did not present a certificate)
 by mx1.freebsd.org (Postfix) with ESMTPS id 2F94D71395;
 Sun, 17 Jun 2018 14:58:16 +0000 (UTC)
 (envelope-from trashcan@ellael.org)
Received: from [IPv6:2003:e9:7f3e:301:6061:d32e:91bf:aaae]
 (p200300E97F3E03016061D32E91BFAAAE.dip0.t-ipconnect.de
 [IPv6:2003:e9:7f3e:301:6061:d32e:91bf:aaae])
 (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
 (No client certificate requested)
 by mx1.enfer-du-nord.net (Postfix) with ESMTPSA id 417y5d0z7Pz8GY;
 Sun, 17 Jun 2018 16:58:13 +0200 (CEST)
X-Virus-Status: Clean
X-Virus-Scanned: clamav-milter 0.100.0 at mail.enfer-du-nord.net
Content-Type: text/plain;
	charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 11.4 \(3445.8.2\))
Subject: Re: syslogd became silent between 11.2-PRERELEASE r334874 and r335282
From: Michael Grimm <trashcan@ellael.org>
In-Reply-To: <20180617145029.GB44323@in-addr.com>
Date: Sun, 17 Jun 2018 16:58:11 +0200
Cc: freebsd-stable@FreeBSD.org
Content-Transfer-Encoding: quoted-printable
Message-Id: <D517924E-5E18-4E3F-9AA5-F1F0572DF6E9@ellael.org>
References: <BDE2979C-728D-4B29-B105-03FFC9A31EF1@ellael.org>
 <20180617145029.GB44323@in-addr.com>
To: Gary Palmer <gpalmer@freebsd.org>
X-Mailer: Apple Mail (2.3445.8.2)
X-Spam-Status: No, score=1.4 required=5.0 tests=RDNS_NONE,TW_VU autolearn=no
 autolearn_force=no version=3.4.1
X-Spam-Level: *
X-Spam-Checker-Version: SpamAssassin 3.4.1 (2015-04-28) on mail.mer-waases.lan
X-BeenThere: freebsd-stable@freebsd.org
X-Mailman-Version: 2.1.26
Precedence: list
List-Id: Production branch of FreeBSD source code <freebsd-stable.freebsd.org>
List-Unsubscribe: <https://lists.freebsd.org/mailman/options/freebsd-stable>, 
 <mailto:freebsd-stable-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-stable/>
List-Post: <mailto:freebsd-stable@freebsd.org>
List-Help: <mailto:freebsd-stable-request@freebsd.org?subject=help>
List-Subscribe: <https://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
 <mailto:freebsd-stable-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Sun, 17 Jun 2018 14:58:17 -0000

On 17. Jun 2018, at 16:50, Gary Palmer <gpalmer@freebsd.org> wrote:
> On Sun, Jun 17, 2018 at 04:27:33PM +0200, Michael Grimm wrote:

>> Host's syslogd can be reached from inside every jail, e.g.:
>>=20
>> 	jtest> nc -4vuw 1 10.x.y.z 514=20
>> 	Connection to 10.x.y.z 514 port [udp/syslog] succeeded!
>=20
> UDP is connectionless, so the client has no way of knowing if the
> connection succeeded or not.  If you put in port 515 I suspect you'd
> get the same result from your 'nc' attempt.

You are right :-)

> Is syslogd on the host running with '-s'?  If so, that'll stop it
> from accepting any remote log events.

No, syslogd at the host is running with the following flags only:
	syslogd_flags=3D"-vv -b 10.x.y.z -a 10.x.y.0/24"

All syslogd within jails (empty flags needed to prevent syslogd of =
opening sockets) ...
	syslogd_flags=3D""

=E2=80=A6 and /etc/syslog.conf with:
	*.*	@10.x.y.z

Regards,
Michael=