Mod_proxy65 not listen...

Hello all,
I've a fully working ejaberd installation under Debian Lenny;

I'm trying to use Mod_proxy65 to support filetransfer also with clients outside LAN, but I don't know why it is not started.

this is the configuration:

{mod_proxy65, [
%% {name, "SOCKS5 Bytestreams"}
%%{access, local}
%%{shaper, c2s_shaper}
]},

(commented lines 'cause I want start with simpliest configuration)

If I telnet on my ejabberd server on 7777 port I get a connection refused

I'm missing something?

Thank you very much for support.

Umberto

www.hacksandmore.com

That configuration should

That configuration should work.

Start ejabberd, and you should see many PROGRESS REPORT, some should refer to proxy65. Or you may find errors.

crash wrote:

If I telnet on my ejabberd server on 7777 port I get a connection refused

With your configuration I get:

$ netstat -nlp | grep beam
(Not all processes could be identified, non-owned process info
 will not be shown, you would have to be root to see it all.)
tcp        0      0 0.0.0.0:5269            0.0.0.0:*               LISTEN      15395/beam.smp
tcp        0      0 0.0.0.0:5280            0.0.0.0:*               LISTEN      15395/beam.smp
tcp        0      0 127.0.0.1:7777          0.0.0.0:*               LISTEN      15395/beam.smp
tcp        0      0 0.0.0.0:5281            0.0.0.0:*               LISTEN      15395/beam.smp
tcp        0      0 127.0.0.1:5222          0.0.0.0:*               LISTEN      15395/beam.smp
tcp        0      0 127.0.0.1:58728         0.0.0.0:*               LISTEN      15395/beam.smp
tcp        0      0 0.0.0.0:4560            0.0.0.0:*               LISTEN      15395/beam.smp

and I can telnet:

$ telnet localhost 7777
Trying 127.0.0.1...
Connected to localhost.
Escape character is '^]'.
asdasdasd
Connection closed by foreign host.

In that moment, ejabberd logs this:

=INFO REPORT==== 28-Feb-2011::19:47:15 ===
I(<0.334.0>:ejabberd_listener:281) : (#Port<0.4386>) Accepted connection {{127,0,0,1},47835} -> {{127,0,0,1},7777}

Thank you, found the problem,

Thank you,
found the problem, proxy65 was listening only on 127.0.0.1 (as default);

I've changed to listen on 0.0.0.0 and now is working.

Umberto

SPAM

Syndicate content