after an update for a sensors 3.1(5) to s62, we are receiving a large amount of events for the new signature 11018-eDonkey Activity, around 12k/hr The source of the alarm is a proxy server on the network. Has any seen or noticed any false positives for this alarm?
With 3.1, it possible for the sensor to get the actual client and server reversed while monitoring a TCP stream. It may be possible for the proxy server to return traffic to the actual client that happens to be using one of the eDonkey ports (4242,4661,4662) as an ephemeral port for an application that matches the pattern for eDonkey traffic. The best solution is to create a filter with the proxy server as a source for this alarm. 4.x sensors should not see this problem.
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...
[toc:faq]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 and UDP are I...