Editing Nattraversal
From EMule Wiki
Warning: The database has been locked for maintenance, so you will not be able to save your edits right now. You may wish to cut-n-paste the text into a text file and save it for later.
The administrator who locked it offered this explanation: site maintenance
The edit can be undone.
Please check the comparison below to verify that this is what you want to do, and then save the changes below to finish undoing the edit.
| Latest revision | Your text | ||
| Line 1: | Line 1: | ||
''nat traversal'' Makes LowID to LowID connections possible in by creating a UDP tunnel. | ''nat traversal'' Makes LowID to LowID connections possible in by creating a UDP tunnel. | ||
| − | http://wiki.emule-web.de/image/Nat-traverse-net.gif | + | [image:http://wiki.emule-web.de/image/Nat-traverse-net.gif] |
The basic tunneling procedure is: | The basic tunneling procedure is: | ||
| Line 13: | Line 13: | ||
UmTCP Sync .................. | UmTCP Sync .................. | ||
</pre> | </pre> | ||
| − | <nowiki>*</ | + | <nowiki>*</nowili> The remote callback is needed in order to tell the requester the actual UDP port of the target client. |
It is not always the case that the ping from B is dropped on FullConeNats it can pass through, there for the remote callback is delayed by a few seconds to see if A answers with a Ping. | It is not always the case that the ping from B is dropped on FullConeNats it can pass through, there for the remote callback is delayed by a few seconds to see if A answers with a Ping. | ||
| Line 22: | Line 22: | ||
Developed by David Xanatos, [[Neomule]]. | Developed by David Xanatos, [[Neomule]]. | ||
| − | [[ | + | [[category:features]][[category:NeoFeatures]] |
