[ejabberd] ejabberd opening unperdictable high number ports

zhong ming wu mr.z.m.wu at gmail.com
Sat Nov 27 04:02:48 MSK 2010


Apart from c2s and s2s ports, ejabberd seems to be listening on one
high numbered tcp port.
That port number seem to be different from one start/stop cycle to another.  Can
someone explain the implications for this?  My current firewall rule
automatically blocks these
ports.   These port numbers are not listed in /etc/services.

Unrelated to the above issue, what is the implication of blocking 4369
(erlang port mapper) which
seems to be opened with ejabberd usage.

I am using centos 5.4

Thanks in advance


More information about the ejabberd mailing list