[Exodus-dev] File Transfers

[Marc Lewis]

I've been trying to get file transfers working for Exodus clients behind a
NAT based firewall for about a week now and have run out of things to try.
At this point, I think its a bug in Exodus, but I'm not sure.

The server is jabberd stable 6. The proxy server is the CVS version of
proxy65 running on Python 2.2.3 and Twisted 1.3.0. The version of exodus
is 0.9.0.0. The two clients are both behind NAT based firewall/routers on
different subnets but connecting to the same server on a third subnet.
They can chat and such just fine, just not transfer files.

Transfers work if both clients are set to manually use the proxy server in
Exodus. If, however, Exodus is set to discover the proxy server from the
server, the transfer sort of starts but doesn't actually work. The sender
starts sending data out until the proxy server's recieve queue is full, and
the recieving client says the transfer is complete immediately. The result
is a hung sending client and the reciever has a zero length file.

As I said, it works if both are set to manually use the proxy server.

Thoughts?

- Marc

[Zhaomin]

I have been meet same problem like yours,Do you have solution of it?
----- Original Message -----
From: "Marc Lewis" <***@blarg.net>
To: <exodus-***@jabberstudio.org>
Sent: Thursday, January 13, 2005 8:03 AM
Subject: [Exodus-dev] File Transfers

Post by Marc Lewis
I've been trying to get file transfers working for Exodus clients behind a
NAT based firewall for about a week now and have run out of things to try.
At this point, I think its a bug in Exodus, but I'm not sure.
The server is jabberd stable 6. The proxy server is the CVS version of
proxy65 running on Python 2.2.3 and Twisted 1.3.0. The version of exodus
is 0.9.0.0. The two clients are both behind NAT based firewall/routers on
different subnets but connecting to the same server on a third subnet.
They can chat and such just fine, just not transfer files.
Transfers work if both clients are set to manually use the proxy server in
Exodus. If, however, Exodus is set to discover the proxy server from the
server, the transfer sort of starts but doesn't actually work. The sender
starts sending data out until the proxy server's recieve queue is full, and
the recieving client says the transfer is complete immediately. The result
is a hung sending client and the reciever has a zero length file.
As I said, it works if both are set to manually use the proxy server.
Thoughts?
- Marc
--
Marc Lewis
Network Administrator
Blarg! Online Services, Inc.
http://www.blarg.net/~marc
_______________________________________________
Exodus-dev mailing list
http://mail.jabber.org/mailman/listinfo/exodus-dev

[Marc Lewis]

Post by Zhaomin
I have been meet same problem like yours,Do you have solution of it?

Nope. To see if it might be something that has been addressed before and
fixed, I just tried the latest nightly build of Exodus, 0.9.0.39. Same
problem, but now at least the reciever knows the transfer didn't work and
tells you the file may be corrupt.

Exact same symptoms. As long as both sides are configured to use the
specific proxy everything works.

[Peter Millard]

----- Original Message -----

Post by Marc Lewis
Transfers work if both clients are set to manually use the proxy server in
Exodus. If, however, Exodus is set to discover the proxy server from the
server, the transfer sort of starts but doesn't actually work. The sender
starts sending data out until the proxy server's recieve queue is full, and
the recieving client says the transfer is complete immediately. The result
is a hung sending client and the reciever has a zero length file.

Using auto-discover vs. manual just determines whether or not the proxy is
discovered by disco'ing the server or not. In manual mode, Exodus always
uses the jid specified in the options dialog. This shouldn't matter once the
transfer starts. Could this be a network problem timing out connections for
some reason? It sounds like bytes just stop (which I've never seen before).

pgm.

[Marc Lewis]

Post by Zhaomin
----- Original Message -----

Post by Marc Lewis
Transfers work if both clients are set to manually use the proxy server in
Exodus. If, however, Exodus is set to discover the proxy server from the
server, the transfer sort of starts but doesn't actually work. The sender
starts sending data out until the proxy server's recieve queue is full, and
the recieving client says the transfer is complete immediately. The result
is a hung sending client and the reciever has a zero length file.

Using auto-discover vs. manual just determines whether or not the proxy is
discovered by disco'ing the server or not. In manual mode, Exodus always
uses the jid specified in the options dialog. This shouldn't matter once the
transfer starts. Could this be a network problem timing out connections for
some reason? It sounds like bytes just stop (which I've never seen before).
pgm.

I'm sure its not a network timeout. I just double checked and tested my
theory against jabber.org. Using the same configuration, two clients
behind two different NAT routers on two different subnets, both set to
auto-discover the file transfer transport.

They both seem to discover the Jabber.org proxy server. The sender starts
its transfer, gets about 64K of the file sent and hangs. The reciever
starts the transfer and then immediately says the transfer is complete and
gives the option to open the file or close the window. The file that was
recieved is 0 bytes long.

It really appears to be a bug in Exodus. This is v0.9.0.0 on both sides,
one computer is running Windows 2000 Pro SP4, and the other is running XP Home
SP1.

- Marc

[Peter Millard]

----- Original Message -----

Post by Marc Lewis
I'm sure its not a network timeout. I just double checked and tested my
theory against jabber.org. Using the same configuration, two clients
behind two different NAT routers on two different subnets, both set to
auto-discover the file transfer transport.
They both seem to discover the Jabber.org proxy server. The sender starts
its transfer, gets about 64K of the file sent and hangs. The reciever
starts the transfer and then immediately says the transfer is complete and
gives the option to open the file or close the window. The file that was
recieved is 0 bytes long.
It really appears to be a bug in Exodus. This is v0.9.0.0 on both sides,
one computer is running Windows 2000 Pro SP4, and the other is running XP Home
SP1.

I thought you were using the latest daily build of Exodus? I do know that I
fixed a ton of bugs in file xfers since 0.9.0.0 (the last release). Please
conduct your tests using the latest daily build.

pgm.