Loading Profile...
Wuala launch is sometimes very slow to launch whilst connected wirelessly to eduroam
Environment:
* Mac OS X 10.6
* eduroam on University of Sussex campus
* 802.1X authentication
* link speed 54 Mbit/s
Sometimes, not always, Wuala takes an extraordinarily long time to start.
Away from campus, limited to a far slower connection, I notice no such delays.
Are slow starts to be expected in certain network environments? Is there anything I can/should do to reduce such delays?
Once Wuala is started, in its Preferences dialogue I see:
> Connection type B: Limited reachability
When I click 'Check again' the cursor spins for a very long time whilst the report reads 'Trying to find UPnP router...' and eventually, '...no UPnP router could be found.'.
I estimate that the time spent 'Trying to find UPnP router' was around the same length of time that I sometimes wait for Wuala to launch.
TIA for any advice.
* Mac OS X 10.6
* eduroam on University of Sussex campus
* 802.1X authentication
* link speed 54 Mbit/s
Sometimes, not always, Wuala takes an extraordinarily long time to start.
Away from campus, limited to a far slower connection, I notice no such delays.
Are slow starts to be expected in certain network environments? Is there anything I can/should do to reduce such delays?
Once Wuala is started, in its Preferences dialogue I see:
> Connection type B: Limited reachability
When I click 'Check again' the cursor spins for a very long time whilst the report reads 'Trying to find UPnP router...' and eventually, '...no UPnP router could be found.'.
I estimate that the time spent 'Trying to find UPnP router' was around the same length of time that I sometimes wait for Wuala to launch.
TIA for any advice.
I’m undecided
1
person has this problem
I have this problem, too!
Tell me when someone solves it.
The more people who report this problem, the more it gets noticed.
The more people who report this problem, the more it gets noticed.
Create a customer community for your own organization
Plans starting at $19/month
-
Inappropriate?Hi Graham,
how long is an extraordinarily long time in minutes? ;)
Had to ask too what can cause this delay. Slow starts are usually not expected. A long period to get usably connection (to "talk" with the router) could be a reason.1 Comment
Add a comment
This solves the problem
-
The inbound connectivity isn't needed to get going (only for trading). If it is part of the inital startup it should be in a separate thread. Worth looking into, even if it only is confirmed and put on that long list of things to work on. -
Inappropriate?Could you please run "ping update.wuala.com" in a terminal and post the output here? As bagelcat said, the start should be quite fast as Wuala starts downloading/updating those classes needed first to show the GUI.
-
Inappropriate?> Away from campus, limited to a far slower connection, I notice
> no such delays.
Proving that generalisation wrong: this morning, working from home with that relatively slow network connection, Wuala *did* fail to launch.
http://pastebin.ca/1562151 for a Console view of all messages filtered for 'wuala'. Line 35 may have been a force quit when I grew impatient.
> the start should be quite fast as Wuala starts
> downloading/updating those classes needed first
> to show the GUI.
OK, at line 37 of http://pastebin.ca/1562151 I see the update to version 165.
> ping update.wuala.com
After a morning on campus (limiting myself to eduroam) I'm now back home, possibly on a different IP address to the one that I used this morning. Wuala launched quickly and the results of the ping are:
--- update.wuala.com ping statistics ---
119 packets transmitted, 118 packets received, 0.8% packet loss
round-trip min/avg/max/stddev = 47.570/51.175/59.486/1.625 ms
— http://pastebin.ca/1562153 for details.
I’m happy
EMPLOYEE
EMPLOYEE
