There is however a problem on windows platforms.
the ping program does not check the address in the response packet.
more precisely, suppose you ping 1.2.3.4, and you receive a response
from 10.0.0.1. the windows ping problem will say it is receiving a response
from 1.2.3.4 instead of 10.0.0.1. It does not check the ICMP header!
dunno what Linux does, but I'm certain it behaves as the BSD variant
and reports that the response is from 10.0.0.1, which is the correct
way.
At 20:00 02/05/01 -0400, Paul D. Robertson wrote:
>On Wed, 2 May 2001, Ben Nagy wrote:
>
> > I was just testing some strange NAT stuff, and I noticed that both Windows
> > NT4 and Linux (2.2.14) don't seem to care about source IP addresses for
> ICMP
> > echo-replies.
>
>Multi-homed hosts generally answer from the nearest (outbound routing
>wise) interface. If this wasn't the case, the router would have to spoof
>the source IP address of the internal interface on the external interface
>despite the differing MAC addresses. I'm not sure that doesn't present
>more long-term problems...
>
> > Has anyone else noticed this? Is it just me, or is that a bizarre
> > implementation choice? It certainly gave me the absolute "what the
> (*^(&???"
> > heebie-jeebies.
>
>It's a normal implementation choice for multihomed hosts, and I'd be
>surprised if it wasn't covered in the specs somewhere...
>
>Paul
>-----------------------------------------------------------------------------
>Paul D. Robertson "My statements in this message are personal opinions
>[EMAIL PROTECTED] which may have no basis whatsoever in fact."
>
>-
>[To unsubscribe, send mail to [EMAIL PROTECTED] with
>"unsubscribe firewalls" in the body of the message.]
-
[To unsubscribe, send mail to [EMAIL PROTECTED] with
"unsubscribe firewalls" in the body of the message.]
