Re: Syslog problem

2003-03-10 Thread Chuck Rock
nevermind, I realize that's not the source origination port, but it's destination port. There I go replying again I'll quit while I'm behind... Chuck On Sun, 9 Mar 2003, Dean Strik wrote: > Chuck Rock wrote: > > On Sat, 8 Mar 2003, Michael K. Smith wrote: > > > This might be your issue, bec

Re: Syslog problem

2003-03-10 Thread Chuck Rock
OK, this does make some sense reading it a few more times. I did include the output of snort which clearly shows the packets coming from port 514 (syslog) which this also says is the default accept port from the source address. This should have worked anyway, shouldn't it? I appreciate the help f

Re: Syslog problem

2003-03-09 Thread Dean Strik
Chuck Rock wrote: > On Sat, 8 Mar 2003, Michael K. Smith wrote: > > This might be your issue, because you haven't specified the service after > > you subnet. Try the following: > > > > /usr/sbin/syslogd -a 207.206.185.1/27:* -a 209.83.132.1/27:* > > Accordifn to the man page, that just specifies w

Re: Syslog problem

2003-03-08 Thread Chuck Rock
Well, that seemed to work. I don't know why, but it did. Thank you! Chuck On Sat, 8 Mar 2003, Michael K. Smith wrote: > Hello Chuck: > > On Sat, 8 Mar 2003, Chuck Rock wrote: > > > For the last few versions of FreeBSD, I have not been able to get my syslog > > to log my dial-up pool from my Cis

Re: Syslog problem

2003-03-08 Thread Chuck Rock
Accordifn to the man page, that just specifies what port to listen on. By default it's 514 syslog port. I'll try it anyway. I'm up for anything at this point ;-) Chuck On Sat, 8 Mar 2003, Michael K. Smith wrote: > Hello Chuck: > > On Sat, 8 Mar 2003, Chuck Rock wrote: > > > For the last few ver

Re: Syslog problem

2003-03-08 Thread Michael K. Smith
Hello Chuck: On Sat, 8 Mar 2003, Chuck Rock wrote: > For the last few versions of FreeBSD, I have not been able to get my syslog > to log my dial-up pool from my Cisco router. > > I changed the syslog startup flags in rc.conf. > > I'm running it now as /usr/sbin/syslogd -a 207.206.185.1/27 -a > 2

RE: Syslog problem

2003-03-08 Thread Chuck Rock
ocal7 facility and one at Severity 3 and one at Severity 5 The log files are still zero bytes. Chuck -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of Chuck Rock Sent: Saturday, March 08, 2003 1:24 PM To: [EMAIL PROTECTED] Subject: Syslog problem For the la

Syslog problem

2003-03-08 Thread Chuck Rock
For the last few versions of FreeBSD, I have not been able to get my syslog to log my dial-up pool from my Cisco router. I changed the syslog startup flags in rc.conf. I'm running it now as /usr/sbin/syslogd -a 207.206.185.1/27 -a 209.83.132.1/27 The router is at .1 and configured to send it's l