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

Subject: Re: cipe tunnel doesn't start automatically
From: "Nico Flemming" <nf,AT,ventas,DOT,de>
Date: Thu, 28 Nov 2002 11:03:44 +0100
In-reply-to: <0pvqrukkl96p03l86b66rcidj3i701lpk6@4ax.com>

Hi Jason,

thank you for your reply. But the problem that we have is that
the internet connection is no flatrate. So we dont want the internet
connection to be online the whole day, just when someone wants
to access the remote network.

Regards,
Nico Flemming

----- Original Message -----
From: "Jason Woods" <emonk,AT,novust,DOT,com>
To: "Nico Flemming" <nf,AT,ventas,DOT,de>
Cc: <cipe-l,AT,inka,DOT,de>
Sent: Thursday, November 28, 2002 10:26 AM
Subject: Re: cipe tunnel doesn't start automatically

> That sounds like a problem I had when I first started using CIPE (Linux
> only installations).  I have a program that pings all CIPE tunnels every 2
> minutes, and the problems went away.  Before I tried the ping program, the
> link would have to initialize if it had been unused for awhile (even with
> ping set in the options file).  All the program does is ping a set of
> sites (well, IPs), and it is run from cron.  It also gives a nice log file
> status of your link ping times and packet loss (mysql logging also
> available via program).
>
> If you want to the program I wrote, I can post a current copy of it on my
> web site.  Try it, as it might work good for you also.
>
> v2.03 of pingchk utility:
> http://www.newsnot.com/~emonk/files/pingchk-2.03.tgz
>
> Nico Flemming wrote:
> >
> > Hi,
> >
> > I have a CIPE Tunnel between to Dial-In Linux Server with static
> > ip adresses.
> >
> > The problem: If the tunnel ist down and someone tries to connect
> > to the remote net, the cipe tunnel doesn't start automatically, You
> > first have to ping the ptp addr:
> >
> > Server A: 192.168.10.1
> > Gateway A:  1.100.15.1
> > |
> > | (internet)
> > |
> > Gateway B: 1.100.15.2
> > Server B: 192.168.11.1
> >
> > So if the tunnel is down and someone tries to ping server A from
> > server B the tunnel doesnt start, it only start when i ping Gateway A
> > from Server B - or Gateway B from Server A.
> >
> > Here is my configuration:
> >
> > // --- CIPE-Configuration of  Gateway A -----------
> > //
> > # IP address of the CIPE device
> > ipaddr           1.100.15.1
> > # IP address of the peer device (i.e. the CIPE device on the other end).
> > ptpaddr          1.100.15.2
> > # IP adress of the local device
> > me               145.253.203.113:8105
> > # IP adress of the remote device
> > peer             217.110.152.210:8105
> > # The link key.
> > key              [.....]
> > # Dynamic key lifetime in seconds
> > tokey            60
> > # Key exchange timestamp timeout
> > tokxts           30
> >
> > // --- CIPE-Configuration of Gateway B --------
> > //
> > # IP address of the CIPE device
> > ipaddr           1.100.15.2
> > # IP address of the peer device (i.e. the CIPE de
> > ptpaddr          1.100.15.1
> > # IP adress of the local device
> > me               217.110.152.210:8105
> > # IP adress of the remote device
> > peer             145.253.203.113:8105
> > # The link key.
> > key              [...]
> > # Dynamic key lifetime in seconds
> > tokey            60
> > # Key exchange timestamp timeout
> > tokxts           30
> > maxerr 1000
> >
> > // --- ip-up of Gateway A
> > /sbin/route add -net 192.168.11.0  netmask 255.255.255.0 gw 1.100.15.2
> >
> > // --- ip-up of Gateway B
> > /sbin/route add -net 192.168.10.0  netmask 255.255.255.0 gw 1.100.15.1
> >
> > Both, Server A and Server B have a default router over their Gateways..
> >
> > Has someone an idea what could be wrong? If the cipe tunnel ist up,
> > everything
> > works perfectly!
> >
> > Regards,
> > Nico Flemming
> >
> > --
> > 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:
<URL:http://sites.inka.de/~bigred/devel/cipe.html>
>
> --
> Jason Woods
>
> emonk{at}newsnot.com
> http://www.newsnot.com/~emonk
>
> If you look hard enough, and paraphrase a bit, there is
> probably a Nostradamus quatrain that foretold of this email.
>
>





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