Send file error

Bug #140289 reported by Bug Importer
0
Affects Status Importance Assigned to Milestone
Coccinella
New
Medium
Unassigned

Bug Description

I trying use Coccinella as Jabber client because I am
very like the Whiteboard tools. However I got some
bugs report as the following that make me hesitate to
use it :

1. Send file : Our company use a NAT local network,
everything allright if we send file between the same
network. But if outside to other users, the send file
function get problem : the receiver side progress bar will
starting but stick in arrount 10%, some second later it
will quit the file transfer progress screen, the file which
recevied only have file name but not complete
successful. The sender side : everything seems allright
and also will get sent OK message as normal.

It will happen also in whiteboard if import any files or
images that can sync to other user very well in local
network but it will fail (cannot show and without any
message) to sync with other users outside local NAT.

2. Whiteboard : After login and create a new
whiteboard, press the "Send" button it will get the error
message (Error : expected boolean value but got "not
valid jid form")

Hope get solution for this part from you.

regards,
Henry Au
A Coccinella user

Revision history for this message
Mats (matsben) wrote :

1. I currently don't handle NATs or firewalls at all. There is a
proposed solution for this in the Jabber protocol, but it is complex
to implement, and also requires binary streaming inbound the
Jabber server. However, you could try fill in the ip address in the
preference dialogs proxy page. This should be the ip as seen by
outsiders but this is completely untested so beware!

2. Bug fixed some time ago.

Revision history for this message
Pcbsl (pcbsl) wrote :

Thanks for your follow up Matben,

1. May I ask is that really about the NATs or firewalls
problem. Since the application can work very well in WB,
Chat and send message etc, but only Send File in problem ??

2. I got what I can get the latest 94.11 version but still with
this problem. Is it mean it come new ver and fixed with it.

best regards,
Henry Au

Revision history for this message
Mats (matsben) wrote :

1. Yes it is. Everything but file transport goes via the jabber
server so it is not affected by NATs. For file transports, the app
runs two embedded servers, and a client must connect to any of
this servers from outside the NAT. But the ip address a client
reports for its server is the local ip, but the external address seen
from the other side is different. Look in the prefs proxy panel and
the external ip address field. Try to figure out this ip if you can.
Untested!

2. I'm getting closer to a 0.95.0 release but have no time to add
this complicated code before that.

Best Wishes, Mats

Revision history for this message
Bug Importer (bug-importer) wrote :

Thank you very much for you info.

Henry

Revision history for this message
Mats (matsben) wrote :

I've just got a router with NAT at home and my tests show that it
should be possible. I've collected the main steps for doing this at
http://hem.fyristorg.com/matben/howto/nats/index.html
Mats

Revision history for this message
Mats (matsben) wrote :

Forgot to say that this will likely only work with current cvs
version and coming 0.95.0.

Mats

Revision history for this message
Mthain (mthain) wrote :

Whiteboard is a great feature but seems unstable (MacOS 10.4.7)
When I loaded the chess board from Library i kept getting an error message
that
required a click 'OK' to dismiss it , this cycled many times before I
could use the
whiteboard or quit Coccinella (Force quit from Dock wouldnt work)

Revision history for this message
Mats (matsben) wrote :

1. No file transfer at all including images etc from the whiteboard will
work through NATs and firewalls. This is due to the nature of the TCP
sockets which have no chance of penetrating those. It means that
normal network traffic (TCP/IP) will never work through NATs etc which
is the normal situation when doing p2p. What people do instead is build
their own network protocol on top of UDP to get secure transfers
through NATs etc. This is like reinventing the wheel once again and is
IMHO a very awkward situation where the suceess of internet has been
the generally accepted TCP/IP protocol. I haven't had the energy to look
into UDP yet but will give it ago when I get some time.

2) Will look into it.

Mats

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.