summaryrefslogtreecommitdiff
path: root/ui
diff options
context:
space:
mode:
authorAdam Ierymenko <adam.ierymenko@gmail.com>2016-03-03 13:52:27 -0800
committerAdam Ierymenko <adam.ierymenko@gmail.com>2016-03-03 13:52:27 -0800
commitba56a5b9d1fd7a9007cf29d467afee20ae4c4a63 (patch)
tree07b90da68d92e44fa4c7ad27543cb02748bb8bf6 /ui
parenta27d8b2910932bb1c31eb8b0542266825eae0ba6 (diff)
downloadinfinitytier-ba56a5b9d1fd7a9007cf29d467afee20ae4c4a63.tar.gz
infinitytier-ba56a5b9d1fd7a9007cf29d467afee20ae4c4a63.zip
Another NAT-t improvement:
Many NATs revert to symmetric behavior from friendlier modes if they cannot preserve ports. This can occur if there is, for example, more than one ZT device behind the NAT using port 9993. Others (Airport Extreme?) seem to have bugs in which they completely freak out if more than one device tries to do a lot of mappings using the same internal local port. Mostly to fix the latter case and somewhat to fix the former, we introduce a secondary port. ZeroTier now binds 9993 (or whatever port you specify) plus another port computed deterministically from your ZeroTier address. This port is used for new links 1/4 of the time. This mostly addresses the second problem above and partly helps to address the first. If uPnP/NAT-PMP is enabled we also still open a tertiary port because some routers freak out if NAT-t is attempted using the same port as uPnP. All of this is IPv4 only of course. IPv6 is sane.
Diffstat (limited to 'ui')
0 files changed, 0 insertions, 0 deletions