aboutsummaryrefslogtreecommitdiff
path: root/src/nat/nat_stun.c
diff options
context:
space:
mode:
Diffstat (limited to 'src/nat/nat_stun.c')
-rw-r--r--src/nat/nat_stun.c11
1 files changed, 4 insertions, 7 deletions
diff --git a/src/nat/nat_stun.c b/src/nat/nat_stun.c
index 78b0a56fc..06ed9261f 100644
--- a/src/nat/nat_stun.c
+++ b/src/nat/nat_stun.c
@@ -19,14 +19,9 @@
19*/ 19*/
20 20
21/** 21/**
22 * This code is based on ministun.c, that is based on Asterisk old STUN code. 22 *
23 * This code provides some support for doing STUN transactions. 23 * This code provides some support for doing STUN transactions.
24 * The simplest request packet is just the header defined in 24 * We send simplest possible packet ia REQUEST with BIND to a STUN server.
25 * struct stun_header, and from the response we may just look at
26 * one attribute, STUN_MAPPED_ADDRESS, that we find in the response.
27 * By doing more transactions with different server addresses we
28 * may determine more about the behaviour of the NAT boxes, of
29 * course - the details are in the RFC.
30 * 25 *
31 * All STUN packets start with a simple header made of a type, 26 * All STUN packets start with a simple header made of a type,
32 * length (excluding the header) and a 16-byte random transaction id. 27 * length (excluding the header) and a 16-byte random transaction id.
@@ -34,6 +29,8 @@
34 * structured as a type, length and a value (whose format depends 29 * structured as a type, length and a value (whose format depends
35 * on the type, but often contains addresses). 30 * on the type, but often contains addresses).
36 * Of course all fields are in network format. 31 * Of course all fields are in network format.
32 *
33 * This code was based on ministun.c.
37 * 34 *
38 * 35 *
39 * @file nat/nat_stun.c 36 * @file nat/nat_stun.c