3proxy and UDP support. True story?
Hey you nice bunch of people!
Soo, since Socks5 is supposed to support TCP and UDP connections and 3proxy claims to respect the protocol (https://www.ietf.org/rfc/rfc1928.txt), I was thinking about setting up a socks proxy for torrenting.
Saldly it doesn't seem to be working for me. 3proxy opens just a TCP port with "socks -p(port)", I wonder why? The only way I found to open a UDP port, is to use "udppm", but this expects a host and port to resolve to - not very useful for torrenting. I also tried to relay the traffic to some other proxy servers (dante, antinat), with no success.
The question is now: Am I simply incapable of setting up such a simple proxy or is 3proxy not capable of this task?
Thank you in advance for your help.
PS: Please do not suggest alternative ways of setting this up. I am doing this just for fun and I'm trying to understand why the socks5 protocol seems to be incompatible with this scenario. I'm only interested in socks5 + udp, thank you.
EDIT, forgot to attach the config file:
This script uses google NS by default
Leave default cache size for DNS requests:
Leave default timeout as well:
timeouts 1 5 30 60 180 1800 15 60
Provide the IP-address to be listened
If you ignore this line, proxy will listen all the server’s IP-addresses
Define user and password
Specify daemon as a start mode
and the path to logs, and log format. Creation date will be added to a log name
log /var/log/3proxy.log D
logformat "- +_L%t.%. %N.%p %E %U %C:%c %R:%r %O %I %h %T"
Compress the logs using gzip
archiver gz /usr/bin/gzip %F
store the logs for 30 days
enable strong authorization
udppm port ip port
Purge the access-list of http-proxy
set the maximum number of simultaneous connections to 80
run socks on -p port
socks -p (port)
Nobody helpy helpy me?
Soooooooo any hints today?
Please pastebin your config, vanilla code tags suck.
Thanks so much for your reply. Good idea!
Here you go: http://pastie.org/private/1pwrbh5q1jewyiguwft0ga
Any help is greatly appriciated!
Use ~~~ before and after code:
Good advice, thanks! Sadly I can't edit the first post anymore.
An UP a day keeps the DDOS away!
Well, you are right UDP associate is supported
!!! UDP associate finaly completed and is fully functional (2003)
UDPASSOC is the same as CONNECT, but that should be compatible with the CLIENT and not the SERVER, even if the server supports it if the client does not use it it's useless. If you are getting TCP connects it means the client is using the CONNECT feature to try to connect to the hosts, it's got nothing to do with the proxy server.
About udppm, here is some more info:
For example if you set this:
udppm -s 53 184.108.40.206 53
when you do "nslookup google.com 127.0.0.1" it should connect to google's name servers, I do not know if this would work with trackers, I never tried but you could try
udppm 3333 fr33dom.h33t.com 3310
And then use 127.0.0.1:3333 as the tracker.
Anyway, I never tried this but you said you wanted to experiment.
Thanks, will try it for sure asap!