[Operators] Strange s2s issue regarding my server and jabber.org (M-Link issue?)

[Marco Cirillo]

Just figured I would let you know,





---> establish outgoing stream to jabber.org
    ---> perform STARTTLS and re-negotiate

    ---> fallback using dialback mechanism
<--- incoming stream from jabber.org
   <--- perform STARTTLS and re-negotiate
   <--- attempt SASL External with successful result
   <--- conclude dialback verification process
   <--- send <stream:stream />

<--- new incoming stream from jabber.org
   <--- perform STARTTLS and re-negotiate
   <--- attempt SASL External with successful result
   <--- deliver ping response...

... almost 2 minutes laters.


Thanks,
Marco.

I'm experiencing very slow s2s communication establishments torward jabber.org, it doesn't seem due to latency or other congestion factors. The flow seems the following by closing s2s connection from/to jabber.org and then sending a ping: ---> attempt SASL External which fails (and on that matter, I'd like to know why) ---> now that the outgoing s2s is authenticated, server sends queued IQ stanza via the outgoing stream More then the, "slightly weird" at least from my point of view, behaviour of M-Link. Have any insight why the first SASL External fails?

smime.p7s
Description: Firma crittografica S/MIME