[Pidgin] #11707: Pidgin does not close TCP ports on router when file transfer is failed
Pidgin
trac at pidgin.im
Thu Jul 1 10:33:16 EDT 2010
#11707: Pidgin does not close TCP ports on router when file transfer is failed
------------------------------+---------------------------------------------
Reporter: andrey_skvortsov | Owner: malu
Type: defect | Status: new
Milestone: | Component: XMPP
Version: 2.6.6 | Resolution:
Keywords: |
------------------------------+---------------------------------------------
Comment(by malu):
Replying to [ticket:11707 andrey_skvortsov]:
> My PC is behind router, that supports UPnP. UPnP is enabled in Pidgin.
In that way, I can use out-of-band transfers in XMPP for file transfers.
Usually Pidgin opens TCP port, sends file to client and afterwards closes
port.
> But if I send file via XMPP and transmission fails for some reason,
Pidgin does not close openned before TCP port. The port stays open for
ever.
> But the port should be closed after transmission independently of
result.
Do you have the opportunaty to recompile the code?
If so, could you try adding the following at line 811 in
libpurple/protocols/jabber.c (before the call to "close"):
purple_network_remove_port_mapping(jsx->local_streamhost_fd);
Unfortunatly, I don't have an opportunity to test this (as I don't have
access to a router with UPnP any longer).
Thanks in advance!
//Marcus
--
Ticket URL: <http://developer.pidgin.im/ticket/11707#comment:6>
Pidgin <http://pidgin.im>
Pidgin
More information about the Tracker
mailing list