hello all,
I run a small community, and file trasnfert works for almost nobody, in our country france, lot of people have routers provided by their isp but don't know how to configure it, they just plug it and it works.
So does anyone know how to setup a good system for file transferts on my clients (gajim, psi, etc) or ejabberd without having to configure the router ?
Because asking my community to setup a port on their router is a pain and impossible to imagine (most of them don't know what is a router :) )
I tried to use a client like gajim with proxies but ports are blocked also.
MSN and SKype works wells everywhere, I think they use different system to transfert files, someone told me skype use port 80.
Would it be dumb to setup all my clients on port 80 for file transferts ?
May be I should setup something on ejabberd server to use it as a proxy (mod_proxy65) and configure something to figure this out.
Hope get some help :)
Best regards
K.
Re: file transfert without configuring router port
May be I should setup something on ejabberd server to use it as a proxy (mod_proxy65) and configure something to figure this out.
Yes, you can set up mod_proxy65, but note that ejabberd should not be located behind a NAT in this case. You can assign a broad available port on it (such as 80/tcp or 443/tcp) and a file transfer will always work.
gajim, psi
All of them support proxy65, but not by default. You just need to configure it.
tryed without success
hello,
thx for your help,
I setted up the mod_proxy65, I can see it in discover services, I tryed telent myserver.com 443 and I receive somthing. I also disabled firewall on my server for tests.
But I still have error on my client, cannot transfert files. same files works fine in local.
ejabberd is on a server not behind a nat.
config is :
{mod_proxy65, [
{host, "proxy.XXXMY_SERVERXXX.com"},
{port, 443}
]},
I used gajim and configured proxy as "proxy.myserver.com" port 443
any other idea ?
Re: file transfert without configuring router port
I used gajim and configured proxy as "proxy.myserver.com" port 443
You should configure "bytestreams proxy" or something, not just proxy for general jabber connection. Also look into ejabberd log: you should see log messages from the proxy service there.
I found the bug !
thx zinid,
in fact I have tryed with an another client and the transfert worked.
So I turned on the xml console to see if something was different and my test client did not send the famous streamhost line of my proxy, it just send his ip to connect in p2p. I have patched my client and all works fine now.
thx for your idea to look into the jabberd log, it give me the idea to look in the xml console of my client ;)
regards,