[Pidgin] #12643: Pidgin/Bonjour doesn't send Instant Message to another Pidgin/Bonjour client, both running on Windows

[Pidgin]

#12643: Pidgin/Bonjour doesn't send Instant Message to  another Pidgin/Bonjour
client, both running on Windows
-----------------------------------------------------+----------------------
 Reporter:  v.plessky                                |        Owner:  datallah
     Type:  defect                                   |       Status:  pending 
Milestone:                                           |    Component:  Bonjour 
  Version:  2.7.3                                    |   Resolution:          
 Keywords:  Bonjour Windows firewall proxy presence  |  
-----------------------------------------------------+----------------------
Changes (by datallah):

  * status:  new => pending


Comment:

 Replying to [comment:21 v.plessky]:
 >
 >
 > Tested Kopete running on Linux, machine connected via Wireless
 connection.
 >
 > See Log file - Pidgin/Windows - talking to Kopete/Linux (wireless
 machine)
 >
 >
 > {{{
 > (19:11:48) bonjour: Starting conversation with kopete at linux-msi-s271
 > (19:11:48) dnsquery: Performing DNS lookup for 192.168.1.51
 > (19:11:48) sound: Playing C:\Program Files\Pidgin\sounds\purple\send.wav
 > (19:11:48) dnsquery: IP resolved for 192.168.1.51
 > (19:11:48) proxy: Attempting connection to 192.168.1.51
 > (19:11:48) proxy: Connecting to 192.168.1.51:5298 with no proxy
 > (19:11:48) proxy: Connection in progress
 > (19:11:48) proxy: Connecting to 192.168.1.51:5298.
 > (19:11:48) proxy: Connected to 192.168.1.51:5298.
 > (19:11:48) bonjour: Receive: -<?xml version='1.0' encoding='UTF-8' ?>
 > <stream:stream xmlns='jabber:client'
 xmlns:stream='http://etherx.jabber.org/streams' from='kopete at linux-
 msi-s271' to='vadim at ASUS-M51TA'>- 176 bytes
 > (19:12:31) prefs: /pidgin/conversations/im/x changed, scheduling save.
 >
 > }}}
 >
 > As you  see, problem is not related to network.
 > Kopete connects to Pidgin, and has 192.168.1.51 IP address (correct)

 Sorry, but that isn't really relevant and doesn't indicate that it isn't
 related to the network.

 This is a connection '''from''' Pidgin '''to''' Kopete.  I'm guessing that
 Kopete doesn't validate that the originating IP address for the connection
 is the expected IP of the user that claims to be connecting and that is
 why it is working.

 If you send the initial message from Kopete to Pidgin, you'll see the same
 problem because the IP address the connection is coming from is wrong.

 > BUT: Message from one client to another not displayed.
 > It seems it's kind of format mismatch.
 > Hope you will understand better from the log.
 >
 > Therefor, we need to debug network part of Pidgin code, to understand
 why it doesn't work in Wireless connection.

 Sorry, but there is nothing to debug within the Pidgin code.  It is just
 the standard `accept()` function to accept an incoming connection and the
 OS provides information about where the incoming connection.

 As I mentioned in the last message, you'll need to use Wireshark or
 something to capture the network traffic, but really you need to look at
 the router for answers.


 > ***
 > I also added one more test user  - 'acer' (on wired computer)
 > When I was trying to select it and do some action, Pidgin crashed.
 >
 >
 > {{{
 > (19:15:11) bonjour: Removed last presence for buddy 'acer at linux-
 acer6935'; signing off buddy.
 > (19:15:11) g_log: purple_find_prpl: assertion `id != NULL' failed
 > (19:15:11) g_log: purple_find_prpl: assertion `id != NULL' failed
 >
 > }}}

 >
 > Can you pls also look at this problem, or I need to file another bug
 report?

 Without a crash report, there isn't anything that I can do with this.

-- 
Ticket URL: <http://developer.pidgin.im/ticket/12643#comment:22>
Pidgin <http://pidgin.im>
Pidgin