On 6/4/08, Dragon <[EMAIL PROTECTED]> wrote: > > André Warnier wrote: > > Mohit Anchlia wrote: >> >> 2. Another question I had was sometimes we don't get real physical IP of >>> the >>> machine but the IP of something that's in between like "router", is there >>> a >>> way to get the real IP so that we don't end up blocking people coming >>> from >>> that "router" or "proxy" >>> >> >> In my opinion, you cannot. The whole point of such routers and proxies is >> to make the requests look like they are coming from the router/proxy, so >> that is the sender IP address you are seeing at your server level, and >> that's it. Your server never receives the original requester IP address. >> > ---------------- End original message. --------------------- > > There are legitimate reasons for this to be done as well, indiscriminately > blocking such access is a bad idea as it will affect legitimate users. NAT > and IP address sharing are among the reasons. This allows an organization to > have a router with one public IP address to serve a larger internal network > with private IP addresses. Without this, we would have run out of IPv4 > addresses a long time ago. > > > Dragon
If there is no way to get the real IP address then how would router know which machine to direct the response to. It got to have some information in the packet. For eg: If A send to router B and router sends to C then when C responds how would B know that the response is for A.
