NAT Traversal Compatibility Survey

Search support for NAT traversal has landed in the DC++ trunk. It’s not yet in any unstables builds, but it should show up in Toast’s ADCPortal build archive shortly as DC++ revision 2160 or later. Passive mode automatically enables NAT traversal; there’s no explicit setting for it. If it works, two passive users are able to communicate directly with each other via a client-client TCP connection and search and transfer files between each other.

The DC++ developers are interested in the success or failure of NAT traversal depending on individual conditions. In particular, router model and operating system have a large impact. Thus, anyone trying this feature (it requires that both involved clients support NAT traversal) is encouraged to describe their results in the DCDev Public hub at adcs://devpublic.adcportal.com:16591 or the ADC Portal forums with their operating system, router setup, and degree of success.

5 Responses to NAT Traversal Compatibility Survey

  1. emtee says:

    Peer 1. WinXP x86 SP2, Router model Edimax BR-6204WG
    Peer 2. Win 7 x86 Starter Edition, Router model D-Link DIR 655
    Both peers ran DC++ bzr rev 2165

    Search worked for both peers. Transfer worked at once from Peer 1. to Peer 2.

    It needed some time to get a successful transfer in the other way. Tried right after the upload finished to Peer 2., got ‘SocketException: Only one usage of each socket address (protocol/network address/port) is normally permitted’ for about 3 minutes. That’s normal I suppose, at least from the explanation in the posts about NAT-T.
    Then I got various other exceptions like ‘Thrown: SocketException: A connection attempt failed because the connected party did not properly respond…’ and SSL errors for another 2 minutes.
    After these I got a successful transfer from Peer 2. to Peer 1. Both transfers were secure and the GUI did not show any error just Connecting… and Disconnected.

  2. emtee says:

    Test #2

    Peer 1. WinXP x86 SP2, Router model Edimax BR-6204WG
    Peer 2. WinXP x86 SP3, Router model Sagem F@st 3464

    Result is the same as above except that ‘Only one usage of each…’ messages took only 2 mins and then I could connect at once.

  3. emtee says:

    Test #3

    Peer 1. WinXP x86 SP2, Router model Edimax BR-6204WG
    Peer 2. WinXP x86 SP3, Router model 2Wire 1701HG

    Search worked for both peers.

    Transfers worked only once after Peer 2. restarted his client. Filelists transferred from each other without any long waiting between the two transfers but no other transfers worked for any subsequent retries.

    Edit: it turned out that Peer 2. has other connection problems so may this test is not relevant.

  4. emtee says:

    Test #4

    Peer 1. WinXP x86 SP2, Router model Edimax BR-6204WG, StrongDC++ svn500
    Peer 2. Win Vista x86, Router model D-Link DIR 635, DC++ 0.770

    Search & transfers passed without problems.

  5. emtee says:

    Test #5

    Peer 1. WinXP x86 SP3, Router model Edimax BR-6204WG, StrongDC++ svn500

    Peer 2. WinXP x86 SP3, Router model Thomson TG789vn, DC++ 0.770

    Search works but no transfers in any direction. This is the first problem where it doesn’t work for me with a brand new router device on the other side.

Leave a Reply

Please log in using one of these methods to post your comment:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s

%d bloggers like this: