[jadmin] Re: Cannot run MU-conference with Jabberd2

[Alexander Semyonov]

> The c2s and router components cannot both listen on the same port.
>
> c2s is only to allow Jabber clients to connect directly, and usually
> should be listening on port 5222.
>
> For a component connection as with mu-c, c2s is not used; the
component
> should connect to the router (presumably on port 5347)
>
> -Alex Mauer "hawke"

Hi! Sure, c2s is listening on port 5222 and 5223 (for secure
connections). This is configured in "local" section of c2s.xml. But
"router" section is not the same. Here are "router" and "local" sections
of c2s.xml. If I change port number in "router" section I can't even
connect. So, we have "router" section in c2s.xml and "local" section in
router.xml; it means that roster module is configured in two files
twice. Why? :-O

<router>
    <!-- IP/port the router is waiting for connections on -->
    <ip>127.0.0.1</ip>            <!-- default: 127.0.0.1 -->
    <port>5347</port>             <!-- default: 5347 -->
</router>

<local>
    <!-- Who we identify ourselves as. This should correspond to the
         ID (host) that the session manager thinks it is. You can
         specify more than one to support virtual hosts, as long as you
         have additional session manager instances on the network to
         handle those hosts. The realm attribute specifies the auth/reg
         or SASL authentication realm for the host. If the attribute is
         not specified, the realm will be selected by the SASL
         mechanism, or will be the same as the ID itself. Be aware that
         users are assigned to a realm, not a host, so two hosts in the
         same realm will have the same users.
         If no realm is specified, it will be set to be the same as the
         ID. -->
    <id>jabber.vitlan.com</id>
    <!-- <id realm='company'>localhost</id> -->

    <!-- IP address to bind to (default: 0.0.0.0) -->
    <ip>0.0.0.0</ip>

    <!-- Port to bind to, or 0 to disable unencrypted access to the
         server (default: 5222) -->
    <port>5222</port>

    <!-- File containing a SSL certificate and private key for client
         connections. If this is commented out, clients will not be
         offered the STARTTLS stream extension -->

    <pemfile>/etc/jabberd2/server.pem</pemfile>
    <!-- File containing an optional SSL certificate chain file for
client
         SSL connections. -->
    <!--
    <cachain>/etc/jabberd2/cachain.pem</cachain>
    -->

    <!-- Require STARTTLS. If this is enabled, clients must do STARTTLS
         before they can authenticate. Until the stream is encrypted,
         all packets will be dropped. -->
    <!--
    <require-starttls/>
    -->

    <!-- Older versions of jabberd support encrypted client connections
         via an additional listening socket on port 5223. If you want
         this (required to allow pre-STARTTLS clients to do SSL),
         uncomment this -->

    <ssl-port>5223</ssl-port>

  </local>

WBR, Alexander.