--On Tuesday, April 19, 2005 05:22:13 PM +0900 "JINMEI Tatuya /
=?ISO-2022-JP?B?GyRCP0BMQEMjOkgbKEI=?=" <[EMAIL PROTECTED]>
wrote:

>>>>>> On Mon, 11 Apr 2005 17:36:33 +0200, 
>>>>>> Peter Bieringer <[EMAIL PROTECTED]> said:
> 
>>> has anyone seen this? I have such problems since long time and don't
>>> know the reason. Today, I debugged a little bit and it's very strange:
>>> 
>>> one side: Fedora Core 3 running 2.6.10-1.770_FC3 openssh-3.9p1-8.0.1
>>> other side: Fedora Core 2 running 2.6.10-1.771_FC3 and
>>> openssh-3.6.1p2-34
>>> 
>>> Connection: FC2 (client) to FC3 (server)
>>> 
>>> Login is working, editing a file with vi, suddenly I do no longer get
>>> any reponse from typed chars.
> 
> (snip)
> 
>> The only equal thing is that the boxes are located in the same data
>> center  having the same IPv6 connectivity.
> 
>> Has noone ever seen such?
> 
> One typical reason for this type of problems is because PMTU discovery
> does not work due to a buggy/mis-configured router/firewall which
> drops ICMPv6 packet too big messages.  You may want to check whether
> this is the case or not in your environment.

As an intermediate result, the reason is that *one* TCP packet inbetween
sent by ssh server does not reach the client, also not on TCP
retransmission (!) (detected by comparing tcpdumps on server and client).
Other packets except the lost one are sent from server to client
afterwards. Happen more or less reproducable on 4 servers (and 3 different
Linux kernels) behind the same IPv6 connectivity.

That's very strange and I'm currently working on investigation of this
issue in front of the servers (try to get some port mirroring to see where
the packet is really got lost...).

        Peter
-- 
Dr. Peter Bieringer                     http://www.bieringer.de/pb/
GPG/PGP Key 0x958F422D               mailto: pb at bieringer dot de 
Deep Space 6 Co-Founder and Core Member  http://www.deepspace6.net/
---------------------------------------------------------------------
The IPv6 Users Mailing List
Unsubscribe by sending "unsubscribe users" to [EMAIL PROTECTED]

Reply via email to