socks.8 2.3 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384
  1. .TH socks "8" "January 2019" "3proxy 0.9" "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 -N
  37. External NAT address 3proxy reports to client for BIND and UDPASSOC
  38. By default external address is reported. It's only useful in the case
  39. of IP-IP NAT (will not work for PAT)
  40. .TP
  41. .B -i
  42. Internal address. IP address proxy accepts connections to.
  43. By default connection to any interface is accepted. It\'s usually unsafe.
  44. .TP
  45. .B -p
  46. Port. Port proxy listens for incoming connections. Default is 1080.
  47. .TP
  48. .B -l
  49. Log. By default logging is to stdout. If
  50. .I logfile
  51. is specified logging is to file. Under Unix, if
  52. .RI \' @ \'
  53. preceeds
  54. .IR logfile ,
  55. syslog is used for logging.
  56. .TP
  57. .B -S
  58. Increase or decrease stack size. You may want to try something like -S8192 if you experience 3proxy
  59. crashes.
  60. .SH CLIENTS
  61. You should use client with SOCKS support or use some socksification support
  62. (for example
  63. .I SocksCAP
  64. or
  65. .IR FreeCAP ).
  66. Configure client to use
  67. .I internal_ip
  68. and
  69. .IR port .
  70. SOCKS allows to use almost any application protocol without limitation. This
  71. implementation also allows to open priviledged port on server (if socks has
  72. sufficient privileges). If you need to control access use
  73. .BR 3proxy (8)
  74. instead.
  75. .SH BUGS
  76. Report all bugs to
  77. .BR 3proxy@3proxy.ru
  78. .SH SEE ALSO
  79. 3proxy(8), proxy(8), ftppr(8), pop3p(8), tcppm(8), udppm(8), syslogd(8),
  80. .br
  81. https://3proxy.org/
  82. .SH AUTHORS
  83. 3proxy is designed by Vladimir 3APA3A Dubrovin
  84. .RI ( 3proxy@3proxy.ru )