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.
hi there, i wanted to post the official question about what the exact technical requirements and capabilites of network access for wuala are, to allow wuala become a supernode, or a client node and all this techstuff information.
some of my wuala clients only become storage nodes (supernode capability false, and mediated over ip/node .....)
i wonder what the exact technical requirements for the networkconnection of wuala are and if this could be made more transparent to the userbase (documentation).
all of my clients run on highcapacity broadband nodes, but none of the wuala clients run directly on the external ip-address/interface visible to the external inet.
some wuala clients run via a upnp-capable internetgateway, others have normal portforwaring set up properly. all wuala client connections result in a good/green connection. all nodes exchange and host/trade storage.
so far it seems as if supernodecapability was somehow related to upnp-ed connection (or maybe direct inet connection without any firewall/restrictions).
i am wondering if this could be enhanced or why portforwarded wuala clients wont become supernodes.