socks.8 2.1 KB

12345678910111213141516171819202122232425262728293031323334353637383940414243444546474849505152535455565758596061626364656667686970717273747576777879
  1. .TH socks "8" "January 2016" "3proxy 0.8" "Universal proxy server"
  2. .SH NAME
  3. .B socks
  4. \- SOCKS 4/4.5/5 gateway service
  5. .SH SYNOPSIS
  6. .BR "socks " [ -d ]
  7. .IB \fR[ -l \fR[ \fR[ @ \fR] logfile \fR]]
  8. .IB \fR[ -p port\fR]
  9. .IB \fR[ -i internal_ip\fR]
  10. .IB \fR[ -e external_ip\fR]
  11. .SH DESCRIPTION
  12. .B socks
  13. is SOCKS server. It supports SOCKSv4, SOCKSv4.5 (extension to v4 for
  14. server side name resolution) and SOCKSv5. SOCKSv5 specification allows both
  15. outgoing and reverse TCP connections and UDP portmapping.
  16. .SH OPTIONS
  17. .TP
  18. .B -I
  19. Inetd mode. Standalone service only.
  20. .TP
  21. .B -d
  22. Daemonise. Detach service from console and run in the background.
  23. .TP
  24. .B -t
  25. Be silenT. Do not log start/stop/accept error records.
  26. .TP
  27. .B -u
  28. Never ask for username authentication
  29. .TP
  30. .B -e
  31. External address. IP address of interface proxy should initiate connections
  32. from. External IP must be specified if you need incoming connections.
  33. By default system will deside which address to use in accordance
  34. with routing table.
  35. .TP
  36. .B -i
  37. Internal address. IP address proxy accepts connections to.
  38. By default connection to any interface is accepted. It\'s usually unsafe.
  39. .TP
  40. .B -p
  41. Port. Port proxy listens for incoming connections. Default is 1080.
  42. .TP
  43. .B -l
  44. Log. By default logging is to stdout. If
  45. .I logfile
  46. is specified logging is to file. Under Unix, if
  47. .RI \' @ \'
  48. preceeds
  49. .IR logfile ,
  50. syslog is used for logging.
  51. .TP
  52. .B -S
  53. Increase or decrease stack size. You may want to try something like -S8192 if you experience 3proxy
  54. crashes.
  55. .SH CLIENTS
  56. You should use client with SOCKS support or use some socksification support
  57. (for example
  58. .I SocksCAP
  59. or
  60. .IR FreeCAP ).
  61. Configure client to use
  62. .I internal_ip
  63. and
  64. .IR port .
  65. SOCKS allows to use almost any application protocol without limitation. This
  66. implementation also allows to open priviledged port on server (if socks has
  67. sufficient privileges). If you need to control access use
  68. .BR 3proxy (8)
  69. instead.
  70. .SH BUGS
  71. Report all bugs to
  72. .BR 3proxy@3proxy.ru
  73. .SH SEE ALSO
  74. 3proxy(8), proxy(8), ftppr(8), pop3p(8), tcppm(8), udppm(8), syslogd(8),
  75. .br
  76. http://3proxy.ru/
  77. .SH AUTHORS
  78. 3proxy is designed by Vladimir 3APA3A Dubrovin
  79. .RI ( 3proxy@3proxy.ru )