Red Hat Bugzilla – Bug 26493
portsentry wrongly reports portmap connections
Last modified: 2008-05-01 11:37:59 EDT
On startup portsentry immediately claims there are external portmap
connections, even when I am not dialled up. It takes up all the CPU time
(along with syslogd, which is logging all the false attack alerts)
This is with no changes to the portsentry config files, and the
security/firewall settings set at installation to "medium".
OK. The problem is that it's trying to listen on ports that are already in use.
In this case portmap on 111 is making portsentry freak. I have updated the
config file for this so that logfiles don't get filled with this anymore.