|
|
417.
|
|
|
What do the DC++-style tags mean?
|
|
|
type: Content of: <html><body><h1>
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
help/faq_plusplus_tag.html:11
|
|
|
438.
|
|
|
In most cases DC++ should be able to automatically detect the appropriate connection method for the user, however, there can still be cases when there are no ways to map the port automatically so a manual configuration required to achieve active mode. This FAQ gives detailed information how to set up port forwarding manually in case of the <a po4a-id=0> automatic connectivity setup</a> fails or you have gateway devices without <a po4a-id=1>automatic port mapping</a> support.
|
|
|
type: Content of: <html><body><p>
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
help/faq_portforward.html:11
|
|
|
439.
|
|
|
This FAQ assumes that
|
|
|
type: Content of: <html><body><p>
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
help/faq_portforward.html:19
|
|
|
440.
|
|
|
You're familiar with <a po4a-id=0>DC++ connectivity concepts</a>
|
|
|
type: Content of: <html><body><p><ul><li>
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
help/faq_portforward.html:21
|
|
|
441.
|
|
|
You already tried the <a po4a-id=0>automatic ways of port mapping</a> without success (or you are certain that you don't have supporting devices in your network)
|
|
|
type: Content of: <html><body><p><ul><li>
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
help/faq_portforward.html:22
|
|
|
442.
|
|
|
You have basic understanding of computer networking
|
|
|
type: Content of: <html><body><p><ul><li>
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
help/faq_portforward.html:24
|
|
|
443.
|
|
|
You have proper access to the configuration layout of your gateway (router) device
|
|
|
type: Content of: <html><body><p><ul><li>
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
help/faq_portforward.html:25
|
|
|
444.
|
|
|
For DC++ to work properly in active mode, it requires access on <acronym po4a-id=0> TCP</acronym> and <acronym po4a-id=1>UDP</acronym> listening ports, as well as outgoing access on all ports for both TCP and UDP. If you are in a private network behind a NAT device the incoming information to the listening ports should be forwarded to the proper computer.
|
|
|
type: Content of: <html><body><p>
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
help/faq_portforward.html:29
|
|
|
445.
|
|
|
For an in-depth, but still easy to understand explanation of port forwarding, read <a po4a-id=0>What is Port Forwarding?</a> The following steps describe the configuration of port forwarding in general as the exact configuration method and layout varies in the different type of gateway devices.
|
|
|
type: Content of: <html><body><p>
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
help/faq_portforward.html:34
|
|
|
447.
|
|
|
You need to forward three ports: 2 ports for transfers and encrypted transfers (both use TCP protocol) and one port for searches what uses the UDP protocol. You can use the same port number for transfers and searches, but <b>you need a different one for the encrypted transfers</b>. Of course you can choose different port numbers for each as well. So select two or three numbers between 1024 - 65535, they should mostly all be free. Make sure you <b>select the correct protocol types</b> (TCP, UDP or Both) for each port number when you cerate the port forwarding rules in the gateway's config interface.
|
|
|
type: Content of: <html><body><ol><li>
|
|
|
|
|
(no translation yet)
|
|
|
|
Located in
help/faq_portforward.html:45
|
