Re: extra open ports in rkhunter

2010-09-20 Thread Carl Johnson
Carl Johnson writes: > I am running rkhunter and it keeps reporting a port inconsistency > between sockstat and netstat -a. Netstat shows an extra 5 ports open, > but netstat doesn't show what is holding ports open, so I don't know > what they are. Does anybody know how to determine what is hol

Re: extra open ports in rkhunter

2010-09-19 Thread Carl Johnson
Carl Johnson writes: > Anonymous writes: >> Do you have some networking FS enabled (NFS, AFS, Coda, etc)? Perhaps, >> one of them listens for connections from kernel and is not associated >> with userland process. But it's just a guess. > > I have NFS enabled, but its processes are accounted for

Re: extra open ports in rkhunter

2010-09-18 Thread Carl Johnson
Anonymous writes: > Chuck Swiger writes: > >> Hi-- >> >> On Sep 18, 2010, at 4:27 PM, Carl Johnson wrote: >>> The following are the ports if anybody has any ideas, but I would also like >>> to know how to trace them down myself: >>> >>> tcp4 0 0 *.876 *.*

Re: extra open ports in rkhunter

2010-09-18 Thread Carl Johnson
Chuck Swiger writes: > Hi-- > > On Sep 18, 2010, at 4:27 PM, Carl Johnson wrote: >> The following are the ports if anybody has any ideas, but I would also like >> to know how to trace them down myself: >> >> tcp4 0 0 *.876 *.*LISTEN >> tcp6

Re: extra open ports in rkhunter

2010-09-18 Thread Anonymous
Chuck Swiger writes: > Hi-- > > On Sep 18, 2010, at 4:27 PM, Carl Johnson wrote: >> The following are the ports if anybody has any ideas, but I would also like >> to know how to trace them down myself: >> >> tcp4 0 0 *.876 *.*LISTEN >> tcp6

Re: extra open ports in rkhunter

2010-09-18 Thread Chuck Swiger
Hi-- On Sep 18, 2010, at 4:27 PM, Carl Johnson wrote: > The following are the ports if anybody has any ideas, but I would also like > to know how to trace them down myself: > > tcp4 0 0 *.876 *.*LISTEN > tcp6 0 0 *.921 *