freebsd stable - Apr 2014 - Syslogd question

Hi, possibly quick and perhaps subtle question about syslogd. I have a
machine that is a syslog server (receives network logs from other hosts),
but also a syslog client (sends logs over the network to yet another syslog
server).

How can I configure the server to locally log the network connections it
receives, but NOT to forward these remotely received messages?

In the old days, this was called "hopping." I think this kind of
forwarding
of remote entries was PREVENTED by default. It had to be enabled with the
"-h" (hop) option.

Anyone know how I can prevent syslogd from hopping/remote forwarding
nowadays?

-- 
James Welcher

On Apr 19, 2014, at 18:24, James Welcher <jwelcher at gmail.com> wrote:
[?]
> How can I configure the server to locally log the network connections it
> receives, but NOT to forward these remotely received messages?
[?]
> Anyone know how I can prevent syslogd from hopping/remote forwarding
> nowadays?
From syslog.conf(5):
> A hostname specification of the form `#+hostname' or `+hostname'
means the following blocks will be applied to messages received from
thespecified hostname.  Alternatively, the hostname specification
`#-hostname' or `-hostname' causes the following blocks to be applied to
messages from any host but the one specified.  If the hostname is given as
`@', the local hostname will be used.  As for program specifications,
multiple comma-separated values may be specified for hostname specifications.
	http://www.freebsd.org/cgi/man.cgi?query=syslog.conf

So you should try something like at the end:

	# Send messages from localhost to remotelogger.
	+@
	*.*		@remotelog.example.com

See also:

	https://www.freebsd.org/doc/handbook/configtuning-syslog.html