So it wasnt a problem in the code..
I think we can safely say that Doug was right..
Cheers
Sent from my iPad
On Oct 29, 2011, at 10:26 AM, Larry Rosenman wrote:
> We found the issue, I needed to add a :* to the end of the -a option
> addresses since the Cable modem is using anonymous ports fo
We found the issue, I needed to add a :* to the end of the -a option addresses
since the Cable modem is using anonymous ports for the source instead of 514.
I'm now getting the messages.
--
Sent from my Android phone with K-9 Mail. Please excuse my brevity.
Remko Lodder wrote:
On Oct 29, 2011
On Oct 29, 2011, at 4:59 AM, Larry Rosenman wrote:
> Since Doug Barton doesn't believe that the syslogd is running with the
> options, here's a ps to show that it is:
>
>
> root 65128 0.0 0.0 12216 1552 ?? Ss 10:02AM 0:01.17
> /usr/sbin/syslogd -n -a 192.168.200.10 -a 192.168
Since Doug Barton doesn't believe that the syslogd is running with the
options, here's a ps to show that it is:
root 65128 0.0 0.0 12216 1552 ?? Ss 10:02AM 0:01.17
/usr/sbin/syslogd -n -a 192.168.200.10 -a 192.168.200.0/24
ler 70268 0.0 0.0 14680 1608 0 S+9:58
Synopsis: remote syslog not logging
State-Changed-From-To: open->closed
State-Changed-By: dougb
State-Changed-When: Sat Oct 29 02:36:36 UTC 2011
State-Changed-Why:
This is something that needs to be reported on a mailing list first, probably
freebsd-questi...@freebsd.org. If you don't get a reso
>Number: 162135
>Category: bin
>Synopsis: remote syslog not logging
>Confidential: no
>Severity: non-critical
>Priority: low
>Responsible:freebsd-bugs
>State: open
>Quarter:
>Keywords:
>Date-Required:
>Class: sw-bug
>Submitter-
