Version: 0.11.2 (using KDE KDE 3.5.2) Installed from: Debian testing/unstable Packages OS: Linux I'm behind a NAT/firewall/router that has a dynamic IP address. I've forwarded ports to my computer, but it would be really nice if Kopete could auto-detect the WAN IP address so I wouldn't have to enter it every time it changes. There are several ways it could be done: * In at least some protocols (e.g. IRC), the server can tell the client what it thinks the client's IP address is. * There are web sites (like whatismyip.com) that can tell you your Internet IP address. It doesn't seem like it should be too difficult, and it would be a big timesaver.
See also wish #48989 (same issue for kpf).
The way to go is STUN. Maybe someone will have time to implement this for KDE4... http://en.wikipedia.org/wiki/STUN
No, the correct solution is to get rid of NAT, once and for all. See RFC 2775. I read over the idea about STUN and I think it's yet-another-hack-to-work-around-the-problem-that-already-has-a-proper-solution. I will not implement it. Discovery of the external IP address, however, may be a good idea for Kopete.
Thiago: What do we do until NAT is gone? We don't have control over when NAT disappears and we're not trying to break ground in network technology here. People expect their IM to just work. Rather than saying "that's such a hack, i won't do it", please help us find a solution rather than adding to the problem.
Well (imho) solution is using UPnP NAT Traversal which is what Messenger does.
What about non UPnP capable routers? Maybe both UPnP and STUN should be implemented to give users as much choice as possible? The success of Skype IMHO shows that automagical NAT traversal is something users appreciate. No complicated setup, no port forwarding, it just works.
I just meant that *I* won't implement this. And, as I said, Kopete may benefit from this, but I don't think it belongs in the KDE Libraries level.
This definitely is something that's only useful for IM and P2P applications. It doesn't belong into kdelibs. But it would be nice to have a libwanip or something so that all the apps needing the WAN IP could rely on the same implementation.
Well I already have a working proof of concept code for UPnP ( which our own Ivor Hewitt himself coded from ground up ). But I have no idea about STUN.
1. Pardon my poor english, it's not my native language. 2. Thank you so much for this great piece of software! 3. I'm not sure if this is the right place to talk about this, but this bug is the most related to the problem I'm having with Kopete right now. --- Version: 0.12.7 (using KDE 3.5.10) Installed from: Mandriva 2009 One OS: Linux Hi! When I send an MSN message containing a local IP address (e.g. 192.168.x.x) to someone in the same local network as me, the local IP is translated to the public IP address (e.g. 81.121.x.x) and thus it's unusable inside the local network, because of NAT or iptables rules. The same applies to incoming messages. Maybe the IP translation discussed above should be done only when the remote IP address doesn't match the local IP address (resolved)? At least there should be an option somewhere to disable the IP resolution feature so I don't have to ask people to send their IP like "192 168 x x" with space separators instead of dots, and I don't have to correct it on my side before using it. For people who know the difference between local and public IP addresses, this Kopete feature is very annoying and time wasting. Thank you for your time ! Best regards
Dear user, unfortunately Kopete is no longer maintained. Please migrate to another solution, e.g. for Jabber a possibility is Kaidan, for Matrix a candidate is NeoChat.