Add an s2s testing feature

Description

Add an s2s testing feature to the admin console. It would let you type in a domain name and test an s2s connection to it. If there were errors connecting, it would tell you. That would be very helpful for debugging server setup issues as well as firewalls, etc.

Environment

None

Activity

Show:

Daryl Herzmann November 13, 2017 at 8:04 PM

feedback was addressed, so marking as resolved.

Guus der Kinderen September 23, 2017 at 8:06 AM
Edited

Richard has been working on this feature. As it is merged, there are a couple of issues:

  • A ping is used to set-up a S2S connecting. A packet interceptor is used to catch the response. This packet interceptor intercepts all traffic, not just the response to the ping. This leads to weird results if other traffic flows between both domains.

  • When there's a pre-existing connection, that connection is terminated before the test occurs. I think some clients pick up on this, and immediately re-establish the connection.

  • The pre-existing session isn't really closed - it's only removed from the routing table.

  • I had to search all over the place for this new feature, in the admin console

Suggested improvements:

  • make sure that the packet listener only intercepts the IQ result of the ping, or, prevent other threads from starting a new s2s connection while the test is running.

  • actually close pre-existing sessions.

  • move the test tool to "sessions" > "tools"

Daryl Herzmann November 18, 2016 at 8:27 PM

Oh, how I long for this feature

Daryl Herzmann February 23, 2013 at 2:01 PM

Setting to Guus for his evaluation on the wish-list!

Guus der Kinderen February 6, 2013 at 7:57 PM

Removing the 'fix version' for all unresolved issues that were scheduled for version 7.8.2. We're releasing this version today - the remaining issues should be rescheduled later.

Fixed

Details

Assignee

Reporter

Components

Fix versions

Affects versions

Priority

Created August 30, 2005 at 6:22 AM
Updated November 13, 2017 at 8:04 PM
Resolved November 13, 2017 at 8:04 PM