I was hoping someone could provide some advice on this fault ticket we have. I will say upfront that the output I have provided is from a Juniper firewall but I have decided to post here in case this issue is vendor agnostic and more 'general'.
The situation unfolds thus: our customer has hundreds of branch sites and there is a certain application/service that is monitored remotely by a 3rd party at each site. The 3rd party has a router at each branch and this connects to our LAN. Between the 'local' 3rd party router and the 3rd party's head office is an IPSec tunnel that carries the alarms. On our LAN interface at each branch we restrict communication between these two to ESP & ISAKMP as the per the following ACL:
We received a fault ticket where the customer was complaining that they were receiving lots of 'rogue' traffic. They sent us some output from their app which confirmed that not only were they receiving traffic with destination port 500 (UDP), as we would expect, but other traffic with random port numbers. The IPSec traverse our DMZ/internet firewalls, the Junipers. I have attached two sets of output: one that describes the 'normal' flow we are expecting, i.e. UDP 500, the other with the random port numbers that the 3rd party is complaining as 'rogue'.
As I understand it ISAKMP is used to set the tunnel up and ESP encapsulates the payload (I think). Certainly from a rough GNS3 setup this is what appeared to be happening. Could this 'rogue' traffic actually actually be legitimate traffic, specifically the ESP-related traffic and this is actually just a big mis-understanding.
With NAT-T data is also encapsulated into UDP/4500.
Looking at the trace you provided: protocol-id="50" I assume this means the IP protocol number. It would indiate this an ESP packet, however ports should not be there. ESP header does not contacin port information.
What would be interesting is to capture the "offending" traffic with wireshark and check what it truly is.
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...