aMule Forum
English => Feature requests => Topic started by: sergiogg on January 14, 2005, 04:58:05 PM
-
hi
i'm sorry about my english, but I think, that's the best way.
i've been using amule many time, and i wanna request a new feature.
that's an option to reject tcp conections thru a filtered port
in this way people with this "problem", could download (with lowid), but ...
thanks, bye
-
Please elaborate.
-
ok (sorry about my english again)
for example, the most common ports, 4662 and 4661 are filtered in some countries, because of legal problems with p2p or because of the problems with de bw of the ips.
note: in a filtered port, you can estabilish a conection, but the router sometimes discard packets, and you loose these conections because of timeout. and obviously you can't upload/download nothing, or only a bit.
it would be ok an option to add ports manually one time you start the program (for example in preferences), not to implement directly in the code (this is my case ;() with an "if" saying that conections with servers or clients thru these ports are rejected.
greetings
-
Ah. I see. However I don't understand why you simply don't just specify a new set of ports in the preferences. Shouldn't that accomplish the same thing?
-
hi again
yes, i can specify a new port in prefereces, but these are MY ports, the problem is the ports of the others (clients and servers). i dont wanna conect servers with 4661 and 4662 and i dont wanna conect clients with theses ports ...
mi code changes (basically adds) afects to this functions ...
BaseClient.cpp --> CUpDownClient::TryToConnect
(dont conect with a client with filtered ports)
PartFile.cpp --> CPartFile::AddSources
(reject conections with a server with filtered ports)
PartFile.cpp --> CPartFile::AddClientSources
(reject sources with a client with filtered ports)
ServerSocket.cpp --> CServerSocket::ConnectToServer
(dont conect to servers with filtered ports)
but i have some doubts, becase i program in c (only a little) but, not in wx (perhaps with time ...)
-
Oh, sorry, I misunderstood you then. I thought you were talking about incoming connections (connections from other clients to your port 4662), not the other way around.