On 07/02/2006, at 1:25 AM, Stian B. Barmen wrote: >> To make sending work in iChat, I had to apply the attached >> patch (while a 'mode' attribute is required by JEP-0065 on >> streamhost offers, iChat apparently doesn't set this). With >> this patch, file sending (and >> receiving) is working great! >> >> I've only found a minor issue with file sending. If the >> connection between the Jabber client and the transport is >> faster than the connection between the transport and the MSN >> Messenger client, the progress bars in the Jabber client and >> the MSN Messenger client don't match (the progress bar in the >> Jabber client will run faster) - so as a Jabber user I don't >> know when the transfer is actually completed. Right now the >> transport will receive data from the Jabber client as fast as >> it can, and buffer the data (the entire file being sent) in >> memory - this leads to quite a large use of memory. It would >> be nice if the transport would only buffer a small amount of >> data and throttle the Jabber client sending data. >> >> I guess the same issue is also present when receiving files >> and the connection between the MSN Messenger client and the >> transport is faster than the connection between the transport >> and the Jabber client. >> >> Best regards, >> Lars >> > > Hello all! > > Is there firewall issues with the MSN clients? Seems I cannot send to > MSN > users that is behind some firewalls. And sometimes MSN clients behind > firewalls cannot send to me. One guy got the file sent but it stalled > at 1 > and 0 kb left, my jabber client got stuck on 0%. But he could receive > files > I sent. > > Also with iChat my users reported that the file sending feature was > disabled. Lars patch was not applied into svn so I patched it manually > now. > The result is now that file sending is available, and the receiver > gets a > request for transfer to accept to, but the transfer just stalls. Seems > no > data gets sent. Kinda the same issues I have with firewalls. The > receive was > MSN 7.5 also behind a firewall. > > Jabber.no has ft socks5 on 8010 and is open in the firewall. Could > there be > more settings that has to be done on the server? Also, should Lars > patch be > added to SVN? > > Sorry for my bad error description, but I just did some quick random > tests. > > Best regards > Stian B. Barmen
The getting stuck on 0% is a problem I've seen occasionally. I haven't worked out the cause yet. It always seems to work if I just try it again. There shouldn't be any issues with firewalls, except possibly for sending files to MSN users. If the Jabber user is behind a firewall, and they can't find a proxy65 component on the server to route the transfer through, then it won't go ahead. So make sure you have proxy65 installed. A little bit of Jabber file transfer background. The sender of the file is responsible for finding a socks5 streamhost for the receiver to connect to. The default streamhost is actually the sender. However if the sender is firewalled, then they have to find another streamhost. The recommended way to do this is to browse the server with disco#items, and see if anything comes up with category="proxy". If so, query that JID and find out if we can use it as a proxy. Then the sender will tell the receiver to connect to the proxy, and the sender will also connect to the proxy, and the transfer goes through. If no proxy is found, then the sender goes ahead and instructs the receiver to connect to itself, and the receiver can't. Either because the sender isn't addressable (behind a NAT), or the port is blocked, or both. Your best bet is to install the proxy65 component. Have a look on jabberstudio.org for it. If you're using Psi, you have to set the data transfer jid (something like that) setting. It doesn't automatically browse for proxies yet I don't think. --- James
