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

Subject: Static routing problem, Fw: cipe tunnel doesn't start automatically
From: "Nico Flemming" <nf,AT,ventas,DOT,de>
Date: Thu, 5 Dec 2002 10:11:19 +0100

Hi,

I want to place a static route over a cipe connection which is not
always up:

> 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 Gateway A must have a static route to Server B over Gateway B. If
the cipe-link is established this is no problem. But what should I do if the
cipe connection is down?

I can not place a route over a none existing device. So a user on Server A
has no chance to establish the cipe connection when pinging Server B.

Is there a solution for this problem? The ip-up is not very useful for this
matter,
because it will be startet after the link is established.

This commands fails on Gateway A if the cipe link is down:
route add -net 192.168.11.0 netmask 255.255.255.0 gw 1.100.15.2

To force the cipe link to be up the whole day is no solution because the
internet connection is not flat and should only be established on demand.

Regards,
Nico Flemming

----- Original Message -----
From: "Nico Flemming" <nf,AT,ventas,DOT,de>
To: <cipe-l,AT,inka,DOT,de>
Sent: Thursday, November 28, 2002 9:40 AM
Subject: cipe tunnel doesn't start automatically

> 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
>





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