[Pidgin] #1522: UPnP timeout period is ridiculously long
Pidgin
trac at pidgin.im
Sun Jun 3 18:51:11 EDT 2007
#1522: UPnP timeout period is ridiculously long
----------------------------------------------+-----------------------------
Reporter: rgovostes | Type: defect
Status: new | Priority: minor
Component: libpurple | Version: 2.0.1
Keywords: upnp timeout file transfer oscar | Pending: 0
----------------------------------------------+-----------------------------
Over on Adium Trac, I've been whittling away at a bug I'm having with
outgoing file transfers on AIM ([http://trac.adiumx.com/ticket/7084
link]). When sending files, the other party wouldn't receive any
notification that I was trying to initiate a connection -- until I
accidentally left a file transfer running in the background, and twenty
minutes later the transfer completed.
Looking over
[http://trac.adiumx.com/attachment/ticket/7084/ItWorksBwahaha.txt the
debug log], I see that the UPnP AddPortMapping request is sent out at
16:26:51 and fails ten minutes later at 16:36:59. The DeletePortMapping
request is sent out at 16:36:59, and that fails at 16:47:07 (another ten
minutes). The transfer starts to work immediately after the second
timeout.
To be clear, UPnP is enabled on my router, but I wouldn't dismiss the
possibility that the router isn't functioning properly. The UPnP requests
ought to time out after just a few seconds (after all, thte NAT-PMP times
out in a quarter of a second).
Unrelatedly, it looks like the AddPortMapping is rightfully using TCP,
while DeletePortMapping is using UDP. This could cause unforeseen problems
elsewhere.
--
Ticket URL: <http://developer.pidgin.im/ticket/1522>
Pidgin <http://pidgin.im>
Pidgin
More information about the Tracker
mailing list