[Operators] S2S problems

[Torsten Reichard]

Hey Peter,

seems to be good.


===SCHNIPP==>
=INFO REPORT==== 2013-09-13 09:08:26 ===
I(<0.4719.2>:ejabberd_s2s:404) : New s2s connection started <0.6307.2>

=INFO REPORT==== 2013-09-13 09:08:26 ===
I(<0.6307.2>:ejabberd_s2s_out:1203) : Trying to open s2s connection:
ch3kr.net -> jabber.ccc.de with TLS=true

=INFO REPORT==== 2013-09-13 09:08:26 ===
I(<0.2255.0>:ejabberd_listener:281) : (#Port<0.71777>) Accepted
connection {{193,110,90,42},34318} -> {{192,168,122,101},5269}

=INFO REPORT==== 2013-09-13 09:08:26 ===
I(<0.6307.2>:ejabberd_s2s_out:365) : Connection established: ch3kr.net
-> jabber.ccc.de with TLS=true
<==SCHNAPP===


Maybe a DNS problem..?

jabber.ccc.de > 193.110.90.23
_xmpp-server._tcp.jabber.ccc.de > jabberd.jabber.ccc.de > 193.110.90.42


Am 13.09.2013 08:49, schrieb Peter Schwindt:
> Folks,
> 
> can anyone please have a look at the S2S connections regarding 
> jabber.ccc.de (my box)? I have quite a number of other operators' 
> reports of disfuctional S2S.
> 
> AFAICS the only thing I changed in the last week was replacing the
> old md5 cacert intermediate with the up-to-date one.
> 
> Thanks, Peter
> 



-- 
Viele Grüße,
Torsten Reichard

mail: t.reichard at ab-storm.de
mobile: 0172 9469964
phone: 0221 2900250