It looks like I have an end user who's TCP stack is not working correctly: immediately after sending his initial HTTP GET, he sends an ACK for a packet I haven't sent yet. I send the proper sequence number on the reply but he's stuck on the wrong one and away we go with an ACK storm that lasts thousands of packets on multiple streams.
I'm amazed that nothing in the path kills the session... I have an ASA w/IPS and a CSS fronting WebLogic web servers and none of them do anything except reply like mad.
I'm hunting for a way to stop these things from dragging down performance but I don't see anything yet... suggestions?
Table of ContentsIntroductionVersion HistoryPossible Future
UpdatesDocuments PurposeNAT Operation in ASA 8.3+ SectionsRule Types
Network Object NATTwice NAT / Manual NATRule Types used per SectionNAT
Types used with Twice NAT / Manual NAT and Network Obje...
Table of Contents Introduction:This document describes details on how
NAT-T works. Background: ESP encrypts all critical information,
encapsulating the entire inner TCP/UDP datagram within an ESP header.
ESP is an IP protocol in the same sense that TCP an...