Alternative to syslogd that actually writes external logs to
kayasaman at gmail.com
Tue Nov 29 00:08:25 UTC 2011
On 11/29/2011 01:50 AM, Jon Radel wrote:
> On 11/28/11 6:42 PM, Kaya Saman wrote:
>> However, when using tcpdump it shows that rsyslog is infact receiving
>> information but still unfortunately not logging to file???
>> # tcpdump -tlnvv -i em0 port 514
>> tcpdump: listening on em0, link-type EN10MB (Ethernet), capture size 96
>> IP (tos 0x0, ttl 255, id 1875, offset 0, flags [none], proto UDP (17),
>> length 142)
>> 192.168.1.1.59189 > 192.168.1.120.514: SYSLOG, length: 114
>> Facility local7 (23), Severity notice (5)
>> Msg: 11578: 011565: Nov 28 23:34:19.475: %SYS-5-CONFIG[|syslog]
>> File permissions are correct as I got rsyslog to create the file from
>> What am I missing here?
> Have you tried with all firewalling on the machine turned off?
> [My apologies if this has been covered earlier in the thread and I
> missed it.]
> --Jon Radel
> jon at radel.com
Yep! I don't actually run any rules on the firewall even though PF is
enabled. it's just meant for fail2ban though.
However, disabled PF but still not working :-(
More information about the freebsd-questions