Opened 6 years ago

Last modified 6 years ago

#12980 new defect

UPnP issues--same router, two systems, one works, other doesn.t

Reported by: MSong Owned by:
Milestone: Component: libpurple
Version: 2.7.5 Keywords:
Cc:

Description (last modified by MSong)

I'm having some difficulty getting UPnP to work with Pidgin (2.7.5, in this case, using the build from the Ubuntu Pidgin-Packagers PPA. But this has been the case for several years at least)

I have two systems--a 64bit Desktop system, and a 32bit Netbook, both of which are connected to a Linksys WRT54g router, running DD-Wrt V24 SP1. Both machines are capable of both wireless and wired connections, the results of which are the same no matter which machine uses which connection.

The odd thing is.. UPnP works fine on the 64 bit desktop--It can get the external IP and forward ports (as evidenced by DD-Wrt's UPnP screen). However, on the 32 bit Netbook, UPnP doesn't work at all

I've made a somewhat minimalist test case where they both attempt to get the external IP on pidgin startup

Attachments (4)

purple-debug.log (3.9 KB) - added by MSong 6 years ago.
Log from the Desktop (UPnP working)
purple-debug2.log (3.3 KB) - added by MSong 6 years ago.
Log from the Netbook (UPnP not working)
Netbook.wireshark (5.7 KB) - added by MSong 6 years ago.
Wireshark capture from the Netbook (UPnP not working)
Desktop.wireshark (8.6 KB) - added by MSong 6 years ago.
UPnP working on the desktop

Download all attachments as: .zip

Change History (11)

Changed 6 years ago by MSong

Log from the Desktop (UPnP working)

Changed 6 years ago by MSong

Log from the Netbook (UPnP not working)

comment:1 Changed 6 years ago by MSong

  • Description modified (diff)

comment:2 Changed 6 years ago by MSong

Additionally, the Deluge Bittorent Client's UPnP functionality works perfectly on both machines.

comment:3 Changed 6 years ago by deryni

  • Status changed from new to pending

It looks like the response being returned is different. Can you dump the actual traffic with something like Wireshark? (I thought there was a way to get pidgin to dump that to the debug log but I don't see it for the responses.)

Changed 6 years ago by MSong

Wireshark capture from the Netbook (UPnP not working)

comment:4 Changed 6 years ago by MSong

  • Status changed from pending to new

Attachment (Netbook.wireshark) added by ticket reporter.

comment:6 Changed 6 years ago by MSong

and in a very strange twist of events, having Wireshark *open*, not even recording, seems to make UPnP not work on the desktop. (With the same errors in the debug log as on the Netbook).

comment:7 Changed 6 years ago by deryni

  • Status changed from new to pending

Literally having wireshark open triggers that? Or having had wireshark listen once causes it to fail from that point on (even after wireshark is no longer listening)? You can repeatedly have it work, open wireshark and have it fail then close wireshark and have it work again?

Assuming I'm reading the capture and the pidgin UPnP code correctly I think that response looks like it should have worked. But it is late and this is the first I'm really ever looking at that code so a second opinion would be a good idea.

comment:8 Changed 6 years ago by MSong

  • Status changed from pending to new

It SEEMED to be following the pattern of open wireshark, open pidgin, upnp fails, close both, open pidgin, upnp works, close pidgin, open wireshark, open pidgin, upnp fails.

But at a little closer glance, it seems to be random whether upnp succeeds on the desktop.. repeatedly closing and opening shows about 2/3 to 3/4 success rate for UPnP. I went back and repeatedly closed and opened pidgin on the netbook to see if that was also the case there, and the netbook still fails reliably over about 20 repeats. Going to try getting a wireshark log of it actually working on the desktop.

Changed 6 years ago by MSong

UPnP working on the desktop

Note: See TracTickets for help on using tickets.
All information, including names and email addresses, entered onto this website or sent to mailing lists affiliated with this website will be public. Do not post confidential information, especially passwords!