Hello,
I have installed ejabberd 1.1.2 on our company server. We are behind NAT.
So far messaging works smoothly, we have set 5223 and 8010 ports on our NAT, so we can connect from outside and send files if one of the nodes has a public IP. But when someone is behind a proxy (in another company) and wants to send me a file, it is not possible. We need a file transfer proxy. And why should we use proxy.jabber.org, when we have our own ejabberd server, so it should be possible to set up a file proxy on it, right?
So my question is: how to configure a file transfer proxy in ejabberd? I haven't found even the word "proxy" in ejabberd.cfg.
As far as I know, there are
As far as I know, there are three options. You could use themy , or you could use Proxy65 , a proxy written in Python.
mod_proxy65
in ejabberd SVN (not sure if it would work in 1.1.2 without changes), or you could usemod_proxy65
implementationNot present in SVN
I have downloaded the whole ejabberd repository with SubVersion (you know, the command "svn co https://svn.process-one.net/ejabberd-modules"), but the mod_proxy65 is not in there. What is the difference between this one and your implementation?
It's in ejabberd itself
I have downloaded the whole ejabberd repository with SubVersion (you know, the command "svn co https://svn.process-one.net/ejabberd-modules"), but the mod_proxy65 is not in there.
It's in ejabberd itself, not in the modules tree.
What is the difference between this one and your implementation?
Not really sure, I actually never tried Евгений's implementation ☺ But from a brief look at the code it seems to handle more corner cases and such.
part of ejabberd?
I haven't found mod_proxy65 anywhere within ejabberd directory either. Do you mean it is compiled into the ejabberd? How to configure it then?
I have ejabberd 1.1.2 for Windows, ain't that a problem?
Hello, proxy65 is in the
Hello,
proxy65 is in the development version of ejabberd and in the upcoming new ejabberd stable release.
It is thus not included in ejabberd 1.1.2 or 1.1.3
--
Process-one
Mickaël Rémond