TCP: Treason uncloaked!

Hi!

I am having redhat linux 7.2 server . while typing the dmesg in the shell i am getting the following message.

# dmesg

TCP: Treason uncloaked! Peer 202.162.56.156:32867/22 shrinks window 2070208664:2070208728. Repaired.
TCP: Treason uncloaked! Peer 202.162.56.156:32867/22 shrinks window 2070208664:2070208728. Repaired.
TCP: Treason uncloaked! Peer 202.162.56.156:32922/22 shrinks window 2811533730:2811533794. Repaired.


That server is co-located server that is remote host.

I am trying to access the websites in my client system which is hosted in the server.

The problem is the site is not clear. some times it is displaying well. some times not clear.

It is displaying with <tag> <html>

What is the solution. Any ideas ?

Kindly help me in this regard.


Regards
Basbosco





LVL 36
Loganathan NatarajanLAMP DeveloperAsked:
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

x
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

jlevieCommented:
I'd say there's two different issues here and they probably aren't related. The TCP errors would tend to point to a problem with the ssh client/system you are using. If I understand your problem with the web site it sounds like some of the data that you expect to be rendered by a browser is showing up as the raw HTML code. That would point to a problem with the HTML pages themselves, or if they are being generated by a scripting language (PHP, Perl, etc) with the code that generates the page.
0
linuxsubCommented:
The reason Linux is printing such messages is because your client guy is shrinking the TCP Window to 0, and the server has something to retransmit. There is something seriously wrong with your client's  stack. Which Stack/OS are you using on he client side, and which browser?

That could explain your browser showing some html tags as the server fails to send the whole page across and based on what browser you are using it is failing to parse it out.
0
Mihai BarbosTrying to tame bits. They're nasty.Commented:
As my predecessors have said, the error means a broken stack on the client side. Or maybe an (pretty silly) attack.
Or a new firewall policy from your ISP or a broken device along the way (although I think this is quite unlikely).

Anyway:
1. do you find any other errors linked to the TCP/IP stack ? Something about wrong checksums ?
2. Are you using any mobile devices ? Some of those seem to have funny ideas about TCP/IP.
3. Do you recognize the IP (202.162.56.156) ?
0
Webinar: Miercom Evaluates Wi-Fi Security

It's not just about Wi-Fi connectivity anymore. A wireless security breach can cost your business large amounts of time, trouble, and expense. Plus, hear first-hand from Miercom how WatchGuard's Wi-Fi security stacks up against the competition in our upcoming webinar!

pjedmondCommented:
The IP 202.162.56.156 does not appear to be a valid registered IP to anyone, and it is not an 'internal network ip' as far as I'm aware, therefore, I'd treat this particular incident suspiciously.

Unfortunately, I can't reproduce this error, even with a RedHat 7.2 Server available to me.

I suspect that this message was as a result of an attempted attack on your sshd. As a result of the number of packets being sent, you attempts to access anything else were messes with, and unable to complete. Therefore I recommend:

a.  Check whether you have sshd running. If you don't need it, then get rid of it.
b. If you do need sshd, then check version number (rpm -q sshd), and go here:

http://www.openssh.com/security.html

Check whether your sshd needs to be updated, and update as required.

HTH:)

0
pjedmondCommented:
Of course if you are not using sshd - just bloke port 22 with your firwall:)
0
ahoffmannCommented:
> .. then check version number (rpm -q sshd),
please don't rely on rpm (or packages anyhow) but use
   sshd -V
to get the real version.
Think secure, not guessing ;-)
0
savashCommented:
The client is "shrinking the TCP Window to 0" and it cause the problem. So, what to do to prevent this issue ?
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
ahoffmannCommented:
logudotcom, could you please explain your grading
0
mgbyrne2004Commented:
*** advertising removed by Netminder, Site Admin ***
0
buckaro0Commented:
Just to comment on pjedmond's remark that you should treat this suspiciously... I'm not so sure.

 -- the original IP address 202.162.56.156 is a _valid_ IP address, with a registered operator in India.
so it's not as suspicious as a packet coming from an unallocated source.

inetnum:      202.162.48.0 - 202.162.63.255
netname:      SPACENET
descr:        HCL Comnet, Internmet Service Provider on VSATs, India
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Linux Security

From novice to tech pro — start learning today.