On Thu, Nov 29, 2001 at 06:01:04PM +0500, Ahsan Ali wrote:
> > For TCP, that is what is always used by default when creating an
> > outbound connection. For incoming connections, the machine will of
> > course reply using the IP address the connection came in on. And a
> > program can always request to use a specific address if it wants to.
> >
> > I am not sure where you see a problem.
>
> What I am saying is that if you have (for instance) 192.168.0.0/24 as a
> network.
>
> Interface A has the IP 192.168.0.10 with a netmask of 255.255.255.0 (/24)
> Alias A:1 has the IP 192.168.0.11 with a netmask of 255.255.255.255 (/32)
>
> Now Host B (192.168.0.20 mask 255.255.255.0) tries to access Alias A:1 which
> is 192.168.0.11/32 so B sends to A:1 which it (correctly) assumes to be on
> its own network, Alias A:1 cannot however reach B without sending the data
> to its configured gateway. If routing is enabled on this host then it may be
> able to send the reply routed through Interface A only...
Hmmm? Routing is always enabled if you plan on talking to any other
machines at all. But all of this is a non-issue. The selection of a
route for a packet has _nothing_ to do with the source address, only
the destination. How a packet finds its way to 192.168.0.20 is the
same no matter what the source address is. 192.168.0.20 is local to
the interface A, so it is sent directly to B.
--
Crist J. Clark | [EMAIL PROTECTED]
| [EMAIL PROTECTED]
http://people.freebsd.org/~cjc/ | [EMAIL PROTECTED]
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-net" in the body of the message
