[Dxspider-support] FW: Telnet Sessions locking up

[Mike Lewis]

I looked at my iptables entries, nothing looking like any problem there.
I then got Wireshark installed on my windoze computer, and captured my
Putty session with my cluster. The cluster system is at local address
192.168.0.200, and the connecting client system is at 192.168.0.207. The
system connects ok, and works for a while, but eventually goes dormant,
apparently coinciding with an ARP request from the cluster that appears
to be properly responded to by the client. I can send the complete
Wireshark capture file if anyone thinks it would be helpful. The last
few lines I include below, showing a DX spot received, and then ~100
seconds later, 2 ARP requests initiated by the cluster, that were
replied to. After that, typing on the Putty session does not appear to
go out at all. Eventually Putty realizes the session is dead.
 
No.     Time        Source                Destination           Protocol
Info
    104 531.095234  192.168.0.200         192.168.0.207         TCP
8000 > 1075 [PSH, ACK] Seq=1809 Ack=59 Win=5840 Len=79
 
Frame 104 (133 bytes on wire, 133 bytes captured)
Ethernet II, Src: LannerEl_00:34:7f (00:90:0b:00:34:7f), Dst:
3Com_4a:61:7f (00:04:76:4a:61:7f)
Internet Protocol, Src: 192.168.0.200 (192.168.0.200), Dst:
192.168.0.207 (192.168.0.207)
Transmission Control Protocol, Src Port: 8000 (8000), Dst Port: 1075
(1075), Seq: 1809, Ack: 59, Len: 79
Data (79 bytes)
 
0000  44 58 20 64 65 20 41 44 35 56 4a 3a 20 20 20 20   DX de AD5VJ:    
0010  20 20 37 30 31 34 2e 34 20 20 36 48 31 4c 20 20     7014.4  6H1L  
0020  20 20 20 20 20 20 20 43 57 20 20 20 20 20 20 20          CW       
0030  20 20 20 20 20 20 20 20 20 20 20 20 20 20 20 20                   
0040  20 20 20 20 20 20 30 35 34 30 5a 07 07 0d 0a            0540Z....
 
No.     Time        Source                Destination           Protocol
Info
    105 531.245876  192.168.0.207         192.168.0.200         TCP
1075 > 8000 [ACK] Seq=59 Ack=1888 Win=65018 Len=0
 
Frame 105 (54 bytes on wire, 54 bytes captured)
Ethernet II, Src: 3Com_4a:61:7f (00:04:76:4a:61:7f), Dst:
LannerEl_00:34:7f (00:90:0b:00:34:7f)
Internet Protocol, Src: 192.168.0.207 (192.168.0.207), Dst:
192.168.0.200 (192.168.0.200)
Transmission Control Protocol, Src Port: 1075 (1075), Dst Port: 8000
(8000), Seq: 59, Ack: 1888, Len: 0
 
No.     Time        Source                Destination           Protocol
Info
    106 775.834244  LannerEl_00:34:7f     3Com_4a:61:7f         ARP
Who has 192.168.0.207?  Tell 192.168.0.200
 
Frame 106 (60 bytes on wire, 60 bytes captured)
Ethernet II, Src: LannerEl_00:34:7f (00:90:0b:00:34:7f), Dst:
3Com_4a:61:7f (00:04:76:4a:61:7f)
Address Resolution Protocol (request)
 
No.     Time        Source                Destination           Protocol
Info
    107 775.834282  3Com_4a:61:7f         LannerEl_00:34:7f     ARP
192.168.0.207 is at 00:04:76:4a:61:7f
 
Frame 107 (42 bytes on wire, 42 bytes captured)
Ethernet II, Src: 3Com_4a:61:7f (00:04:76:4a:61:7f), Dst:
LannerEl_00:34:7f (00:90:0b:00:34:7f)
Address Resolution Protocol (reply)
 
No.     Time        Source                Destination           Protocol
Info
    108 885.463257  LannerEl_00:34:7f     3Com_4a:61:7f         ARP
Who has 192.168.0.207?  Tell 192.168.0.200
 
Frame 108 (60 bytes on wire, 60 bytes captured)
Ethernet II, Src: LannerEl_00:34:7f (00:90:0b:00:34:7f), Dst:
3Com_4a:61:7f (00:04:76:4a:61:7f)
Address Resolution Protocol (request)
 
No.     Time        Source                Destination           Protocol
Info
    109 885.463292  3Com_4a:61:7f         LannerEl_00:34:7f     ARP
192.168.0.207 is at 00:04:76:4a:61:7f
 
Frame 109 (42 bytes on wire, 42 bytes captured)
Ethernet II, Src: 3Com_4a:61:7f (00:04:76:4a:61:7f), Dst:
LannerEl_00:34:7f (00:90:0b:00:34:7f)
Address Resolution Protocol (reply)
 
Any ideas what the problem is?
 
ML
 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mailman.tobit.co.uk/pipermail/dxspider-support/attachments/20070130/100644c1/attachment.htm