Recent activity
Subscribe to this feed
A comment on the question "linux not well connected" in Wuala:
Thanks for reply. I am using an ubuntu derivative. I don't think there is any software firewall. One suspicious thing I noticed - I configured wuala to listen on port 4004. Here is what netstat shows:
fedor@fedor-laptop:~$ netstat -u -l
Active Internet connections (only servers)
Proto Recv-Q Send-Q Local Address Foreign Address
State
udp 0 0 *:32769 *:*
udp 0 0 *:bootpc *:*
udp 0 0 *:mdns *:*
udp 0 0 fedor-laptop:ntp *:*
udp 0 0 localhost:ntp *:*
udp 0 0 *:ntp *:*
udp6 0 0 *:4004 *:*
udp6 0 0 *:26183 *:*
udp6 0 0 *:26184 *:*
udp6 0 0 fe80::216:6fff:fea7:ntp *:*
udp6 0 0 ::1%134619192:ntp *:*
udp6 0 0 *:ntp *:*
as you can see it's listening on udp6, but not udp. I wonder if this is the cause of the issue. Thanks!
PS. oops this does not seem to format well, but you get the idea... – fedor, on June 07, 2008 06:40
A comment on the question "linux not well connected" in Wuala:
Maybe you need to configure your (software-) firewall. This is definitively the case for SUSE. Maybe with other distros too. – Roger, on June 06, 2008 06:38
A comment on the question "linux not well connected" in Wuala:
I still seem to be having this issue. Router is set up (manually) and I tried editing /etc/hosts , but it does not help. – fedor, on June 05, 2008 19:51
hjvjglkbsbfb started following the idea "Use Sun HotSpot JVM, not GIJ" in Wuala.
oona replied on March 10, 2008 14:46 to the idea "Use Sun HotSpot JVM, not GIJ" in Wuala:
As Luzius said, we've just added it: http://download.wua.la/en/linux_dl.html
Thanks again!
Luzius replied on March 10, 2008 10:18 to the idea "Use Sun HotSpot JVM, not GIJ" in Wuala:
NikolasCo shared an idea in Wuala on March 10, 2008 02:15:
Use Sun HotSpot JVM, not GIJUse Sun HotSpot JVM, not GIJ ...
GIJ 4.2 and 4.3 hangs at the login screen or displays an error.
Note that versions can be checked easily with java -version.
Gentoo: java-config
Debian and Ubuntu: update-alternatives --config java
Running with GIJ yields the following error:
XML error
Build: Linux 79
App: Domain Application, user: not logged in
(Data Application, not connected
NikolasCo replied on February 09, 2008 01:30 to the question "linux not well connected" in Wuala:
Correction: it doesn't use the first entry in /etc/hosts; it's just continuing the lookup of the hostname (fetched via the uname system call, a la uname -n). So, if you add an /etc/hosts entry for the currently configured IP address, UPnP works as expected.
This doesn't fix the issue for me because 1) I'm behind at least two layers of NAt at the moment and 2) I'm using a laptop, which wanders a lot... A system-config workaround is unsavory, though; enumerating the current interfaces seems like the way to go, probably after using getLocalHost and calling isLoopback on that, so well-configured systems can specify their "default" IP.
The code is trivial, so I haven't bothered posting it ... I've just been fiddling with a separate test class/program to figure out what's going on (in combination with strace -f) and what the "right" solution might be ...
Ivan Pulleyn replied on February 09, 2008 00:48 to the question "linux not well connected" in Wuala:
@NIkolasCo: If that's the case, you should be able to hack /etc/hosts to work around the problem, correct? BTW, this also implies that a multi-homed Linux machine might have problems because it may return an address for the wrong local interface.
I had exactly the same problem(s) on a P2P software product that I worked on. If you need me to patch the code for the linux version, just let me know :-)
Ivan...
NikolasCo replied on February 08, 2008 21:19 to the question "linux not well connected" in Wuala:
I've had at least a similar issue with UPnP configuration. My "router" has UPnP request logging, so I was able to see the following:
1 02/08 07:26:59 add port failed 127.0.1.1 7453 UDP 7453
I didn't immediately trust this, and did a package capture to confirm it; Wuala is sending a SSDP/SOAP message with NewInternalClient set to 127.0.0.1
Looking into the issue further, I suspect that Wuala uses java.net.INetAddress.getLocalhost(); on Linux this often doesn't work (it tries to lookup hostname via DNS, and seems to fall back to just reading the first line of /etc/hosts). It seems that using NetworkInterface.getInterfaces() is necessary...
Loading Profile...

