[Pidgin] #14390: Title: Pidgin (2.9.0) Windows - incorrectly detects IP address when multiple network adapters are detected, causing file transfer to fail.
Pidgin
trac at pidgin.im
Fri Jul 8 05:42:44 EDT 2011
#14390: Title: Pidgin (2.9.0) Windows - incorrectly detects IP address when
multiple network adapters are detected, causing file transfer to fail.
----------------------+-----------------------------------------------------
Reporter: jonathan | Owner: MarkDoliner
Type: defect | Status: new
Component: AIM | Version: 2.9.0
Keywords: |
----------------------+-----------------------------------------------------
Pidgin is used in LAN, server is on the same subnet (192.168.9.x), however
Pidgin auto detect seems to radomly detect and use all installed network
adapters addresses, including invalid ones like 169.254.65.* and 0.0.0.0.
Worst, manual IP setting does not seem to make any difference.
This bad detection causes XMPP file transfer to often fail, transfer
slowly starts or receving side crashes, even with configured IP and a file
proxy. Here is the file transfer request generated by pidgin:
<iq from='jonathan at server-pc/924824306131037034820002' to='niki at server-
pc/3663187984131042080451492' type='set' id='purpled4e8a704'>
<query xmlns='http://jabber.org/protocol/bytestreams'
sid='purpled4e8a703'>
<streamhost jid='jonathan at server-pc/924824306131037034820002'
host='192.168.116.1' port='53379'/>
<streamhost jid='jonathan at server-pc/924824306131037034820002'
host='192.168.56.1' port='53379'/>
<streamhost jid='jonathan at server-pc/924824306131037034820002'
host='169.254.65.217' port='53379'/>
<streamhost jid='jonathan at server-pc/924824306131037034820002'
host='192.168.9.58' port='53379'/>
<streamhost jid='jonathan at server-pc/924824306131037034820002'
host='0.0.0.0' port='53379'/>
<streamhost jid='jonathan at server-pc/924824306131037034820002'
host='0.0.0.0' port='53379'/>
<streamhost jid='jonathan at server-pc/924824306131037034820002'
host='127.0.0.1' port='53379'/>
<streamhost jid='proxy.server-pc' host='192.168.9.128'
port='7777'/>
</query>
</iq>
The server and file proxy is 192.168.9.128, actual sender IP is
192.168.9.58, the hardcoded IP in prefs is 127.0.0.1. Receiving Pidgin
will try all IPs in a row, time out on every, or just crash.
Why the hardcoded IP is not used first, and then the file proxy?
--
Ticket URL: <http://developer.pidgin.im/ticket/14390>
Pidgin <http://pidgin.im>
Pidgin
More information about the Tracker
mailing list