Hi all,
I've just installed ejabberd 2.0.5 (x86_64 rpm package for OpenSuSe 11.2) and configured server with LDAP authentication. Now the server is up and running. The users can chat with no problem but the file transfer between clients (pidgin-pidgin, for example) is not working!! However, the mod_proxy65 line in the ejabberd.cfg configuration file is commented out. Is there necessary any additional configuration? Any help would be much appreciated!!
Thanks, in advance!
File transfer is negotiated
File transfer is negotiated between the clients: if they can connect directly, they transfer directly. In case of NAT, firewalls, then they try to use a proxy.
Maybe you need to configure in the clients the "file transfer proxy address".
Re: File Transfer is negotiated
Hi,
I've tried with clients (pidgin) in the same LAN and the file transfer worked fine. Just left uncommented "{mod_proxy65, []}" and in the client set the file transfer gateway to proxy.jabber.org:7777, but set the proxy options field to "No proxy". Now if I want the transfer to work with clients using NAT I have to configure a proxy, haven't I? In this case, have I to configure the ejabberd server as a proxy using the different parameter available in "{mod_proxy65, ...". Besides, at the client side have I to set the field "connect to server" to my ejabberd server, and tell that uses a proxy of SOCKS5 type and as a port uses 7777 and give it a username and a password??
Thanks,
Javier Marta
Your client can use two proxies, for different things
Don't confuse a proxy to connect to port 5222 (you don't need, and in fact ejabberd doesn't implement such thing) with a file transfer proxy (your NATted clients need that, and ejabberd implements a file transfer proxy in mod_proxy65). Your client will allow you to define two proxies, but remember they are for different tasks: one is to connect to the server in case of NAT, the other is to transfer files in case of NAT.
I can't help more because in fact I never used the file transfer proxy.
Re: Your client can use two proxies, for different things
Thanks badlop! You're right, I only need to configure a "proxy (gatweway) file tranfer" for being used by my NAT clients! When I get the server ready for production and could be accessed from Internet I'll do more trials! In the meantime all works fine inside the corporate LAN and the file transfer is done peer to peer. I've fixed the listen port in the clients (pidgin) to 8010 in order to client's PC firewall could filter unnecessary unused ports!
Ciao, and Happy New Year!!
J. Marta