> Source: [sk168336](https://support.checkpoint.com/results/sk/sk168336)

# sk168336 - VPN traffic (after encryption) is not visible via tcpdump and does not arrive at the remote VPN peer when using SHA-384 

| Property | Value |
|----------|-------|
| Solution ID | sk168336 |
| Date Created | 2020-08-04 |
| Last Modified | 2020-12-23 |
| Technical Level | Advanced |

## Symptoms

- * When SHA-384 is configured for p1 and\\or p2, the encrypted traffic (ESP) is not visible via tcpdump (the encrypted traffic is visible via "fw monitor").
* The tunnel is marked as non-accelerated via the "vpn tu tlist": "p: -". <br />

## Cause

SecureXL does not support SHA-384.

<br />

## Solution

This solution requires authentication. Please log in to view the full solution.

---

# Agent Instructions

This content is from the Check Point Support Center (https://support.checkpoint.com), the official knowledge base for Check Point cybersecurity products.

## Navigating This Knowledge Base

- **Complete index**: [llms.txt](https://support.checkpoint.com/llms.txt)
- **All SK articles**: [SecureKnowledge Sitemap](https://support.checkpoint.com/sitemaps/secureknowledge-sitemap-index.xml)
- **SK article URL pattern**: `https://support.checkpoint.com/results/sk/{skId}`
- **Markdown responses**: AI bot User-Agents automatically receive `text/markdown` content