I understand that the below indicates a "TCP protocol violation by a box on the other end". That does not mean hacking to my server correct? I'm suspecting that the below has something to do with my servers being down. I'm seeing several of the below and it's from different ip address. How could I trace where does the source ip comes from?
TCP: Treason uncloaked! Peer 212.138.47.15:14732/80 shrinks window 4108809652:4108812411. Repaired.
This Question has been solved and asker verified All Experts Exchange premium technology solutions are available to subscription members.
Experts Exchange has been collecting answers to technology questions since 1996…3 million and counting! If you have a question, chances are we already have your answer.
If you can't find the exact answer you're looking for, ask our exclusive community of 50,000 experts. You’ll get a personalized answer from a trusted professional.
Thousands of free tech tips, tricks, how-to’s and tutorials are available in our peer reviewed articles section. See for yourself how smart our experts are, no login required.
Save solutions to your questions, answers you’ve discovered through searching plus helpful articles in your personal knowledgebase for easy future access.
Access the answers to your technology questions today.
30-day free trial. Register in 60 seconds.
Members of the expert community talk about why the experience at Experts Exchange is different than what you will find anywhere else.
Try it out and discover for yourself.
30-day free trial. Register in 60 seconds.
Join the community of experts here and help other tech pros by answering question in your area of expertise. You can earn FREE access to all Experts Exchange's premium features and resources.
I've seen this answer at the below url:
From: Russell Coker <russell@coker.com.au>
http://lists.debian.org/de
Any other possibilities?
Business Accounts
Answer for Membership
by: gauravmPosted on 2003-04-29 at 08:17:02ID: 8420715
>From /usr/src/linux/net/ipv4/tc
if (tp->snd_wnd == 0 && !sk->dead &&
!((1<<sk->state)& TCPF_SYN_SENT|TCPF_SYN_REC
/* Receiver dastardly shrinks window. Our retransmits
* become zero probes, but we should not timeout this
* connection. If the socket is an orphan, time it out,
* we cannot allow such beasts to hang infinitely.
*/
#ifdef TCP_DEBUG
if (net_ratelimit())
printk(KERN_DEBUG "TCP: Treason uncloaked! Peer
%u.%u.%u.%u:%u/%u shrinks window %u:%u. Repaired.\n",
NIPQUAD(sk->daddr), htons(sk->dport), sk->num, tp->snd_una, tp->snd_nxt);
#endif
So it appears that someone is running some sort of "tar-pit" system that is designed to keep sockets in a bad state and run you out of kernel memory.
Maybe you should tell your ISP that they are to blame for such actions being done to you and that they should give you face(I think that was the term you used) by closing their open relays.
Someone who's doing the tar-pit attack would probably like your box to crash, but I'd hope that Linux can withstand such things, and there is special-case code in there to deal with it.