my application will be used in that environment:
the server has a real ip,
but the client may be in a LAN , the client doesn't have a real ip ,it connects to WAN
just like a chat software, or other p2p software,
the server has to send messages to client initiatively and continuously.
(that means the server will send messages .At the same time ,the client will accept those messages like a server.)
if i use socket to write my code , i just need use send ,
then, although the client in a LAN ,i can connect to it ,and send messages initiatively.
but now ,i can't get the client 's ip and port in ICE.
how to do when i have to send messages to a client which is in a LAN and don't have a real ip ?
i need the server sends messages initiatively.
is there any example which can let me study?
Well, you can't have the server connect to the client, for the reasons you gave. But once the client is connected, there is nothing to stop messages from being sent in either direction at any time. You just have to program the client to be ready to receive messages from the server.`
luri ron wrote:didn't quite get your question. here is my 2 cents.
ip is the network layer. without the ip address, i don't think you can send send anything.
let us assume you have the network layer, if you want to server to send something to client, you can send the message using UDP first from the "server" to "client"
who said i want to connect to any computer that does not have ip.
client have a local ip . but to connect to WAN it uses a common natted ip.
in actual many internet provider gives you a natted ip to connect to net .
so when you are connected to net if you see your ip address by an ipconfig. you may not get a ip that is global.
most of the time you get a natted ip