[JDEV] s2s problems
Charles Forsythe
forsythe at netvoice.net
Tue Dec 12 23:36:12 CST 2000
I'm having a problem with server-to-server communication. I found a
similar problem reported in a JDEV email from last month, and the
response was:
> it means that your server failed to deliver a packet to
> 198.140.216.68 .. you probably need to add a s2s component into
> your server, or someother <host/> method of handling general
> packets not intended for any internal hostnames
This answer is confusing for two reasons:
1) I thought jabber servers were designed to
automagically relay messages to other jabber
servers.
2) Where are "s2s components" and "<host/>" methods
documented. Even if this advice is accurate,
can anyone explain to a relative newbie how to
follow it?
A little background on my config:
1. The server is at moe.netvoice.net (feel free to hit it if that would
help). Ports 5222 and 5269 are open to the public.
2. The servers I'm testing against are jabber.org and hotjabber.com.
jabber.org usually works great. hotjabber.com fails consitantly. When
I say "fails," I'm talking about out-going data. Incoming packets tend
to be fine.
3. I had problems with the release jabber 1.2 so I got the latest build
from CVS. That build seems more stable, but it still has the same
issues.
4. These error messages might be illuminating:
20001213T04:59:37: [notice] (hotjabber.com):
server connection timed out
20001213T04:59:37: [notice] (hotjabber.com):
bouncing a packet to redpen at hotjabber.com from
forsythe at moe.netvoice.net/home: (null)
20001213T04:59:37: [notice]
(jabber.org): server connection timed out
20001213T04:59:37: [notice] (jabber.org):
bouncing a packet to forsythe at jabber.org from
forsythe at moe.netvoice.net/home: (null)
Is this my config? Is this just heavily-loaded servers? If it's the
latter, shouldn't the s2s code respond to the situation a little more
gracefully? Finally, if hotjabber.com can consitantly get data *to* me,
shouldn't that connected be used by moe.netvoice.net's jabber server to
return data?
Thanks for any insight.
-- Charles
More information about the JDev
mailing list