Version: 4.1.85 / 0.60.81 (using Devel) Installed from: Compiled sources Currently the Jingle implementation in Kopete uses http://whatismyip.com/automation/n09230945.asp to retrieve the public IP address of the client, which is probably not the nicest way of doing this, and may also have some drawbacks. Some of which are: - The IP as seen by whatsmyip.com may not be the same as the one seen by the contact - It opens a popup in that kget/whatever applet A better solution might be to ask the Jabber server for the IP, or use the same mechanism that is used for file transfers. (It might be advisable to have a "how to get my ip" settings box for each account.) Random thought: The IP address retrieved for one account can probably differ from the IP address for another account, due to multiple IP addresses for this machine, NATs, VLANs, routing, etc.
In KDE 4.3 (or 4.4), a new revision of the Iris library will be used, this one will support Jingle directly with ICE-UDP support (which is a mechanism that connects 2 computers together, passing through NATs and everything) I will change the default setting so it is not done by default. The mechanism used to get the IP is different in XMPP File Transfer (there is a Jingle File Transfer protocol though).
(In reply to comment #1) > In KDE 4.3 (or 4.4), a new revision of the Iris library will be used, this one > will support Jingle directly with ICE-UDP support (which is a mechanism that > connects 2 computers together, passing through NATs and everything) > > I will change the default setting so it is not done by default. > > The mechanism used to get the IP is different in XMPP File Transfer (there is a > Jingle File Transfer protocol though). Has this change ever been done? Can I close this bug?