|
1782
|
1 #summary XEP-0065: SOCKS5 Bytestreams file transfer proxy |
|
|
2 #labels Stage-Beta, Deprecated |
|
|
3 |
|
|
4 = Introduction = |
|
|
5 |
|
|
6 mod_proxy65 implements XEP-0065: SOCKS5 Bytestreams as a component. It allows the server to proxy file transfers between 2 clients that are behind NAT routers or firewalls, and otherwise wouldn't be able to transfer files. |
|
|
7 |
|
|
8 = Details = |
|
|
9 Once set up, depending on which client you are using the proxy may be automatically used, or the client may have to be configured. Consult your client's friendly documentation for more information :) |
|
|
10 |
|
|
11 = Usage = |
|
|
12 {{{ |
|
|
13 Component "proxy.example.com" "proxy65" |
|
|
14 }}} |
|
|
15 |
|
|
16 = Configuration = |
|
|
17 Although none are required, under the Component section mod_proxy65 understands several configuration options: |
|
|
18 |
|
|
19 ||proxy65_interface||The server's interface (IP address) to bind (listen) on (default is "`*`", meaning all interfaces)|| |
|
|
20 ||proxy65_address||The advertised address of the proxy, which clients use to connect to (default is the same as the hostname of the component)|| |
|
|
21 ||proxy65_port||The port on the server to which clients should connect (default is port 5000)|| |
|
|
22 ||proxy65_acl||Access Control List, when specified all users will be denied access unless in the list. The list can contain domains, bare jids (normal) or full jids (including a resource). e.g. proxy65_acl = {"example.com", "theadmin@anotherdomain.com", "only@fromwork.de/AtWork"}|| |
|
|
23 |
|
|
24 = Compatibility = |
|
|
25 ||0.7 and above||Officially included in Prosody|| |
|
|
26 ||0.6||Works|| |
|
|
27 ||0.5||Should work|| |
|
|
28 |
|
|
29 = Todo = |
|
|
30 * Optional support for UDP connections |
|
|
31 * Statistics, bandwidth limits/monitoring |
