BB Unix Network Monitor - Message
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: {bb} messages file full of same telnetd error from bigbro
- To: bb@bb4.com
- Subject: Re: {bb} messages file full of same telnetd error from bigbro
- From: "Stephen Pesini" <stephen.pesini@villanova.edu>
- Date: Sun, 09 Apr 2006 21:34:52 -0400
- Content-disposition: inline
- Content-language: en
- Content-transfer-encoding: 7bit
- Content-type: text/plain; charset=us-ascii
- Reply-to: bb@bb4.com
- Sender: owner-bb@bb4.com
Just use telnet:s in your bb-hosts file to tell big brother not to do a
protocol handshake.
It will only test the ability to connect to the socket (port 25) and no
handshake. This usually stops the protocol errors. This also works for
things like jakarta (tomcat) listener checks, if all you need is to test
for listening socket.
----- Original Message -----
From: Philip Clark <bblist@cannae.uklinux.net>
Date: Sunday, April 9, 2006 5:41 pm
Subject: Re: {bb} messages file full of same telnetd error from bigbro
> On Fri, 2006-04-07 at 14:46, Charles Jones wrote:
> > Why are you even running telnetd? If you don't need it for some
> legacy
> > application support or something, I would do away with telnet
> and just
> > use sshd. The errors are most probably caused by bigbro dropping
> the
> > telnet connection un-gracefully. The ttloop error occurs because
> the
> > telnet session was reset before the session could fully initialize.
> >
> > I don't know offhand of an easy way to ignore/disable these
> warnings,
> > other than hacking telnetd source, or bigbro itself. One sure
> fire way
> > is to stop using insecure telnet ;-)
>
> Except that sshd will probably do something very similar when it's
> tested by BB. A search of the list archives for "protocol mismatch"
> should reveal a few threads about that.
>
> If testing with bbnet (even using the optional flags) causes the
> telnet daemon to log the connection, you could try using an external
> script which can call the telnet client. That is likely to be much
> slower than the normal way, so you may want to run it less frequently.
> Also, this may just change the message that is logged from failure
> to success.
>
> Another approach, which has been reported as being useful, is to use
> syslog-ng to filter any messages that are triggered by BB test from
> the logs.
>
> Cheers, Phil.
>
>
>
> --
> It's not an optical illusion, it just looks like one. (Phil White)
>
> --
> =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-==-=-=-=-=-=-=-=-=-=-
> =-=
> To unsubscribe from this list, or to subscribe to the bb-digest list
> send e-mail to mailto:majordomo@bb4.com with unsubscribe bb -
> and/or-
> subscribe bb-digest in the BODY of the message.
>
--
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-==-=-=-=-=-=-=-=-=-=-=-=
To unsubscribe from this list, or to subscribe to the bb-digest list
send e-mail to mailto:majordomo@bb4.com with unsubscribe bb -and/or-
subscribe bb-digest in the BODY of the message.
Home |
Main Index |
Thread Index