Thanks, but that doesn't seem to be the problem. I think it's getting through IPFW fine, and I removed the -s from syslogd's options, but I still can't find any info on (configuring) remote logging, aside from -a which I'm already using.
Chris Pepper
At 12:16 AM -0500 2002/11/19, Jerry Bell wrote:
I really don't know if it would work or not, but you could put an ipfw divert rule and natd to redirect the syslog packets to localhost:514 or similar.Also, you'll need to remove the '-s' flag from syslogd. Jerry ----- Original Message ----- From: "Chris Pepper" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Monday, November 18, 2002 11:54 PM Subject: 4.7-S: syslog from TiVoI've just networked my TiVo, and noticed that it tries to connect to 255.255.255.255:514/udp on restart. So naturally I'd like to capture this in syslog, to see what it has to tell me. I opened up the port in ipfw, and see a packet coming through, but after much head-banging on syslog.conf.5, and trial and error, I still can't get anything to showi up in the log file I created for this host, or messages or console.log. What am I missing?? Thanks much, Chris Pepper >[www:~] root# uname -a >FreeBSD www.reppep.com 4.7-STABLE FreeBSD 4.7-STABLE #2: Mon Nov 18 >21:56:46 EST 2002 >[EMAIL PROTECTED]:/usr/obj/usr/src/sys/REPPEP i386 >[www:~] root# ipfw -aN l|grep syslog >01400 1 122 allow udp from 66.92.104.200/30 to any >dst-port syslog >[www:~] root# ps -aux|grep syslog >root 5850 0.0 0.2 1028 720 ?? Ss 11:28PM 0:00.04 >/usr/sbin/syslogd -4 -a 66.92.104.200/30 >[www:~] root# tail -2 /etc/syslog.conf >+airport.reppep.com >*.* /var/log/airport.log >[www:~] root# ls -l /var/log/airport.log> >-rw-r--r-- 1 root wheel 0 Nov 18 21:09 /var/log/airport.log
-- Chris Pepper: <http://www.reppep.com/~pepper/> Rockefeller University: <http://www.rockefeller.edu/> To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-questions" in the body of the message
