[jadmin] Re: s2s connection problem

[Andre M.]

Hello

- Yes, both server I used to test have a FQDN (application-factory.de 
and devground.de) which can be resolved at least by minimal the first 
and secondary DNS. For the first of the FQDN I added the SRV DNS records.
Both server can connect under the FQDNS's

- Yes, both are resolvable at minimal by 2 DNS

- ? Both server are set with the s2s section of the standard Debian Etch 
  Stable Release installation. I installed Jabber out of the apt-paket 
jabber

It is set to:

   <!--
   The following 's2s' config handles server connections and
   dialback hostname verification.  The <legacy/> element is
   here to enable communication with old 1.0 servers. The
   karma settings are a little higher here to handle the
   higher traffic of server-to-server connections (read
   the io section below for more details, medium settings).
   -->

   <service id="s2s">
     <load>
       <dialback>./dialback/dialback.so</dialback>
     </load>
     <dialback xmlns='jabber:config:dialback'>
       <legacy/>
       <!-- Use these to listen on particular addresses and/or ports.
       <ip port="7000"/>
       <ip port="5269">127.0.0.1</ip>
       -->
       <ip port="5269"/>
       <karma>
         <init>50</init>
         <max>50</max>
         <inc>4</inc>
         <dec>1</dec>
         <penalty>-5</penalty>
         <restore>50</restore>
       </karma>
     </dialback>
   </service>

is there more to set that s2s work anywhere ?

- Port 5269 is opened in the iptables, both server

when sending a message (that will bounce) it shows in netstat:

(server 1)
tcp        0      0 af5.applica:xmpp-server af3.application-f:43807 
VERBUNDEN  jabber     1212414419 1419/jabberd

(server 2)
tcp        0      0 af3.applica:xmpp-server af5.application-f:44778 
VERBUNDEN  jabber     1272573647 1929/jabberd

(please note: af5 is the reverse dns name auf devground.de, af3 the 
reverse dns of the host which host jabber for application-factory.de)

telnet on 5269 opens a connection (but I get introductional response 
after the connect, like a name, version or anything else from the 
server, only open connection and ready to accept input - don't know what 
to type to provocate a output from the server.

By the way I enabled ssl for clients on one of the server, and on the 
other not. As I read from the documentation I understood that this is 
only for clients (what, by the way, work for the clients ok). Could this 
make problems that one of the server which has enabled ssl try to 
connect by ssl to the other who has no ssl (and so, no cert or key, too) ?

Andre

Peter Saint-Andre schrieb:

> On Thu, Jul 12, 2007 at 09:33:16PM +0200, Andre M. wrote:
>> Hello together
>>
>> i'm just using and configuring a jabberd 1.4.3 out of the Debian Etch
>> Stable Release.
>>
>> The Jabber Server seems to work fine except for the transport of
>> messages to other jabber server.
> 
> We can ask some standard questions:
> 
> - Is your server a fully qualified domain name?
> - It is resolvable from outside your local area there?
> - Does your config file include the s2s bits?
> - Is port 5269 open?
> 
> Maybe ssh to another machine somewhere and try this:
> 
> telnet yourserver.tld 5269
> 
> /psa