I read the doc (), and it's saying that
"This module implements SOCKS5 Bytestreams (XEP-0065). It allows ejabberd to act as a file transfer proxy between two XMPP clients."
Does this mean ejabberd WILL create the proxy server, and host is proxy.machine1.abcd.com?? Or I need to install other proxy server (like squid) on machine1.abcd.com?
The module mod_proxy65 has been configured to be follows:
{mod_proxy65, [{host, "proxy.machine1.abcd.com"},
{name, "File Transfer Proxy"},
{port, 7777},
]},
ping proxy not work.... If
ping proxy not work....
If mod_proxy65 will activate the proxy server, why I can NOT ping proxy.machin1.abcd.come after ejabberd restarts? It shows:
ping: cannot resolve proxy.machine1.abcd.com: Unknown host.Is that normal? Or I should setup other things to tell xmpp client where is the proxy server.
Short answer is: Yes it WILL
Short answer is: Yes it WILL act as proxy.
Long answer is below :)
As far as I can understand this XEP is supposed to create simple socket proxy which implies p2p-like connection but instead of peer for the opposite side in at the negotiation stage server one is used. In other words, when client1 wants to reach client2 server opens two sockets on its side and makes "bridge".
You _can_ use for this purpose TURN server which does conceptually the same thing but works independently of server as separate service. I could not find working implementation though... Psi+ declares support but I couldn't find working TURN server for it.
Good luck!