<< | Thread Index | >> ]    [ << | Date Index | >> ]

Subject: Re: Final resort CIPE routing question
From: Sven Schulthei▀ <schulti,AT,discus,DOT,wh,DOT,uni-stuttgart,DOT,de>
Date: Wed, 10 Jan 2001 20:28:08 +0100
In-reply-to: <003101c07a48$2d0bb5b0$be01a8c0@trollslayer>

Your routing tables look good now. Your Cipe-Tunnel works.

> Tcpdump output on crux of the ping 192.168.0.1 on callisto gives :
> 
> [root@crux domme]# tcpdump -i cipcb0
> Kernel filter, protocol ALL, datagram packet socket
> tcpdump: listening on cipcb0
> 10:45:42.299163 < 192.168.1.252 > 192.168.0.1: icmp: echo request
> 10:45:42.299402 > 192.168.0.252 > 192.168.1.252: icmp: host 192.168.0.1
> unreachable [tos 0xc0]
> 10:45:43.299216 < 192.168.1.252 > 192.168.0.1: icmp: echo request
> 10:45:43.299432 > 192.168.0.252 > 192.168.1.252: icmp: host 192.168.0.1
> unreachable [tos 0xc0]
> 10:45:44.299458 < 192.168.1.252 > 192.168.0.1: icmp: echo request

192.168.1.252 sends the ping through the tunnel, and it arrives at
192.168.0.252.
192.168.0.252 cannot find 192.168.0.1. 
Maybe you should check your firewall rules to your internal nets. 
Do you have rules that allow traffic from the other subnet on eth1?

Sven





<< | Thread Index | >> ]    [ << | Date Index | >> ]