View Single Post
  #5   (View Single Post)  
Old 16th March 2009
da1 da1 is offline
Fdisk Soldier
 
Join Date: Feb 2009
Location: Berlin, DE
Posts: 49
Default

Quote:
Originally Posted by ddekok View Post
So you should have something like
Code:
syslogd_flags="-d -a 192.168.0.1/24:* -vv"
yup, that works but logs everything into /var/log/messages

Quote:
Originally Posted by J65nko View Post
Did you create the /var/log/router.log file?
Syslogd only logs to an existing file, it does not create this file unless you use the -C option.
yup, file was created way before changes were made. lucky man command

Quote:
According to syslogd(8) your -a 192.168.0.1 option actually is -a 192.168.0.1/16:514. Is that /16 netmask correct for your setup?
actually /24 (255.255.255.0) is corect for my netmask but this doesn't works. I see that no matter what /16, /24 or /32 I use the results are the same; logging does not works, and I keep getting that "port mismatch" error. this only applies if i use :514. if i use :* all is ok no matter of the netmask


Quote:
RE: tcpdump
You can use the -n flag to disable name lookups, and the -s0 to see the complete data. -vv also helps
I like poking my eyes at everithing and then eliminating the bad and using the good; but thx for the head's up


So..recap:

if i use in rc.conf of my bsd box -d -a 192.168.0.1/whatever:* -vv (tried /16 /24 /32 result are the same) logging works but logges to /var/log/messages and "port mismach error" is replaced by a very nice looking, I might add, output of
Code:
cvthname(192.168.0.1)
validate: dgram from IP 192.168.0.1, port 2052, name router.ro;
accepted in rule 0. <----

le: one of my mistakes was that i read the wrong manual for syslogd. dunno why i used google to search for the manual and ended up with a faulty one that did not have the /:* mentioned at all. I mean, I dunno why I didn't used freebsd's manual (command line or web)

Last edited by da1; 16th March 2009 at 03:03 AM.
Reply With Quote