Skip site navigation (1)Skip section navigation (2)
Date:      Fri, 28 Oct 2011 23:08:05 -0500
From:      Larry Rosenman <ler@lerctr.org>
To:        Stanislav Sedov <stas@FreeBSD.org>
Cc:        freebsd-current@freebsd.org, FreeBSD PR followup <bug-followup@FreeBSD.org>
Subject:   Re: bin/162135: remote syslog not logging
Message-ID:  <4EAB7C25.3020309@lerctr.org>
In-Reply-To: <20111028210110.3afca748.stas@FreeBSD.org>
References:  <20111028201614.5e340538.stas@FreeBSD.org> <93b1f542-2d5a-4295-8c64-32889ce1ae63@email.android.com> <20111028210110.3afca748.stas@FreeBSD.org>

next in thread | previous in thread | raw e-mail | index | archive | help
On 10/28/2011 11:01 PM, Stanislav Sedov wrote:
> On Fri, 28 Oct 2011 22:20:27 -0500
> Larry Rosenman<ler@lerctr.org>  mentioned:
>
>> See the options lines
>>
>> -a 192.168.200.0/24
>>
>> And the Cable modem is sending to 514.
>>
> Please, read the manpage description for the '-a' switch.
> The modem is sending to the port 514, it's true, but it's not
> using port 514 as a source.  And you didn't specify the source
> service in the '-a' command line argument parameter.
>
AHA! That's the issue.  I changed the -a to:
syslogd_flags="-n -a 192.168.200.0/24:*"

and we now get the messages logged.

THANK YOU.





Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4EAB7C25.3020309>