X-Git-Url: https://tinc-vpn.org/git/browse?a=blobdiff_plain;f=goals.mdwn;h=57bffec947255b2342fb8988ae337cf15fe0dc34;hb=e5406abde6714ee5b0ed56245a9e984e02cd45ec;hp=19f02f5cdc4d78e4f8c6a9ca964762e8ccb2adad;hpb=e45797c2adf3298c676ef3ad7315dd7b58f25f7b;p=wiki

diff --git a/goals.mdwn b/goals.mdwn
index 19f02f5..57bffec 100644
--- a/goals.mdwn
+++ b/goals.mdwn
@@ -65,7 +65,7 @@ The 1.1 branch of tinc has been created as a stepping stone towards
 2.0. Only gradual changes to the source code are allowed, ensuring
 that the code is always in a mostly usable state. The protocol will
 stay compatible with that of the 1.0 branch. The following features
-are planned in this branch:
+are planned or are already implemented in this branch:
 
 **Replaceble cryptography backend**
 
@@ -93,16 +93,6 @@ in the tinc.conf files. It is desirable to have tinc manage the
 creation of control connections as well, so that the administrator
 does not have to do this manually anymore.
 
-**Deal with NAT**
-
-The 1.0 branch by default tries to exchange packets via UDP.
-However, if one or more peers are behind a NAT, and source ports
-might be changed or packets may not arrive at all, the
-administrator had to manually enable the TCPOnly option or use
-another workaround to get tinc to work. Tinc should be able to cope
-with altered source ports, and should detect whether or not packet
-exchange via UDP works at all, and if not fall back to TCP.
-
 **Automate setting up nodes**
 
 The tincctl utility should have a wizard-like interface that asks a few