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

To: <cipe-l,AT,inka,DOT,de>
Subject: Re: Automatic ruleset generation with CIPE
From: "Hans Steegers" <hsx,AT,dds,DOT,nl>
Date: Mon, 8 Sep 2003 11:04:03 +0200
Reply-to: "Hans Steegers" <steegers,AT,steegers,DOT,nl>

Jan Frederik,

CIPE executes an if-up script when it comes up and an if-down
script when it goes down (if specified in the options file).

The following is available in the script
# Arguments:
#  $1 interface     the CIPE interface
#  $2 myaddr        our UDP address
#  $3 daemon-pid    the daemon's process ID
#  $4 local         IP address of our CIPE device
#  $5 remote        IP address of the remote CIPE device
#  $6 arg           argument supplied via options

It is all described in the documentation. Sample scripts
are in the sample directory. You can export the values in
variables and use them in whatever-you-need-them-for.

Hans Steegers

-----Original Message-----
From: Jan Frederik Pielhau <J.Pielhau,AT,inuit,DOT,de>
To: cipe-l,AT,inka,DOT,de <cipe-l,AT,inka,DOT,de>
Date: Monday, September 08, 2003 10:42 AM
Subject: Automatic ruleset generation with CIPE

>Hi Cipe-List,
>i would like to connect a static-IP Net with a dynamic-IP Net.
>Both Cipe-Gateways are SuSe-Linux based.
>The Question is: how can i insert the needed rules into both chains of
>both Cipe-Gateways dynamically?
>And how can i delete them, when the Cipe-Interface gets down?
>What about the Routing-Entries, are they deleted when the Cipe-Interface
>gets down?
>Thanks for any answers, i was successful with the Cipe Implementation on
>fli4l <http://www.fli4l.de> and would now like to use "the real" Linux
>Jan Pielhau
>Message sent by the cipe-l,AT,inka,DOT,de mailing list.
>Unsubscribe: mail majordomo,AT,inka,DOT,de, "unsubscribe cipe-l" in body
>Other commands available with "help" in body to the same address.
>CIPE info and list archive:

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