[Pidgin] #12643: Pidgin/Bonjour doesn't send Instant Message to another Pidgin/Bonjour client, both running on Windows
Pidgin
trac at pidgin.im
Fri Sep 24 10:58:21 EDT 2010
#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 v.plessky):
Tried method you described. See log attached.
two comments on it
1) first two attempts "from 192.168.1.2" - coming from wireless computer
192.168.1.51
{{{
(18:39:53) bonjour: Received incoming connection from 192.168.1.2.
(18:39:53) bonjour: We don't like invisible buddies, this is not a
superheroes comic
(18:39:56) bonjour: Received incoming connection from 192.168.1.2.
(18:39:56) bonjour: We don't like invisible buddies, this is not a
superheroes comic
(18:40:10) bonjour: Received incoming connection from 192.168.1.139.
(18:40:10) bonjour: We don't like invisible buddies, this is not a
superheroes comic
}}}
Last attempt (also via telnet) from wired connection, computer
192.168.1.149
Pls also note that both computers are Linux machines.
Therefor problem is not specific to Windows.
And I doubt in this scenario that problem may be caused by Linux- (or
Windows-) networking configuration.
2) I have questions on this part of log
{{{
(18:39:31) dnsquery: Performing DNS lookup for 192.168.1.2
(18:39:31) dnsquery: IP resolved for 192.168.1.2
(18:39:31) proxy: Attempting connection to 192.168.1.2
(18:39:31) proxy: Connecting to 192.168.1.2:1780 with no proxy
(18:39:31) proxy: Connection in progress
(18:39:31) prefs: /pidgin/blist/width changed, scheduling save.
(18:39:31) prefs: /pidgin/blist/height changed, scheduling save.
(18:39:31) proxy: Connecting to 192.168.1.2:1780.
(18:39:31) proxy: Connected to 192.168.1.2:1780.
(18:39:31) util: request constructed
(18:39:31) util: Response headers: 'HTTP/1.1 200 OK Content-Type: text/xml
Content-Length: 3726 Connection: close Pragma: no-cache '
(18:39:31) util: parsed 3726
(18:39:31) upnp: parse_description_response(): could not get
serviceTypeNode 7
(18:39:31) upnp: purple_upnp_parse_description(): control URL is NULL
(18:39:31) bonjour: service advertisement - callback.
}}}
Why, for the Heaven's sake, Pidgin making query to 192.168.1.2?
Than 'Attempting connection to 192.168.1.2; Connecting to
192.168.1.2:1780 with no proxy; Connection in progress'
There is no Bonjour client on that host/IP address.
Why Pidgin connects it and what negotiates?...
Last part: "Connecting to 192.168.1.2:1780; Connected to 192.168.1.2:1780;
request constructed" even more confusing.
What kind of request it constructed?..
P.S. probably we need more detailed logging to fix reported problem.
--
Ticket URL: <http://developer.pidgin.im/ticket/12643#comment:17>
Pidgin <http://pidgin.im>
Pidgin
More information about the Tracker
mailing list