> From: manikandan mvk [mailto:[EMAIL PROTECTED] 
> Basically I have a question ,If the request is made from 
> multihomed machine
> ,which IPaddress will be taken as clients's IPaddress?. Does it is
> configurable  or how it decides that ?

A typical client, such as a Web browser, will acquire a TCP endpoint
dynamically from the operating system.  Most OSs will hand back a TCP
port bound to IP address 0.0.0.0 (i.e. all adapters), with a specific
port number.  When the client then connects that endpoint with another
system, such as a server, the OS will pick one adapter to send the
initial TCP SYN from.  This is entirely OS-specific, and may even depend
on factors such as load balancing and the queues on the adapters at that
instant.  That will become the client's apparent IP address for the
duration of that TCP connection.  If the connection is closed and
another is opened, it may appear from a different IP address; again,
that behaviour is OS-specific.

If you want to change this behaviour, you will need control over the
client so that it obtains a socket at a specific adapter.  This is
possible if you control the network code in the client.  It is generally
not possible if the client is eg. a browser.

To find out in your case (assuming you're running Windows or UNIX on the
client):

- Make a number of connections from your client to your server,
downloading a sufficiently large file that the request won't finish for
a few seconds;

- While the request is in progress, run 'netstat -n' from a shell /
command prompt and look for ESTABLISHED connections between client and
server.  You should see the local IP address as part of the output,
which will give you a reasonable idea what it's bound to.

                - Peter

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to