pidgin xmpp file sharing

Ishwor Gurung ishwor at loopback.ath.cx
Sun Mar 29 08:06:28 EDT 2009


hello people,

I am trying to share file within a LAN using pidgin and ejabberd.

I've setup 2 test accounts on the jabber server to test for this purpose.

The 2 accounts can chat with each other nicely (no worries there) but
when trying to send a binary files (such as .pdf), it fails.

The pidgin setting is as follows -

***First account***
//Tab Basic//
Protocol: XMPP
Username: ishwor
Domain:	machapuchre
Resource: Home
Password: abracadabra
[*] Remember password

//Tab Advanced//
[] Require SSL/TLS
[] Force old (port 5223) SSL
[] Allow plaintext auth over unencrypted streams
Connect port: 5222
Connect server: 192.168.1.109
File transfer proxies: [empty]
[*] Show Custom Smileys
Proxy type: No Proxy

***Second account***
//Tab Basic//
Protocol: XMPP
Username: aashish
Domain:	machapuchre
Resource: Home
Password: abracadabra
[*] Remember password

//Tab Advanced//
[] Require SSL/TLS
[] Force old (port 5223) SSL
[] Allow plaintext auth over unencrypted streams
Connect port: 5222
Connect server: 192.168.1.109
File transfer proxies: [empty]
[*] Show Custom Smileys
Proxy type: No Proxy


Now, the interesting bit. I started both pidgin using "pidgin -d" and
try to understand what the heck was going on (not up to sleeve on the
understanding of XMPP protocol). So here's what happens -

//On the sender's side//

(22:18:45) jabber: Sending (ssl): <iq type='get'
id='purpleb4a25efe'><ping xmlns='urn:xmpp:ping'/></iq>
(22:18:45) jabber: Recv (ssl)(234): <iq from='aashish at machapuchre'
to='aashish at machapuchre/Home' type='error' id='purpleb4a25efe'><ping
xmlns='urn:xmpp:ping'/><error code='503'
type='cancel'><service-unavailable
xmlns='urn:ietf:params:xml:ns:xmpp-stanzas'/></error></iq>
(22:18:53) jabber: jabber_si_xfer_free(): freeing jsx
0x9f8a330(22:18:53) jabber: in jabber_si_xfer_cancel_send
(22:19:03) dbus: Need to register an object with the dbus subsystem.
(If you are not a developer, please ignore this message.)
(22:19:03) dbus: The signal "blist-node-extended-menu" caused some dbus
error. (If you are not a developer, please ignore this message.)
(22:19:10) jabber: Sending (ssl): <iq type='set' id='purpleb4a25eff'
to='ishwor at machapuchre/Home'><si xmlns='http://jabber.org/protocol/si'
id='purpleb4a25f00'
profile='http://jabber.org/protocol/si/profile/file-transfer'><file
xmlns='http://jabber.org/protocol/si/profile/file-transfer'
name='Resume.pdf' size='239869'/><feature
xmlns='http://jabber.org/protocol/feature-neg'><x xmlns='jabber:x:data'
type='form'><field var='stream-method'
type='list-single'><option><value>http://jabber.org/protocol/bytestreams</value></option></field></x></feature></si></iq>
(22:19:15) jabber: Sending (ssl): <iq type='get'
id='purpleb4a25f01'><ping xmlns='urn:xmpp:ping'/></iq>
(22:19:15) jabber: Recv (ssl)(234): <iq from='aashish at machapuchre'
to='aashish at machapuchre/Home' type='error' id='purpleb4a25f01'><ping
xmlns='urn:xmpp:ping'/><error code='503'
type='cancel'><service-unavailable
xmlns='urn:ietf:params:xml:ns:xmpp-stanzas'/></error></iq>
(22:19:32) jabber: Recv (ssl)(348): <iq from='ishwor at machapuchre/Home'
to='aashish at machapuchre/Home' type='result' id='purpleb4a25eff'><si
xmlns='http://jabber.org/protocol/si'><feature
xmlns='http://jabber.org/protocol/feature-neg'><x xmlns='jabber:x:data'
type='submit'><field
var='stream-method'><value>http://jabber.org/protocol/bytestreams</value></field></x></feature></si></iq>
(22:19:33) network: Listening on port: 59966
(22:19:33) network: Couldn't create UPnP mapping
(22:19:33) network: Couldn't create UPnP mapping
(22:19:33) jabber: jabber_si_xfer_bytestreams_listen_cb() will be
looking at jsx 0x9ff0688: jsx->streamhosts (nil) and sh->jid
0x9c68c80(22:19:33) jabber: Sending (ssl): <iq type='set'
id='purpleb4a25f02' to='ishwor at machapuchre/Home'><query
xmlns='http://jabber.org/protocol/bytestreams'
sid='purpleb4a25f00'><streamhost jid='aashish at machapuchre/Home'
host='192.168.1.109' port='59966'/><streamhost
jid='aashish at machapuchre/Home' host='10.1.1.3'
port='59966'/><streamhost jid='proxy.machapuchre' host='127.0.0.1'
port='7777'/></query></iq>
(22:20:03) jabber: Recv (ssl)(204): <iq from='ishwor at machapuchre/Home'
to='aashish at machapuchre/Home' type='error' id='purpleb4a25f02'><error
code='404' type='cancel'><item-not-found
xmlns='urn:ietf:params:xml:ns:xmpp-stanzas'/></error></iq>


//Comment//
UPnP is enabled in the wrt wireless modem.

What on earth is it trying to do with 10.1.1.3?
//end comment//


//On the receiver's side//

(07:48:28) jabber: Recv (ssl)(401): <iq from='aashish at machapuchre/Home'
to='ishwor at machapuchre/Home' type='set' id='purpleb4a25efc'><query
xmlns='http://jabber.org/protocol/bytestreams'
sid='purpleb4a25efb'><streamhost jid='aashish at machapuchre/Home'
host='192.168.1.109' port='35028'/><streamhost
jid='aashish at machapuchre/Home' host='10.1.1.3'
port='35028'/><streamhost jid='proxy.machapuchre' host='127.0.0.1'
port='7777'/></query></iq>
(07:48:28) dns: DNS query for '192.168.1.109' queued
(07:48:28) dns: Wait for DNS child 22730 failed: No child processes
(07:48:28) dns: Created new DNS child 22991, there are now 1 children.
(07:48:28) dns: Successfully sent DNS request to child 22991
(07:48:28) dns: Got response for '192.168.1.109'
(07:48:28) dnsquery: IP resolved for 192.168.1.109
(07:48:28) proxy: Attempting connection to 192.168.1.109
(07:48:28) proxy: Connecting to
e6e3fcf74ddc8bea543f2628a664ed89ac74c6f4:0 via 192.168.1.109:35028
using SOCKS5
(07:48:28) socks5 proxy: Connection in progress
(07:48:43) jabber: Streamhost connection timeout of 15 seconds exceeded.
(07:48:43) jabber: si connection failed, jid was
aashish at machapuchre/Home, host was 192.168.1.109, error was Timeout
Exceeded.
(07:48:43) dns: DNS query for '10.1.1.3' queued
(07:48:43) dns: Successfully sent DNS request to child 22991
(07:48:43) dns: Got response for '10.1.1.3'
(07:48:43) dnsquery: IP resolved for 10.1.1.3
(07:48:43) proxy: Attempting connection to 10.1.1.3
(07:48:43) proxy: Connecting to
e6e3fcf74ddc8bea543f2628a664ed89ac74c6f4:0 via 10.1.1.3:35028 using SOCKS5
(07:48:43) socks5 proxy: Connection in progress
(07:48:58) jabber: Streamhost connection timeout of 15 seconds exceeded.
(07:48:58) jabber: si connection failed, jid was
aashish at machapuchre/Home, host was 10.1.1.3, error was Timeout Exceeded.
(07:48:58) dns: DNS query for '127.0.0.1' queued
(07:48:58) dns: Successfully sent DNS request to child 22991
(07:48:58) dns: Got response for '127.0.0.1'
(07:48:58) dnsquery: IP resolved for 127.0.0.1
(07:48:58) proxy: Attempting connection to 127.0.0.1
(07:48:58) proxy: Connecting to
e6e3fcf74ddc8bea543f2628a664ed89ac74c6f4:0 via 127.0.0.1:7777 using SOCKS5
(07:48:58) socks5 proxy: Connection in progress
(07:48:58) socks5 proxy: Connected.
(07:48:58) proxy: Connection attempt failed: Connection refused
(07:48:58) jabber: si connection failed, jid was proxy.machapuchre,
host was 127.0.0.1, error was Connection refused
(07:48:58) jabber: Sending (ssl): <iq type='error' id='purpleb4a25efc'
to='aashish at machapuchre/Home'><error code='404'
type='cancel'><item-not-found
xmlns='urn:ietf:params:xml:ns:xmpp-stanzas'/></error></iq>
(07:48:58) jabber: jabber_si_xfer_free(): freeing jsx
0x9b01f50(07:48:58) jabber: in jabber_si_xfer_cancel_recv

//Comment//
(07:48:28) proxy: Connecting to
e6e3fcf74ddc8bea543f2628a664ed89ac74c6f4:0 via 192.168.1.109:35028
using SOCKS5.
Where is this comming from? I have already set NO SOCKS5 or any other
proxy already as you can see in the above settings.
Ditto for:
(07:48:43) proxy: Connecting to
e6e3fcf74ddc8bea543f2628a664ed89ac74c6f4:0 via 10.1.1.3:35028 using SOCKS5
(07:48:43) socks5 proxy: Connection in progress
//end comment//

And then the Pidgin shows this nice little GUI saying "client canceled"
on the file transfer window (on the sending side).

Is XMPP file sharing this broken in Pidgin or is it something utterly
stupid that i am doing? I have been seriously googling all over the
place without much success.

Cheers,
Ishwor



More information about the Support mailing list