[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:  new     
Milestone:                                           |    Component:  Bonjour 
  Version:  2.7.3                                    |   Resolution:          
 Keywords:  Bonjour Windows firewall proxy presence  |  
-----------------------------------------------------+----------------------

Comment(by datallah):

 Replying to [comment:23 v.plessky]:
 >
 > RE:
 > ''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.
 > ''
 >
 > It is message coming from Kopete to Pidgin.
 > See word "Receive:" in Log
 >
 > {{{
 > (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
 >
 > }}}

 Yes, Pidgin is '''Recieving''' that message from Kopete, but it is
 receiving it on a connection that was initially made from Pidgin to Kopete
 - that is where the issue is.  Once the connection is made, both side can
 use it to send data.

 Notice that immediately before that in the Pidgin log, it is Pidgin that
 is connecting to the remote instance - as soon as the connection is
 accepted by the remote Kopete instance (and apparently Kopete doesn't
 validate the origin of the connection), Kopete is sending that "<?xml
 version='1.0'...".

 As I said before, if the '''initial''' connection had been made '''from'''
 Kopete '''to''' Pidgin (assuming the same wireless network configuration),
 the same problem would happen - it would look like it was coming from the
 wrong IP.  I don't know what I can do to make that more clear.


 > It seems you misunderstood what I am trying to say.
 > Pidgin - using Bonjour - should not know about existence of 192.168.1.2
 address.
 > Instead, it talks to it and making some configs/guesses using it.

 You're misunderstanding what is going on.

 That stuff in the log about connecting to 192.168.1.2 is completely
 unrelated to Bonjour!
 The Bonjour part of Pidgin doesn't know anything about 192.168.1.2  - it
 is the overall Pidgin initialization that discovers the UPnP service
 available on 192.168.1.2.

 As I mentioned, if you disable the network settings related to UPnP, you
 wont see those entries in the log.

 > Re:
 > ''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.
 > ''
 >
 > Please, before making such suggestions understand how Layer2 network
 works.
 > Host can talk to each other inside 192.168.1.x/24 subnet. Routing is not
 involved.
 > Therefor, word "router" is not applicable to this scenario or this bug.
 > If "Access Point" makes things better to understand, let's use it.
 >
 > Access Point - as it installed and configured - forward traffic to
 host(s) in 192.168.1.x subnet, and back.
 >
 > May be, you can install Access Point (Wirelss "router" working as AP)
 and test connection between one Wired and one Wireless client?
 > Problem - as it was initially reported - is "End User" problem.
 > I guess there are some users of Pidgin using it on Windows.
 > Wi-Fi became very popular. People would try Pidgin - and just say "it
 doesn't work"
 > And make conclusion "all that open-source doesn't work"
 > I guess we want to avoid it, isn't it?

 You're right - "router" isn't the right word, sorry I used the wrong
 confusing word.  I meant "Wireless Access Point" when I said "router".
 I'm familiar with how routing works :)

 I think you're making the wrong assumption that this occurs with all
 wireless networks, but that simply isn't the case.  It is something very
 specific that is wrong with your network that is causing the problem.

 This isn't a problem that has been reported before.  I use Bonjour in
 Pidgin on my mixed wired/wireless network at home and at work frequently
 and so do many other users.

 What exactly do you mean when you say "Access Point - as it installed and
 configured - forward traffic to host(s) in 192.168.1.x subnet, and back."
 - that makes it sound like your access point is configured to do some sort
 of network bridging or something?

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