Re: Ping problem

Looks like a routing or firewall problem:

192.168.1.248 -> 192.168.10.1: ping reply returns to the local cipe
interface but is not seen by the ethernet interface..(?)
192.168.10.1 -> 192.168.1.248: ping request reaches the cipe interface on
248 but reply fails.
So, there must be a problem between the cipe interface and the ethernet
interface on 192.168.1.248, related to routing or the firewall blocks ICMP
reply packets..


Hans Steegers

-----Original Message-----
From: David A. Osborn <[email protected]>
To: [email protected] <[email protected]>
Date: Sunday, August 31, 2003 6:35 PM
Subject: Ping problem


I am still having issues getting CIPE working.  It looks like it is close,
but my ping is acting a little weird.  The two machines have Ip address
192.168.10.1 and 192.168.1.248, I do a "tcpdump -i cipcb0"  on both machines
and do a ping and I get the following:

ping from 192.168.1.248 to 192.168.10.1:
both tcpdumps display:
192.168.1.248 > 192.168.10.1: icmp: echo request (DF)
192.168.10.1 > 192.168.1.248 icmp: echo reply

This would tell me that the ping should be completing fine, but the actual
Ping command fails on every attempt.

ping from 192.168.10.1 to 192.168.1.248
both tcpdumps display
192.168.10.1 > 192.168.1.248: icmp: echo request (DF)

neither display the echo reply and of course the Ping fails.

Any ideas?




--
Message sent by the [email protected] mailing list.
Unsubscribe: mail [email protected], "unsubscribe cipe-l" in body
Other commands available with "help" in body to the same address.
CIPE info and list archive: <URL:http://sites.inka.de/~bigred/devel/cipe.html>