[Pidgin] #9830: pidgin registers the wrong IP in UPnP router when client is multihomed

[Pidgin]

#9830: pidgin registers the wrong IP in UPnP router when client is multihomed
------------------+---------------------------------------------------------
Reporter:  lpm    |        Type:  defect   
  Status:  new    |   Component:  libpurple
 Version:  2.5.8  |    Keywords:  UPnP     
------------------+---------------------------------------------------------
 When configuring port forwardings, Pidgin 2.5.8 may register the wrong
 Local IP in the UPnP router if the PC on which pidgin is running has
 multiple interfaces. Pidgin registers the IP of the first interface,
 instead of the IP that is used to communicate with the router to the local
 LAN.

 Example: let's assume a PC has two interfaces: one IEEE 1394 network with
 an autoconfigured IP address (10.4.0.1), and an ethernet (192.168.1.2)
 connected to the local LAN, where the UPnP router (192.168.1.1) is
 located. Pidgin will successfully configure UPnP forwarding on the router,
 but on the wrong address (10.4.0.1). Generally speaking, Pidgin will use
 the address of the first interface, regardless of whether or not it's the
 right interface.

 Workaround: disable all IP interfaces on the PC where pidgin is running -
 except the local LAN.

 Suggested fix: pidgin should use the local IP of the interface that is
 used to communicate with the UPnP router.

-- 
Ticket URL: <http://developer.pidgin.im/ticket/9830>
Pidgin <http://pidgin.im>
Pidgin