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

Subject: Re: cipe doesn't ask the DNS
From: "Christopher J. Oliver" <cjo,AT,sympatico,DOT,ca>
Date: Sun, 28 Jul 2002 17:57:01 +0200
In-reply-to: <Pine.LNX.4.44.0207281029350.11861-100000@bluebell.marzen.de>

Hi,

Since your carriers are both dynamic, try the following settings in your 
options file:

dynip 1
maxerr 8
tokxts 60
ping 60
toping 180
cttl 64

Let us know if this works.

Cheers,

Chris

At 10:35 AM 28/07/2002 +0200, you wrote:
>I have cipe 1.5.4 and both my machine and the partner machine have
>dynamic addresses. Address changes of the other machine are not always
>detected. When I then ping the other machine then I see with tcpdump
>that the udp packets go to the other's old address. A nslookup returns
>the new address, so there are no DNS-related problems.
>
>A restart of ciped solves the problem, but then the interface is doen
>for a short time and tcp-connections are interrupted.
>
>How can I force cipe to do a nslookup from time to time, so address
>changes are always detected?
>
>-------------------------------------------------------
>device cipcb1
>
># the peer's IP address
>ptpaddr         aaa.bbb.ccc.dd
>
># our CIPE device's IP address
>#ipaddr          172.16.0.2
>ipaddr          aaa.bbb.ccc.ee
>
># my UDP address. Note: if you set port 0 here, the system will pick
># one and tell it to you via the ip-up script. Same holds for IP
># 0.0.0.0.
>me              0.0.0.0:20002
>
># ...and the UDP address we connect to. Of course no wildcards here.
>peer            bla.fasel.dynamic.moepx.de:20002
>
># The static key. Keep this file secret!
># The key is 128 bits in hexadecimal notation.
>key             abababababababababababababababab
>
>checksum
>dynip 1
>ping 300
>toping 900
>
>mtu    1400
>maxerr  -1





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