Alanaktion / transmisson-remote-gui

Automatically exported from code.google.com/p/transmisson-remote-gui
GNU General Public License v2.0
1 stars 0 forks source link

Transmission client is not able to connect from the first time #333

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago
The issue was already submitted by me previously on version 1.4.3 or similar, 
but was quite rare before. Now after moving on version 2.1.1 the client is not 
able to connect much more often. At the same time the web-client is always able 
to connect and show the list of downloads.

When connection fails, I'm trying to re-connect (Torrect -> Connect), and in 
most of the cases that try fails. Even when it is connected, it is still 
periodically disconnected by some reason, even if the traffic in my network is 
very low. Possibly the problem is caused by slighly higher delays in 
communication between laptop and box with transmission (WiFi is used on a 
laptop).

To simlify analysis, I'm attaching collected and filtered Wireshark .pcap 
files. 192.168.1.5 is the host with GUI, 192.168.1.6 (port 9091) is the server. 
Files are collected both for the case when connection is successful (couple of 
times, just in case) and when it is not. In case of failed conection it seems 
that there is no some frame from server to client. But when it is sent (in 
successful case), it looks like it contain strange HTTP response code (409), 
though it is connected successfully right after that. Hope that helps.

What steps will reproduce the problem?
1. Start Transmission Remote GUI
2. If it is not able to connect, do "Torrent -> Connect"

What is the expected output? What do you see instead?
Connection from the first time, as well as reconnection.

What version of the product are you using? On what operating system?
Windows Vista (32-bit) with GUI ver. 2.1.1. Transmission server ver. 1.91 
(10269)

Please provide any additional information below.
See attached 'testcases.zip' with captures from Wireshark (in .pcap format) for 
tried test cases (both successful and not).
More information on configuration and testcases could be found in attached 
'details.txt'
Filter used in Wireshark could be seen in attached 'transmission-ws-filter.txt' 
file (not needed, but just in case, since .pcap are already filtered).

Original issue reported on code.google.com by Oleg.Kli...@gmail.com on 22 Oct 2010 at 6:14

Attachments:

GoogleCodeExporter commented 9 years ago
Nobody else have such problem. Probably it is only specific to your environment.

Original comment by j...@cp-lab.com on 20 Feb 2011 at 2:16