[Spacewalk-list] jabberd - router listens only on tcp6
Robert Paschedag
robert.paschedag at web.de
Tue Feb 7 05:47:46 UTC 2017
Am 7. Februar 2017 00:19:10 MEZ schrieb Konstantin Raskoshnyi <konrasko at gmail.com>:
>Hi folks,
>
>I disabled ipv6 on Rhel7 since I had some problems with proxies,
>for some reasons jabberd-router listens only on tcp6 during startup, I
>check config files and didn't find anything suspicious,
>
> <!-- Local network configuration -->
> <local>
> <!-- IP address to bind to (default: 0.0.0.0) -->
> <ip>::</ip>
>
> <!-- Port to bind to (default: 5347) -->
> <port>5347</port>
>
> <!-- File containing the user table. This is where the router gets
> its component and secret information from for component
> authentication.-->
> <users>/etc/jabberd/router-users.xml</users>
>
> <!-- Shared secret used to identify XEP-0114 components (that is,
> "jabber:component:accept" components that authenticate using
> the Jabber Component Protocol's "handshake", for example
> mu-conference). If this is commented out, support for XEP-0114
> components will be disabled. -->
> <secret>cfd1bee12672e7f7e6abe34c4aec00f6b5963259</secret>
>
> <!-- File containing an SSL certificate and private key for client
> connections. From SSL_CTX_use_certificate_chain_file(3):
> "The certificates must be in PEM format and must be sorted
> starting with the subject's certificate (actual client or
> server certificate), followed by intermediate CA certificates
> if applicable, and ending at the highest level (root) CA"
> (the latter one being optional).
> If this is commented out, connecting components will not be able
> to request an SSL-encrypted channel. -->
> <!--
> <pemfile>/etc/jabberd/server.pem</pemfile>
> -->
> </local>
>
>Any thoughts?
The "::" explicitly sets ipv6 here. Try setting it to "0.0.0.0".
Regards
Robert
More information about the Spacewalk-list
mailing list