Is there any kind of problem with syslogd and the -a option? I've tried all sorts of variations (-a 10.0.0.x, -a 10.0.0.x/24, -a myrouter.mydomain, -a myrouter.mydomain/24, etc.) and it just doesn't seem to let anything through. Starting syslogd without any option works (my router can write to the system log--both are on my internal LAN); starting it with the -a option for a little more security prevents anything at all from being written. Am I doing something wrong, or is there a bug? I don't necessarily need the extra security (no syslog UDP traffic can enter the LAN from the outside, anyway), but it would be nice if I could get this option to work.
-- Anthony _______________________________________________ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
