Linux - NetworkingThis forum is for any issue related to networks or networking.
Routing, network cards, OSI, etc. Anything is fair game.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
I was presented with this error when using ChkRootKit-0.39a. I have alos found a post or two online referring to the same error with respect to netstat.
Of course there was no answer to this person's question...
well... it was contained in the body of an email that I send my self via this cron job:
sh /usr/sbin/chkrootkit-0.39a/chkrootkit |grep -v "not" |mail -s "CHKROOTKIT on $(hostname)"
This is the email:
From: Cron Daemon <root@www.mydomain.com>
To: root@www.mydomain.com
Subject: Cron <root@www> sh /usr/sbin/chkrootkit-0.39a/chkrootkit |grep -v "not" |mail -s "CHKROOTKIT on $(hostname)" wendels@mydomain.com
Date: 19 Mar 2003 08:51:09 -0500
warning, got bogus tcp line.
This is the standard out recieved when running chkrootkit. I duplicated the output yesterday running chkrootkit from the command line. Didn't get the same error today...
Can you run chkrootkit in a terminal and see if you get this 'bogus tcp line' error. I'm not sure if this an e-mail error or a message from chkrootkit.
chkrootkit will check things like sniffer logs, your syslogs and other log files for potential hack attempts / exploits and so forth.
I highly suspect that it detected something in your syslog (possibly a netfilter log entry) which lent it to believe someone was trying to compromise your box.
Easiest way to find out is to simply run chkrootkit (without the grep -v) and see *WHERE* it displays the problem.
You'll see something like this :
Checking `aliens'... no suspect files
Searching for sniffer's logs, it may take a while... nothing found
Searching for HiDrootkit's default dir... nothing found
Searching for t0rn's default files and dirs... nothing found
Searching for t0rn's v8 defaults... nothing found
Searching for Lion Worm default files and dirs... nothing found
Searching for RSHA's default files and dir... nothing found
Searching for RH-Sharpe's default files... nothing found
Searching for Ambient's rootkit (ark) default files and dirs... nothing found
Searching for suspicious files and dirs, it may take a while...
and will be able to determine where'bouts it detected 'something bogus'
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.