[snip]
To disable that behavior, just put -a 10.10.10.1/32:* in your syslogd_flags
and you should be good to go (if your problem was the same as mine :)
Thanks, that helped a lot. for the record, I had to set the
syslogd_flags as Jon described, as well as adding +@ and
+fortigate lines to
On Jan 11, 2008, at 9:51 AM, Andy Greenwood wrote:
I have recently set up a Fortigate-60 to run as a firewall/vpn on my
home network. I have a FreeBSD 7.0-prerelease machine sitting behind
it in the DMZ which is running ssh/web/etc. I'm trying to get the FG
to log to the BSD box's syslog.
Jeffrey Goldberg [EMAIL PROTECTED], said on Sat Jan 12, 2008 [03:50:45 PM]:
} On Jan 11, 2008, at 9:51 AM, Andy Greenwood wrote:
}
} I have recently set up a Fortigate-60 to run as a firewall/vpn on my
} home network. I have a FreeBSD 7.0-prerelease machine sitting behind
} it in the DMZ
On 2008-01-12 15:50, Jeffrey Goldberg [EMAIL PROTECTED] wrote:
On Jan 11, 2008, at 9:51 AM, Andy Greenwood wrote:
I have recently set up a Fortigate-60 to run as a firewall/vpn on my
home network. I have a FreeBSD 7.0-prerelease machine sitting behind
it in the DMZ which is running
I have recently set up a Fortigate-60 to run as a firewall/vpn on my
home network. I have a FreeBSD 7.0-prerelease machine sitting behind it
in the DMZ which is running ssh/web/etc. I'm trying to get the FG to log
to the BSD box's syslog. I have set up the necessary stuff on the FG,
and can
