From: Abraham Iglesias (abraham.iglesiasgenaker.net)
Date: Mon Nov 08 2004 - 06:08:39 CST

• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

They do not correspond to the internal IP addresses of the gw...

I have tried both:
ping -I 172.16.14.15 10.10.28.31

from the gw itself

and

ping 10.10.28.31 from a machine within the 172.16.14.0/24 network

I have my filter turned off, and the gwB filter pings to the external
interface (gwB Ip address). Is it possible that the gwB filters the
pings to the 10.10.28.31 machine?

Thanks for any idea ;)

/bram

Hakan Olsson wrote:

> On Mon, 8 Nov 2004, Abraham Iglesias wrote:
> ...
>
>> I ping from 172.16.14.5 to 10.10.28.31 and I can see the echo request
>> encapsulated going out,
>> but I can't see any echo reply back...
>> Can anyone help me?
>
>
> If any of those IPs are the internal IPs of the gateway machines, then
> this is expected behaviour (as the gateway will respond from it's
> external IP, which is not part of the tunnel).
>
> Or, if both these are internal addresses, it is likely a routing
> problem (it could also be a problem with your filters).
>
> You need to track the 'ping' packets every step of the way to find
> exactly where it fails. When you do, you'll likely be able to see why
> as well.
>
> /H

• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]