The periodic script /etc/periodic/security/900.tcpwrap that is enabled by default in the periodic emails does not report any refused connections.
Reason is that refused connections do not seem to be reported anymore in the /var/log/messages file. However, refused connections to SSH daemons are (still) reported in /var/log/auth.log.
My /etc/syslog.conf file is (by my knowledge) the standard 8.1 syslog file:
# $FreeBSD: src/etc/syslog.conf,v 220.127.116.11.4.1 2010/06/14 02:09:06 kensmith Exp $
# Spaces ARE valid field separators in this file. However,
# other *nix-like systems still insist on using tabs as field
# separators. If you are sharing this file between systems, you
# may want to use only tabs as field separators here.
# Consult the syslog.conf(5) manpage.
security.* /var/log/security auth.info;authpriv.info /var/log/auth.log
lpr.info /var/log/lpd-errs ftp.info /var/log/xferlog
# uncomment this to log all writes to /dev/console to /var/log/console.log
# uncomment this to enable logging of all log messages to /var/log/all.log
# touch /var/log/all.log and chmod it to mode 600 before it will work
# uncomment this to enable logging to a remote loghost named loghost
# uncomment these if you're running inn
# news.crit /var/log/news/news.crit
# news.err /var/log/news/news.err
# news.notice /var/log/news/news.notice
I do not see any major differences in here from previous FreeBSD versions.
An easy but incorrect fix (IMHO) would be to have the /etc/periodic/security/900.tcpwrap parse the /var/log/auth.log file. However this would then only show refused connections to daemons concerned with authentication.
I suspect that the tcp-wrappers code logs to the wrong syslog facility and/or level. Or that a change has been made to this without also changing the /etc/syslog.conf file.
How-To-Repeat: Edit /etc/hosts.allow in a way that blocks an IP address controlled by you.
Try to make a tcp session to the FreeBSD 8.1 installation from the blocked IP address. Observe that your connection is refused.
Check the /var/log/messages file and see that there is no log record mentioning the blocking of your IP address.
For bugs matching the following criteria:
Status: In Progress Changed: (is less than) 2014-06-01
Reset to default assignee and clear in-progress tags.
Mail being skipped