Skip to content

Commit 5835817

Browse files
author
Paul D.Smith
committed
Explain TWAMP, UDP, NATs.
1 parent ed4cb34 commit 5835817

File tree

1 file changed

+35
-0
lines changed

1 file changed

+35
-0
lines changed
Lines changed: 35 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,35 @@
1+
---
2+
title: "Azure Operator Nexus: TWAMP (UDP) not working"
3+
description: Learn how to troubleshoot TWAMP (UDP) issues.
4+
author: papadeltasierra
5+
ms.author: pauldsmith
6+
ms.service: azure-operator-nexus
7+
ms.custom: azure-operator-nexus
8+
ms.topic: troubleshooting
9+
ms.date: 12/10/2024
10+
# ms.custom: template-include
11+
---
12+
13+
# Troubleshoot TWMP (UDP) not working
14+
15+
TWAMP (Two-Way Active Measurement Protocol) over UDP does not work if NAT (network address translation) occurs between the Session-Sender and the Session-Reflector and/or Control-CLient and Server. Typically the Sesion-Sender and Control-Client will reside in one network and the Session-Reflector and Server will reside in a second network.
16+
17+
Examples where NAT can occur include any meeting between two LANs with independent addressing such as a connection to/from a vLAN.
18+
19+
TWAMP over TCP can work through a NAT providing the Session-Reflector and Server have IP addresses outside the address range of the subnet in which the Session-Sender and Control-Client reside and the Session-Reflector and Server IP addresses are unique along the entire path.
20+
21+
## Diagnosis
22+
23+
TWAMP (UDP) is configured but does not work. Network traffic analysis shows traffic leaving the Control-Client and/or Session-Sender but not returning from the Server and/or Session-Reflector.
24+
25+
## Mitigation steps
26+
27+
None are possible. Two-way UDP protocols cannot traverse networks where address translation occurs without additional logic elements such as an ALG (Application-level Gateway).
28+
29+
Two-Way TCP protocols can traverse a NAT providing that the TCP connection is esablished from inside the NAT to outside. This is possible because a long-live connection is established through the NAT and reaffic in the return direction flows long this connection. UDP traffic does not establish a long-live connection so there is no defined path back through the NAT for return traffic to follow.
30+
31+
## Related content
32+
33+
- [A Two-Way Active Measurement Protocol (TWAMP)](https://datatracker.ietf.org/doc/html/rfc5357)
34+
- If you still have questions, contact [Azure support](https://portal.azure.com/?#blade/Microsoft_Azure_Support/HelpAndSupportBlade).
35+
- For more information about support plans, see [Azure support plans](https://azure.microsoft.com/support/plans/response/).

0 commit comments

Comments
 (0)