Main Page

From ADCPortal Wiki

Jump to: navigation, search
I
This wiki is a read only resource for unregistered users. Before using any of the content provided please ensure that the intended use follows the terms of the GNU FDL.

Welcome to ADCPortal Wiki

Welcome to our Wiki for ADCPortal and the ADC Protocol development
We have exactly 58 articles and we have 22 Contributers.
ADCPortal wiki has a complete encyclopedia of the software that supports ADC Protocol and the Extensions that are already implemented or drafting. For asking questions about any of the material presented here, please visit ADCPortal and ask them in there.

Featured Article: NATT - NAT traversal

NATT - NAT traversal

NAT traversal allow two passive clients to connect to each other. For more information about NAT traversal[1][2].

If a client does not support TCP4 or TCP6, it will send an RCM to the client it is trying to connect to. If the other client also doesn't support TCP4 (or TCP6 correspondingly), NAT traversal may instead be used. The feature should be signalled in SUP as NATT.

Do note that the hub must forward I4 or I6 for respective clients' INF.

BASE RCM updates

When receiving an RCM and the client does not support TCP4 or TCP6, and if NAT-T is supported in the remote client, a NAT command should be sent repeating the protocol and token. The port shall be the outbound port to the connected hub.

NAT

NAT protocol port token

Contexts: T

States: NORMAL

Upon receiving this, try and connect to the specified port. An RNT command should be sent repeating the protocol and token. The port shall be the outbound port to the connected hub. Upon receiving this, try and connect to the specified port.

RNT

RNT protocol port token

Contexts: T

States: NORMAL

Upon receiving this, try and connect to the specified port.

Example

Client A is connected to hub A with the outbound port 1000 and client B is connected to hub A with the outbound port 2000. Client A has the SID AAAA and client B has the SID BBBB.


Client A: DRCM AAAA BBBB ADC/1.0 foobar Client B: DNAT BBBB AAAA ADC/1.0 2000 foobar
<Client A connects to client B's IP address and port 2000>
Client A: DRNT AAAA BBBB ADC/1.0 1000 foobar
<Client B connects to client A's IP address and port 1000>

References

  1. ↑ NAT Traversal Constraints by Cologic (Jun 15, 2010)
  2. ↑ Passive Mode C-C Connections and NAT Traversal by Cologic (Feb 13, 2010)

Links

NAT Traversal Compatibility Survey

ADCPortal Information

ADCPortal wiki was started to document ADC Protocol and history with the help of its developers.

It tries to be as relevant as possible so that everybody has a good picture of how ADC works. The purpose is that users are be able to get in touch with latest software news, development, or to learn the protocol and its extensions, or even how to create their own applications using ADC. For info on how to contribute look below.

Wiki News

Wiki loading slowly

We wanted to acknowledge that we are aware of the wiki loading slow as hell and we are trying to resolve the issue --Toast 19:35, 19 July 2009 (UTC)

We're back

Wiki is back in stable service sporting with a few new extensions for your convenience please see this page for further details -- Crise 23:34, 16 March 2009 (UTC)

More patches

Some bugfix patches have been applied from developement versions, also added some wikipedia style editor mods -- Crise 13:34, 15 March 2009 (UTC)

More…

Articles

Additional Sections

Contribute!

This Wiki is a reg-only based. Accounts may be requested from the forum (see request link).

And for those that do not wish to have an account but still submit articles we have a suggestion thread on the forum (see suggestion link).

Retrieved from "http://www.adcportal.com/wiki/index.php/Main_Page"
Personal tools