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

Subject: Re: CIPE 1.5.2 Linux - Strange behaviour :-(((
From: "Les Mikesell" <lesmikesell,AT,home,DOT,com>
Date: Tue, 25 Sep 2001 04:00:32 +0200
In-reply-to: <u07uqtg6md6qnak12kviqnlj3bguq4ga79@4ax.com>

Are you perhaps starting cipe with a RedHat script that
pulls most of the option settings from files under
/etc/sysconfig?    If I use that version, I always change
it to start with '-o /etc/cipe/options' instead of the
original command line.

   Les Mikesell

----- Original Message ----- 
From: "RoMaN SoFt / LLFB" <roman,AT,madrid,DOT,com>
To: <cipe-l,AT,inka,DOT,de>
Sent: Monday, September 24, 2001 7:06 AM
Subject: CIPE 1.5.2 Linux - Strange behaviour :-(((


 I posted some time ago about problems establishing a CIPE link
between a 2.4.4 Linux and a 2.2.19 Linux, both with 1.5.2 version of
Cipe. Well, those problems were NOT solved, but I temporarily leave it
'cause I was too much busy. Now I re-take cipe stuff and I want to
solve it.

 I'm going to sumarize because all scheme is difficult (and hard) to

 The main problem is that CIPE link works on only one way but not in
the other way. I mean, if the hosts running CIPE are named A and B, I
can send encapsulated (over cipcb0) packets from A to B, but NOT from
B to A. I've looked routes, firewall rules, etc and all seems to be
ok: path from B to A should be perfectly ok. Indeed it seems A and B
are "speaking" CIPE protocol ok. But if I examine logs when trying to
send to a IP attached to the CIPE dev  I can see Cipe is sending
packets to the wrong IP !!!!!! This "strange" IP results to be I don't know where the hell is this IP coming from, because I
haven't not entered in any config file (/etc/cipe/options or similar).
I'm totally lost! This is confusing.

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