S2S doesn't work (dialback broken)

Description

Many users report that S2S isn't working for them anymore after the upgrade to 3.7.0.

"After further testing, I've found that 3.7.0 will no successfully negotiate dialback connections with other systems also running 3.7.0. These connections also log an error like:

2011.03.04 15:45:53 ServerDialback: OS - Unexpected answer in validation from: ee.washington.edu id: 5b589264 for domain: dragonsdawn.net answer:<stream:features xmlns:stream="http://etherx.jabber.org/streams"><starttls xmlns="urn:ietf:params:xml:ns:xmpp-tls"/><dialback xmlns="urn:xmpp:features:dialback"/><mechanisms xmlns="urn:ietf:params:xml:ns:xmpp-sasl"/></stream:features>"

also http://community.igniterealtime.org/message/210452#210452

Environment

None

Activity

Show:
Neustradamus
November 1, 2013, 1:34 PM
Guus der Kinderen
January 1, 2012, 12:58 PM

I've committed Marcins patch to improve communication with domains using pre 1.0-versioned stream headers.

Lets use a different issue than this one () for new issues with S2S - this one is getting out of hand.

Marcin Marcin
December 17, 2011, 3:32 PM

Update: jabber.wp.pl s2s works today without any problems (probably something on their said, as suddenly s2s connections from my non-Openfire accounts started working.

Marcin Marcin
December 17, 2011, 1:05 AM

I have quickly checked breaking session - amessage.de fails on TLS/SSL negotiation

The other one (jabber.wp.pl) stops at some point, it's not related to the version header I guess:
Fetching vCard works fine with that server.

Openfire to WP:

WP to Openfire:

Openfire to WP:

WP to Openfire:

Openfire to WP:

Marcin Marcin
December 16, 2011, 11:58 PM

With the ancient server in question it works - it does not like version="1.0" only in responses to its own greeting.

I run openfire trunk for myself for my daily use and I keep s2s connections to:

jabber.org
igniterealtime.org
gmail.com
the one making trouble - non public
another non public making sometimes trouble with s2s
7thguard.net
chrome.pl

but I have added two s2s contacts for my accounts at

amessage.de
jabber.wp.pl

and yes, it seems it does not get through. Not sure how the last one works with s2s. Amessage is occasionally making s2s trouble with some servers.

I have no access to any older Openfire instance right now.

Fixed

Assignee

Guus der Kinderen

Reporter

wroot

Ignite Forum URL