Wuala client is binding to the wrong IP address on XP; how to reassign?

I'm brand new to wuala, didn't realize how prevalent this issue was.

I disabled all of the other network adapters except my primary connection before launching wuala and it binds to the right connection.

But I'd have to go through the same routine every reboot. Meh.

hehe yeah, threaten the caleido team with suice, maybe they'll get their asses up at last and do something about it.

heh

:)

Anyone try this?

http://www.r1ch.net/stuff/forcebindip/

Did a Google search for bind application to a specific IP.

Now it'll be really easy to get huge cloud disk space by running multiple environment on one computer.

Force Bind IP doesn't work. It doesn't allow the local host connections to work, causing the app to fail to load (either that, or it doesn't kick in early enough to actually change the preferred IP address)

Azureus (now Vuze), has an IP binding option - it's java too, so clearly this option is possible to implement, it's just that the Wuala developers haven't got around to doing it yet :-(

its pretty crazy that this feature a lot of people are asking for still hasnt been implemented as of now.

must be really hard ;p

My (lousy) workaround involves temporarily disabling all but the IP I want to bind, start wuala client, and re-enable the other net connections.

That particular machine doesn't get rebooted much so it works; obviously this would be a real pain if you reboot often.

I believe they currently bind to 0.0.0.0 (all nic's) and upnp only goes to certain one. All we need is a box to override the upnp ip addess.

http://java.sun.com/docs/books/tutori... shows how to list all nics in java.

Yep, it's not hard to fix this one, you just add a configuration option and call socket.bind before using it. (Worse case make the configuration option an command line or environment variable)

you still keep wondering why caleido isnt doing anything at all to address this issue.

please add some bind-to-specific-ip/interface at last for crying out loud.
jebuz.

One of the μTorrent mods was saying Windows XP does not behave reliably when it comes to binding to IPs. The workaround that I've established for this is to use the free Virtual PC 2004, install microXP, and Wuala inside of that. You can select specific a specific MAC you want to bind to with Virtual PC.

They are binding to all interfaces, it's just the address that they report to the upnp server is wrong.

I am having the same issue on Mac OS X.

(Twiddles Thumbs)

After having a closer look at my connection stats I found that I'd not been connected correctly for sharing for almost a week. The green light was showing, but on closer inspection Wuala had bound itself to the "wrong" IP.
Turns out that it was bound to a virtual IP set up by VMWare. As much as I tried, it wouldn't un-bind until I uninstalled VMWare.
Bit of a pain.

If you manually port forward in your router it doesn't matter what wuala thinks. The ip in wuala is for UPnP (automatic port forward).

I can't use Wuala until this is implemented ... please do so soon =).

This is solved woth the latest update

Great news, thanks.
I've been forwarding the ports to workaround the issue, but using UPnP is a bit quicker and easier.