AW: [standards-jig] Re: My IP Address

Heiner Wolf wolf at
Tue Sep 2 10:11:56 UTC 2003


asking the server (or some other external instance) is useful to get the
externally visible IP address. Sometimes the client has multiple IP
addresses from multiple network interfaces, externel, internal
addresses, dialup and LAN at the same time, etc. NAT makes it even more
difficult for a client to determine the correct address for a
"jabber:iq:ip" response. So, asking the server gets back the address
which the server "sees" on the connection. This is most likely the one
that will be useful for other clients in P2P. 

Dr. Klaus H. Wolf
bluehands GmbH & Co.mmunication KG
+49 (0721) 16108 75
-----Ursprungliche Nachricht-----
Von: Alexander Gnauck [mailto:gnauck at]
Gesendet: Dienstag, 2. September 2003 11:17
An: standards-jig at
Betreff: [standards-jig] Re: My IP Address


Justin Karneges wrote:
> Hi,
> What about a simple way of asking the server for the client's own IP
> The AIM and ICQ protocols have this to assist with direct connections
> clients.  It can be useful for clients stuck behind NAT, particularly
on a 
> network with a dynamic connection, so that they don't have to each be 
> configured with external IP address information.  A simple port
forward at 
> the router will do.

Why do you want to ask the server. You can do this with a "iq" and ask 
the the other clients. In our open source demo client we have done this 
for Netmeeting integration with jabber:iq:oob.

We could take something like this:

     from='user1 at'
     to='user2 at'
   <query xmlns="jabber:iq:ip"/>

     from='user2 at'
     to='user1 at'
   <query xmlns="jabber:iq:ip">
     <desc>my IP Adress</desc>


Alexander Gnauck
mailto:gnauck at
jabber:gnauck at

Standards-JIG mailing list
Standards-JIG at

More information about the Standards mailing list