linux not well connected

nope, how do i configure my router on ubuntu linux?

I don't know if this is what causes the problem but either way you should always configure your router to forward connections to you. Go to http://portforward.com/english/router... , choose your router model e follow the steps.

makes not much sense for a ubuntu linux user

Hello. I've got the same or at least a simliar problem.

Hallo. Ich habe ein äliches bzw. das gleiche Problem.

My Ubuntu 7.10 (Gutsy Gibbon) seems to be unable to accept incoming connections. It works perfectly on windows, the router UpnP-configuration is okay. Wuala just seems to be not listening. I've asked the console and got the following output:

Proto Recv-Q Send-Q Local Address Foreign Address State Benutzer Inode PID/Program name

tcp6 0 0 :::26183 :::* LISTEN 1000 31567 7899/java

tcp6 0 0 :::26184 :::* LISTEN 1000 31576 7899/java

tcp6 0 0 :::57183 :::* LISTEN 1000 31545 7899/java

udp6 0 0 :::7234 :::* 1000 31533 7899/java

udp6 0 0 :::26183 :::* 1000 31566 7899/java

udp6 0 0 :::26184 :::* 1000 31575 7899/java

The ahavi-daemon is not needed here, so I deleted it from the output. I don't understand much of this output, but as fair as I understand Wuala does not listen to it's 'sharing port' number 7234.
I hope, it is Wuala that opened these ports, but I think so because no other Java-Software is running.
So far, any ideas? ;)

That was in English for general comprehension. Now in German, for our heroes in Switzerland. :D

Nun auf Deutsch. Auf Englisch, damit diese Frage ül verstanden wird. Ihr seid ja soweit ich weißin der Schweiz...

Also, mein Ubuntu 7.10 (Gutsy Gibbon) scheint nicht in der Lage zu sein, die Speicherplatz-teilen-Verbindungen aufzubauen. Auf Windoof XP funktioniert wunderbar, die Konsole von Wuala gibt auch eine erfolgreiche Konfiguration von UpnP aus. Allerdings offenbarte eine Konsolenfrage ein etwas seltsames Bild:

Proto Recv-Q Send-Q Local Address Foreign Address State Benutzer Inode PID/Program name

tcp6 0 0 :::26183 :::* LISTEN 1000 31567 7899/java

tcp6 0 0 :::26184 :::* LISTEN 1000 31576 7899/java

tcp6 0 0 :::57183 :::* LISTEN 1000 31545 7899/java

udp6 0 0 :::7234 :::* 1000 31533 7899/java

udp6 0 0 :::26183 :::* 1000 31566 7899/java

udp6 0 0 :::26184 :::* 1000 31575 7899/java

Der avahi-Daemon wird hier wohl nicht benöt...
Soweit ich verstehe, was da steht, höWuala auf dem Port 7234 einfach nicht zu. Dabei sollte es das!
Ich hoffe, es ist Wuala, das unter dem Namen „java“ den Port geöet hat. Aber es lät soweit ich weißkeine andere Java-Software.
Ideen? ;)

After the reply one minute ago...
It works with Windows, so I don't think it's a router problem here..

Nach der Antwort eine Minute zuvor...
Es funktioniert mit Windows, also schließ ich eine Router-Problem aus.

Greets,
SchöGrüMarcel

It unfortunately doesn't work. The testing function gives the following output:

Analyzing Connection...
Got answer from Ping Server A, your external adress is /84.*.*.89:7234
Got answer from Ping Server B, your external adress is /84.*.*.89:7234
/84.161.221.89:7234 does not accept incoming connections.
Trying UPnP...
Found UPnP router http://192.168.2.1:5431/dyndev/uuid:5...
Port forwarding setup successful, retesting connection...
/84.161.221.89:7234 does not accept incoming connections.
It seems your connection is not suitable for trading storage.
Please enable UPnP on your router/firewall or configure it manually to forward incoming UDP connections
on port 7234 to this computer. If you have already done so, you
might need to restart your router and/or Wuala.

(I've changed the sharing port to my loved 7234.)

'Port forwarding setup succesful, ...'
Hm? What does that mean?
On Windows, I got the same error 'cause the firewall was in 'stealth mode', but Ubuntu doesn't even have a firewall!

Greets,
Marcel

No, I don't spam console outputs, no...^·-

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...

@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...

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 ...