help

[roadkill]

i have an isu about dowloding fillist from my fellow airdc 2.04 users
can som help me 2 fix that problem

[Yada]

If you are using a router then create a new TCP port forwarding and type that port number in the TLS box.

[roadkill]

tnx agane i working fine now

[spaljeni]

did not fix the problem

[en_dator]

spaljeni, do you mean that you have three ports correctly set up and you still can not download filelists from other users of last AirDC++ version?
only from this client or other clients like StrongDC++ 2.21 as well?

Can other ppl download that list that you can not?


next time spaljeni could you please create a new topic with a specific issue?

[KaKtuScAr]

i solved this by disabling "use tls when remote client supports it"

i'm pretty sure i set up my connection settings well otherwise :|

[KaKtuScAr]

ok, so after a talk with night, i set a different port for each protocol, turned tls back on, and it works fine.... so... that's kinda in contradiction to yada's advice here :)

[en_dator]

While most of dc is pretty simple and straight forward, the thing with ports seems to be the one thing that many people get confused about, and rightly so as it is not normally something you deal with. Other types of application (like torrents and IM clients) usually handle this by themselves without help from the user. Here dc is a bit different and it requires a little work from you as a user.

The three little boxes where it says TCP, UDP and TLS is the next thing we need to take care of, and it is here where things start to get tricky. If you know how to set up NAT (or portforwarding) for your router then just go ahead and do so, I suggest you use three different port numbers in the range from 1024 to 65536. If you dont understand what NAT or port forwarding is here are two external links that will explain it all http://en.wikipedia.org/wiki/Port_forwarding and http://en.wikipedia.org/wiki/Network_ad ... ranslation .

Above quote is from the HOWTO about ports that is sticky in this forum.

While there is no technical reason for using a different number for the TCP and UDP port, it seems that it does eliminate some problems that (I beleive) is caused by some routers. The port number for TCP and TLS must of course be different from eachother as they both are tcp ports. If you do not understand this then you do not know what port forwarding and NAT is.