Quote:Single port + multiple

mfoss — Sun, 16 Nov 2008 19:18:49 +0000

Quote:

Single port + multiple IPs

Not possible yet: Impossible to bind the same port to multiple interfaces. You can configure ejabberd to listen in a port for all IPs, or for a certain IP.

It isn't possible to restrict users of a vhost to a certain port.

If you are ready to use so many different ports numbers and IP addresses, you can install ejabberd several times in different directories, and configure each one to use different ports (and to have different erlang node names). They will act independently.

Nope! Virtual hosts is only a simulation. What for?

nu3ga — Wed, 12 Nov 2008 16:37:49 +0000

I've tried the variant with separated Databases:
hosts: vhost1, vhost2
users: user01, user02(names duplicated at both servers)
So, as a result(example) user01@vhost1 list:
user01@vhost2
user02@vhost1
user02@vhost2
Everybody can freely contact each other. The only difference is that offline messages are stored at recepient's side(database). That's pretty logical.
But I'd like vhosts work like servers(using s2s_* rules). Or that's not so logical?

`mod_filter' is not applicable for this aim without appropriate revision, because now it can process only lacedone(last) chain of rules, named mod_filter, so even if we can deny vhost1-to-vhost2 traffic, we can't deny backwards.

The single "normal"(superfluous, but working) method, I could discover, is :

create separate databases for each "virtual"-host

create separate ejabberd-conficurations

create separate ejabberdctl-configurations*)

run each config on separate --node

________________________
*) This one must contain ERLANG_NODE=s@localhost with node name from p.4. WARNING! Extraspecify host in every parameter to make Erlang engine work correctly, while using ejabberdctl-utility.

At the and to simplify use, I propose simple scripts, which can be modified for definite purposes
ctl.sh:

#!/bin/sh
C="$1"
R="$2"
Rs=""
if [ -n "$R" ]
then
    Rs="_$R"
else
    R="ejabberd"
fi
pw=`pwd`
cm="$pw/ejabberdctl
    --config /usr/home/jabber/etc/ejabberd/ejabberd${Rs}.cfg
    --ctl-config /usr/home/jabber/etc/ejabberd/ejabberdctl${Rs}.cfg
    --node ${R}@localhost
    --spool /usr/home/jabber/var/lib/ejabberd/${R}
    ${C}"
echo "$cm"
$cm

and one of super-script start.sh:

#!/bin/sh
pw=`pwd`
cm="$pw/ctl.sh start $1"
$cm

Usage:
ctl.sh <action> [node]
start.sh [node]
node is an optional parameter(when skipped, `ejabberd' is default), which means --node [node]@localhost parameter and(!) usage of specified configuration files and directories:
--config ejabberd_[node].cfg
--configctl ejabberdctl_[node].cfg
--spool ejabberd/[node].cfg
Scripts should be put into the same directory with standard ejabberdctl-script. All directories should be changed to appropriate values, of course.

So, this method also decides Single_port-to-Multiple_IPs mapping, because {listen}-tag is specified independently.

Thanks. Good Luck.

ejabberd - Comments for "Single port + multiple IPs / Virtual hosts"

Quote:Single port + multiple

Nope! Virtual hosts is only a simulation. What for?