Recently active problems in Wuala tagged with connection

hi there,

a main problem with the wuala project as whole is, that there is far too little information on technical details, far too little documentation and real information given by the developers.

people often wonder why the wuala software behaves this or the other way, search for solutions that are sometimes no real problems if the behaviour would be properly documented.

i started up some older build (winxp) wuala client after a while of downtime and it upgraded itself.
after logging in to the wuala network (username) the wuala client now works heavily on the wuala database files in probably reoganisation tasks (fragmentsxx.db and COMP-fragmentsxx.db files being messed with the whole time)

anyways so it literally took ages for this client to finish, and the connection status icon was yellow all the time. only after a long while, and when finally the insane diskactivity has finished, the connection status icon went green again.

ctrl+alt+d _shownetworkstats displayed that it wasnt connected to any supernodes during this period, hence the yellow icon i presume.

what makes me wonder if this is a neccessary behviour, that the client cant properly connect to the network until its finished with its database overhaul. maybe some multithreading designs could help, or maybe its just really the need to bring the database into a consistant and up-to-date state again before being able to add and fetch chunks of data again to and from it.

it would really be great if the wuala team could document its piece of software much more in detail.

Die interne IP wird von Wuala stäig falsch abgebildet. Es steht 192.168.122.1 statt 192.168.1.5 da. Dadurch kann weder der Router noch irgend eine andere Verbindung gefunden werden, die einen ordnungsgemän Datentransfer erlaubt. Ein im selben Netz eingebundener Windows Rechner hat kein Problem. Dort klappt auch das UPnP.

MfG,
Rhys

When you have Fusion running on the Mac, there are 2 extra network interfaces: vmnet1 and vmnet8. For some reason, Wuala is using these as the origination IP address instead of using en0/en1 depending on which one is up.

How can I kick Wuala into using the current default IP interface?

Thanks,

Wout.

Hi!

I'm using Wuala now for a week. I'm getting the status "Online", no problem, but only the yellow one. Sometimes, very rare, it gets the green one. But that happen maybe two times since i downloaded Wuala.

It's not able to connect with the external IP and if i try to test it, I'm only get this result:

Prürbindung...
Problem: Could not contact ping server A

Port is forwoarded on my router and i'm not using any firewall! Someone may has an idea??

Yours sincerely

I uploaded 2 mb file into my wuala space yesterday. Today I went to file properties and pressed Clear Cache button. Now when I'm trying to get my file back I have a problem: "Could not open file. Maybe Wuala is still busy downloading another file or there is no connection to the Wuala network. Please try again later. If you think this is a bug.....bla-bla-bla". How do I have to work to be sure that I can get my files back?

If I run Wuala, my Router always disconnect and reconnect. And If I close it, everything is OK, no connection Problems.

Every 10min Wuala, ICQ... is disconnected (internet).

I have a Belkin Router and Arcor as my DSP.

Since I have updated to alpha v.105 (Linux) I am having problems with my connection. It is o.k. for about a minute and then the status turns to yellow and shortly afterwards to red. After a few minutes I get a good connection again, but then it shuts down again and the whole procedure repeats itself. While the connection is down I can't even ping my wlan-router. After shutting down wuala, it takes about a minute and then I can ping my wlan-router again. I have already turned off the file system integration, but that doesn't do any good.

Heute morgen lief wuala problemlos. Als ich vorhin einen Reboot ausgefüatte, wollte wuala nicht mehr starten.
Deswegen füich einen weiteren Reebot durch.
Jetzt startet wuala auch, aber ich erhalte keine Verbindung.
unten links steht Connecting und dann kommt nach 5 Sekunden Offline

Seit heute morgen bekomm ich nur noch den gelben Status. Meine Verbindung zum Netz ist aber wie immer.

Hi folks,

several points in this post:
First: I temporarily forwarded 7492 to my server (some of you might still remember my old post about my server not having forwarded that port and the port not being able to be changed yet). So I did that and I ran the connection check which returns:
[code]
Analyzing Connection...
Got answer from Ping Server A, your external adress is /85.145.149.43:7492
Got answer from Ping Server B, your external adress is /85.145.149.43:7492
/85.145.149.43:7492 accepts incoming connections.
Congratulations, your connection is suitable for trading storage!
[/code]
Still, under my port settings, it says: X "Connection not suitable for trading storage"

Second: While in the connection tab in the settings it says that my connection is not suitbale, in the Storage tab it says: X "Your compiter is well connected."
Two points: There is a cross in front which doesn't correspond to the text and the text doesn't correspond to what it says in the Connection tab.

Third: Average online time is give in 3 significant figures but it says exactly 9.00% which obviously cannot be true because it has been saying that for almost 10 hours and I only use Wuala for approximately 1day so it should change quite quickly if I am online.

And last but not least:
Fourth: When the point next to the status indicator (which says "Online") is green, does that mean, that I can share storage or simply that I am online?

Thanks for reading my way too long post and taking the time to maybe answer me ^^,
Darkstriker

Dear Supportteam,

When you change your connection to allow the port you entered in wuala, the program keeps on counting the time it is online as OFFLINE time. Altough, you were online and available for trading storage. This means that I now added another day of downtime to my records while my server was online since approximately 2pm (cest=gmt+1). Which kind is kind of not nice.

Please fix that for future users who have a permanently on server and don't restart the app after opening ports or changing the port.

One more addition: Force the update on the client from the next version on (or at least alert users who don't turn off their app, that there is a version available).

Thanks =)

hi there,

lately i get a lot of these errors in the about dialobox (win32, latest builds) on networks with upnp routers when wuala client wants to check if theres a newer build out there...

if i close logout/restart wuala it downloads the latest build anyways even if the check in the about box failed.

would be great if the checking for a new build would be more reliable (maybe other protocol, triggering it directly with a button or a url and so on....)

maybe it has also to do with congested networks (even the local lan or the gateway to the inet), or nat-overloads at the gateway or such thing.

somehow i suspect that the versioncheck is also performed by means of udp rather than a tcp check of a browsing of some url/xml/file because the failed message turns up so very quickly/instantly on the client... there seems to be no timeout or something.

thanks.