Changes between Version 7 and Version 12 of Ticket #2305


Ignore:
Timestamp:
Dec 3, 2015, 6:06:27 PM (8 years ago)
Author:
Josh
Comment:

Added a few bits of information to the description from my recent research.

Legend:

Unmodified
Added
Removed
Modified

  • Ticket #2305

    • Property Summary UDP Hole Punching / NAT Transversal → UDP Hole Punching / NAT Traversal
    • Property Milestone Alpha 16 → Backlog

  • Ticket #2305 – Description

    v7 v12  
    11==== Details ====
    2 Right now in 0 A.D. we use a primitive UPnP system to implement NAT transversal but this system is unreliable. We'd like to see a better method using UDP Hole Punching instead. The solution would most likely involve interacting with the lobby server to get transversal information but it could also involve using something like [http://en.wikipedia.org/wiki/STUN STUN].
     2Right now in 0 A.D. we use a primitive UPnP system to implement NAT transversal, but this system is unreliable. We would like to see a better method using UDP Hole Punching instead.
     3
     4The solution would involve interacting with the lobby server to get transversal information. The recommended implementation would use  [http://en.wikipedia.org/wiki/STUN STUN] with [https://en.wikipedia.org/wiki/Interactive_Connectivity_Establishment ICE]. It may be possible to (ab)use [http://xmpp.org/extensions/xep-0176.html XEP-0176: Jingle ICE-UDP Transport Method] for the desired result. Ejabberd has a built-in STUN server ([https://www.process-one.net/docs/ejabberd/guide_en.html#stun Manual Entry]). Both Ejabberd and Gloox support XEP-0176.
    35
    46==== Expected Result ====