[ejabberd] limited firewall ports
brian.safford at eds.com
Thu Feb 22 17:49:37 MSK 2007
I'll try your suggestion.
I'm a bit confused about your other comment though - sendmail is able to create as many connections as it wants using the same port ... as is wildfire and jabberd2, so I don't understand why erlang does it differently. I probably am just missing some important information about how this stuff works ...
From: ejabberd-bounces at jabber.ru [mailto:ejabberd-bounces at jabber.ru] On Behalf Of Mickaël Rémond
Sent: Thursday, February 22, 2007 8:29 AM
To: ejabberd at jabber.ru
Subject: Re: [ejabberd] limited firewall ports
Le 22 févr. 07 à 13:45, Safford, Brian a écrit :
My question is this - is there any hope at all of getting the connection
from outside to inside working?
Yes, you need to configure your epmd deamon properly and your firewall.
To do that, you need to use inet_dist_listen_min and inet_dist_listen_max parameter.
Port used are 4369 + a range of port configurable with the erlang
parameter inet_dist_listen_min and inet_dist_listen_max:
For example, with:
erl -name ejabberd -kernel inet_dist_listen_min 4711 net_dist_listen_max
The distribution only requires two ports 4369 and 4711.
And my comment is ... why didn't / doesn't epmd work like most other
super-daemons? Like sendmail and inetd ... or like wildfire and
jabberd2 ... :-(
It is a portmapper daemon: You can run tens of thousands of node if you want with the normal setting and port will be correctly distributed. By definition, you do not know how many port you will need (Like the port used by a client for example).
I hope this helps,
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the ejabberd