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

Subject: Re: Static routing problem, Fw: cipe tunnel doesn't start automatically
From: Alan Stern <stern,AT,rowland,DOT,harvard,DOT,edu>
Date: Fri, 6 Dec 2002 16:26:26 +0100
In-reply-to: <006b01c29d03$1e1ec170$298f4e01@ventas.de>

On Fri, 6 Dec 2002, Nico Flemming wrote:

> Server A: 192.168.10.1
>   |
>     eth0: 192.168.10.254
> Gateway A
>     cipcb0: 1.100.15.1
>       |
>       | Internet
>     cipcb0: 1.100.15.2
> Gateway B
>     eth0: 192.168.11.254
> |
> Server B: 192.168.11.1
>
>
> Server A has its default route over Gateway A:
> 0.0.0.0         192.168.10.254  0.0.0.0         UG    0      0        0 eth0
>
> And Server B has its default route over Gateway B:
>
> 0.0.0.0         192.168.11.254  0.0.0.0         UG    0      0        0 eth0
>
> In the /etc/cipe/ip-up from Gateway A is:
> /sbin/route add -net 102.168.11.0  netmask 255.255.255.0 gw 1.100.15.2
>
>
> In the /etc/cipe/ip-up from Gateway B:
> /sbin/route add -net 102.168.10.0  netmask 255.255.255.0 gw 1.100.15.1
>
>
> So. Thats the situation.
> In fact the CIPE tunnel is loaded when the server boots. But if the internet
> connection is dropped and someone from 192.168.11.1 pings 192.168.10.1
> then all packets were dropped and the cipe connection wont be established
> again.
>
> But: If someone pings 1.100.15.1 from 192.168.11.1 then the cipe connection
> will be immediately established.

Do you mean, "the internet connection will be immediately estalished"?
What if someone at 192.168.11.1 tries to ping 192.168.10.1, gets no
response, and then tries to ping 1.100.15.1?  After the first ping fails,
you said, "the cipe connection wont be established again."  This
contradicts your statement that for the second ping, "the cipe connection
will be immediately established."  Which one is correct?

> What is wrong?

Okay, this is puzzling.  Is it possible that one or both of your Gateway
machines is using a cipe option that turns off the link when too many
errors are encountered?  Try making sure that maxerr is set to -1 in your
configuration files.  (That's a long shot, I admit.)

Also have you verified, even when your internet connection is down, that
the cipe link is still connected and the routing tables are set properly?
Sometime when your internet connection is down, try doing
/sbin/ifconfig -a and /sbin/route -n to check.

If this doesn't help, then I give up.  Someone more familiar with cipe
will have to answer your question.

Alan Stern





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