'Strange KDE networking problem - session termination'

[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-devel
Subject:    Strange KDE networking problem - session termination
From:       Lukasz Jakubowski <lukaszj () s3group ! com ! pl>
Date:       2002-07-12 10:55:42
[Download RAW message or body]

<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
  <title></title>
</head>
<body>

<div class="moz-text-flowed"
 style="font-family: -moz-fixed; font-size: 13px;" lang="x-central-euro">Hello! 
<br>
 <br>
Problem: <br>
X session is terminated after 2 hours+a few minutes for no apparent  reason.
Both idle and active (user does something and then all of a  sudden all windows
disappear). <br>
 <br>
Environment: <br>
ReflectionX 8 PC-Win X server, KDE clients on Linux 6.2 and 7.2,  firewall
inbetween. <br>
 <br>
Observations: <br>
- Problem applies both to session started with xsession and via XDMCP. <br>
- Problem is <span class="moz-txt-underscore"><span class="moz-txt-tag">_</span>not<span
 class="moz-txt-tag">_</span></span> valid when firewall does not come into
play, so  neither X server nor X client have any timeout limit. Firewall
_idle_ session timeout limit is set to 1 hour.<br>
- Problem is <span class="moz-txt-underscore"><span class="moz-txt-tag">_</span>not<span
 class="moz-txt-tag">_</span></span> valid for fe. telnet sessions (so the
problem does  not lay in TCP/IP stacks) <br>
- Problem is also _not_ valid for non-KDE X sessions (f.e. xclock run from
telnet session)<br>
- Session is closed by client (proper FIN+ACK) after 10 mysterious (at  least
for me) ACK or RST+ACK (?) packets from client machine in last 10 minutes
 before session termination (1 per minute). These are dropped by firewall
as packets of  an unknown established connection, which is true. <br>
 <br>
I think the problem may be somewhere in KDE client-server  communications.
If you know any better place for this problem please let  me know. <br>
 <br>
Below is example (last) mysterious packet. Right after it, client  started
closing TCP connection. <br>
 <br>
Regards, <br>
Lukasz <br>
 <br>
IP:   ----- IP Header ----- <br>
IP: <br>
IP:   Version = 4 <br>
IP:   Header length = 20 bytes <br>
IP:   Type of service = 0x00 <br>
IP:         xxx. .... = 0 (precedence) <br>
IP:         ...0 .... = normal delay <br>
IP:         .... 0... = normal throughput <br>
IP:         .... .0.. = normal reliability <br>
IP:   Total length = 40 bytes <br>
IP:   Identification = 5924 <br>
IP:   Flags = 0x4 <br>
IP:         .1.. .... = do not fragment <br>
IP:         ..0. .... = last fragment <br>
IP:   Fragment offset = 0 bytes <br>
IP:   Time to live = 64 seconds/hops <br>
IP:   Protocol = 6 (TCP) <br>
IP:   Header checksum = f050 <br>
IP:   Source address = 192.168.89.130, 192.168.89.130 <br>
IP:   Destination address = 192.168.88.136, 192.168.88.136 <br>
IP:   No options <br>
IP: <br>
TCP:  ----- TCP Header ----- <br>
TCP: <br>
TCP:  Source port = 1110 <br>
TCP:  Destination port = 6000 (XWIN) <br>
TCP:  Sequence number = 860735638 <br>
TCP:  Acknowledgement number = 9846897 <br>
TCP:  Data offset = 20 bytes <br>
TCP:  Flags = 0x14 <br>
TCP:        ..0. .... = No urgent pointer <br>
TCP:        ...1 .... = Acknowledgement <br>
TCP:        .... 0... = No push <br>
TCP:        .... .1.. = Reset <br>
TCP:        .... ..0. = No Syn <br>
TCP:        .... ...0 = No Fin <br>
TCP:  Window = 8120 <br>
TCP:  Checksum = 0x040c <br>
TCP:  Urgent pointer = 0 <br>
TCP:  No options <br>
TCP: <br>
XWIN:  ----- XWIN:   ----- <br>
XWIN: <br>
XWIN:  "" <br>
XWIN: <br>
 <br>
</div>
</body>
</html>

>> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe <<
[prev in list] [next in list] [prev in thread] [next in thread] 