Date: Sun, 17 Jun 2018 16:58:11 +0200 From: Michael Grimm <trashcan@ellael.org> To: Gary Palmer <gpalmer@freebsd.org> Cc: freebsd-stable@FreeBSD.org Subject: Re: syslogd became silent between 11.2-PRERELEASE r334874 and r335282 Message-ID: <D517924E-5E18-4E3F-9AA5-F1F0572DF6E9@ellael.org> In-Reply-To: <20180617145029.GB44323@in-addr.com> References: <BDE2979C-728D-4B29-B105-03FFC9A31EF1@ellael.org> <20180617145029.GB44323@in-addr.com>
next in thread | previous in thread | raw e-mail | index | archive | help
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=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?D517924E-5E18-4E3F-9AA5-F1F0572DF6E9>