[jdev] Connectivity issues with gmail.com and googlemail.com
Hi!
Last few weeks I'm experiencing a loss of connectivity with gmail.com
and googlemail.com. It's interesting that my messages (from nes.ru to
gmail.com) rich recipients just fine, but messages from gmail.com
can't be delivered (users get error messages).
After switching off STARTTLS over S2S (which hides the problem) I got
the following ejabberd log (it's a typical scenario):
1) Google server connects to nes.ru:
=INFO REPORT 2007-09-19 20:35:31 ===
I(0.241.0:ejabberd_listener:90): (#Port0.6781) Accepted connection
{{72,14,252,129},30195} - {{212,119,199,80},5269}
(Note #Port0.6781. It's an Erlang port, which processes the TCP connection.)
2) ejabberd opens an incoming S2S stream:
=INFO REPORT 2007-09-19 20:35:31 ===
I(0.5062.0:ejabberd_s2s_in:105): started: {gen_tcp,#Port0.6781}
Now the stream is controlled by Erlang process 0.5062.0.
3) gmail.com sends a key
=INFO REPORT 2007-09-19 20:35:32 ===
I(0.5062.0:ejabberd_s2s_in:317): GET KEY: {nes.ru,
gmail.com,
[],
CAESBxC07cjz0SIaEEWGpREmNkivSJRYciOVI70=}
Note port number 0.5062.0.
4) nes.ru opens outgoing S2S stream to verify the key (it's irrelevant here)
5) googlemail.com sends a key over the same TCP connection (!):
=INFO REPORT 2007-09-19 20:35:32 ===
I(0.5062.0:ejabberd_s2s_in:317): GET KEY: {nes.ru,
googlemail.com,
[],
CAESBxC17cjz0SIaEBnkylXoIZMlEI4Y4qYXHDQ=}
The port is the same 0.5062.0. After that the connection is stalled.
ejabberd never receives anything in this stream.
For me it looks like a severe bug in Google Talk server.
Did someone experienced similar problems with gmail.com and
googlemail.com? May be Google Talk admins read this list and can help?
Cheers!
--
Sergei Golovan
Re: [jdev] Connectivity issues with gmail.com and googlemail.com
Hi Sergei,
5) googlemail.com sends a key over the same TCP connection (!):
That's called piggybacking.
=INFO REPORT 2007-09-19 20:35:32 ===
I(0.5062.0:ejabberd_s2s_in:317): GET KEY: {nes.ru,
googlemail.com,
[],
CAESBxC17cjz0SIaEBnkylXoIZMlEI4Y4qYXHDQ=}
The port is the same 0.5062.0. After that the connection is stalled.
ejabberd never receives anything in this stream.
For me it looks like a severe bug in Google Talk server.
They've been doing that ever since s2s was enabled.
Did someone experienced similar problems with gmail.com and
googlemail.com? May be Google Talk admins read this list and can help?
Cheers!
Happy ejabberd debugging. Dialback is already horrible to debug, but
piggybacking makes it a real nightmare.
Philipp
Re: [jdev] Connectivity issues with gmail.com and googlemail.com
On 9/19/07, Philipp Hancke [EMAIL PROTECTED] wrote: Hi Sergei, 5) googlemail.com sends a key over the same TCP connection (!): That's called piggybacking. Then things become more complicated, and I don't know where the bug is. Ejabberd verifies both keys, sends dialback answers, and after 10 minutes of silence closes the socket. -- Sergei Golovan
Re: [jdev] Connectivity issues with gmail.com and googlemail.com
On 9/19/07, Sergei Golovan [EMAIL PROTECTED] wrote: On 9/19/07, Philipp Hancke [EMAIL PROTECTED] wrote: Hi Sergei, 5) googlemail.com sends a key over the same TCP connection (!): That's called piggybacking. Then things become more complicated, and I don't know where the bug is. Ejabberd verifies both keys, sends dialback answers, and after 10 minutes of silence closes the socket. Moreover, when I removed the only contact with JID [EMAIL PROTECTED] the situation remains the same. gmail.com opens the stream, and after the dialback is verified no more data comes through the socket. After ten minutes the socket is closed. It's very strange given that other ejabberd deployment don't have problems with Google Talk S2S. Cheers! -- Sergei Golovan
Re: [jdev] Connectivity issues with gmail.com and googlemail.com
Hello, Sergei! Wed, 19 Sep 2007 23:19:58 +0400 you wrote: SG It's very strange given that other ejabberd deployment don't have SG problems with Google Talk S2S. You aren't the only one who has problems with Google :) my ejabberd 1.1.4 also fails when Google tries to add someone from my domain to its roster. -- WMBR, George Hazan ([EMAIL PROTECTED])
Re: [jdev] Connectivity issues with gmail.com and googlemail.com
2007/9/19, Sergei Golovan [EMAIL PROTECTED]: On 9/19/07, Sergei Golovan [EMAIL PROTECTED] wrote: On 9/19/07, Philipp Hancke [EMAIL PROTECTED] wrote: Hi Sergei, 5) googlemail.com sends a key over the same TCP connection (!): That's called piggybacking. Then things become more complicated, and I don't know where the bug is. Ejabberd verifies both keys, sends dialback answers, and after 10 minutes of silence closes the socket. Moreover, when I removed the only contact with JID [EMAIL PROTECTED] the situation remains the same. gmail.com opens the stream, and after the dialback is verified no more data comes through the socket. After ten minutes the socket is closed. It's very strange given that other ejabberd deployment don't have problems with Google Talk S2S. It's probably not related to this, but Mats lately also found some bugs in the Google Talk server (but on the client side): http://coccinella.im/node/93 -- Mvg, Sander Devrieze.
Re: [jdev] Connectivity issues with gmail.com and googlemail.com
On Sep 19, 2007, at 21:41, George Hazan wrote: Hello, Sergei! Wed, 19 Sep 2007 23:19:58 +0400 you wrote: SG It's very strange given that other ejabberd deployment don't have SG problems with Google Talk S2S. You aren't the only one who has problems with Google :) my ejabberd 1.1.4 also fails when Google tries to add someone from my domain to its roster. On my ejabberd server, connections to @gmail.com work fine, but connections from Google for domains fail, maybe this is the reason. andy
