I just had FiOS installed so I'm using a new router and the problem may be with that, but I was wondering if anyone else noticed this issue with their router. If not, then I know it's just my new Verizon supplied router, but if others are noticing it, maybe we need to open a bug for it.

Version ?

2.2 will make sure the ports are released, but it won't wait forever.

George wrote:Version ?

2.2 will make sure the ports are released, but it won't wait forever.

yeah I'm using 2.2, may just be the router has a problem then.

Do you now how to use wireshark (aka ethereal) ?

George wrote:Do you now how to use wireshark (aka ethereal) ?

never used it before, but I can give it a shot

Start up KT with no torrents running, then start a trace with ethereal, exit KT, wait 5 seconds and stop the trace.

In the trace you should see a http connection being setup to your router. It should have some SOAP in it (which is just XML, should contain a tag with RemovePortMapping)

If everything goes well, the router should answer back with a 200 OK.

George wrote:Start up KT with no torrents running, then start a trace with ethereal, exit KT, wait 5 seconds and stop the trace.

In the trace you should see a http connection being setup to your router. It should have some SOAP in it (which is just XML, should contain a tag with RemovePortMapping)

If everything goes well, the router should answer back with a 200 OK.

When doing this I do not see an HTTP connection on close. To verify that I was looking at the correct items I started wireshark before ktorrent and saw the UPnP connection to forward the ports (as TCP PSH,ACK packets), but upon closing I saw no response at all for UPnP. I used this filter to see the data "(data contains PortMapping || http) && (ip.src == gatewayIP || ip.dst == gatewayIP)"

It seems you are right, there was a small bug which prevented the UPnP plugin from starting the remove port mapping job when KT was shutdown.

George wrote:It seems you are right, there was a small bug which prevented the UPnP plugin from starting the remove port mapping job when KT was shutdown.

Glad I could help

Just updated to 2.2.2 and it seems that a similar problem happens again.

* The TCP packets that request the port mapping seem to have bad check sums
* When closing ktorrent, it seems to request a delete port mapping, but I never see a response from the router. and the port mapping remains open. This TCP packet also contains a bad checksum.

johnjaylward wrote:Just updated to 2.2.2 and it seems that a similar problem happens again.

* The TCP packets that request the port mapping seem to have bad check sums
* When closing ktorrent, it seems to request a delete port mapping, but I never see a response from the router. and the port mapping remains open. This TCP packet also contains a bad checksum.

The kernel generates the TCP checksums, so there is not much we can do about this.