What port-range in the firewall of a Socks (e.g. JSocks) server?
843790Oct 28 2008 — edited Oct 29 2008Hi there,
I am using the JSocks implementation of a socks v5 server.
Some of my questsions are quite general (not only specific to JSocks) and I hope that someone knows the answer. Unfortunately the forum of JSocks (sourceforge) is only rudymentary so I think this place is better to answer my questions.
However...
As I understand the socks proxy, the server waits on a specific port - normally 1080 and processes the client requests (bind, connect, accept...).
For example one client requests a bind. Then the socks server opens a port locally on the socks host and (if successful) replies the new listening port and ip to the requesting client. ...
(Forget authentication, cascaded proxies and ip-ranges at this point!)
Now, if other clients should be able to access this port, the firewall (if any) needs to allow connection to this port.
My questions:
What should be an adequate port range for the socks proxy? With other words: what is the port range of the new ports that are created for the requesting clients?
How schould a seperate firewall be configured not to conflict with a socks proxy?
Specific to JSocks (if somebody knows this he wins a virtual cookie): What is the port range that JSocks uses if it opens (generates) new ports for its clients?
Where is the port range defined in the jsocks - I havent found any?
Imagine that on the same machine there are other running applications that are listening on predefined ports. (e.g. 8080, 21, ...) - what is the best way to exclude the ports in jsocks?
Any hints and explanations are welcome!
Edited by: krafzig on Oct 28, 2008 8:27 AM