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

Subject: Re: Cipe for Windows
From: "Damion K. Wilson" <dkw,AT,rcm,DOT,bm>
Date: Tue, 17 Oct 2000 22:32:58 +0200
In-reply-to: <200010171247030374.00C02502@mail.sprint.ca>

Let me know what you get in DebugView. If there is a key exchange loop,
you'll see it


*********** REPLY SEPARATOR  ***********

On 10/17/00 at 2:19 PM chris wrote:

>Hi Damion,
>I set the timeout on the Windows end to 999 seconds, but the symptoms
persist. As always, I can 
>get 4 or 5 pings out over the tunnel, then they start timing out and
that's it. If I wait for a while, I can 
>get another 4 or 5 packets out, but it always hangs. If I let it ping
continuously, I get 4 or 5 packets 
>once every 50 or so packets. In /var/log messages the same set of entries
repeat : setkey, cipe_recvmsg, 
>cipe_recvmsg, cipe_sendmsg. 
>I guess I'll try CIPE 1.3.0.
>>Yes, I have but only several versions ago and, even then, only with
>>CIPE-Win32 instance (i.e., I have never had it happen against Cipe 1.3.0
>>Try setting the Key timeout value in the CIPE-Win32 control panel applet
>>something very high.
>>Also, if possible, try using the same CIPE-Win32 instance against a CIPE
>>1.3.0 instance so we will know if it's something new with Cipe 1.4.x.
>>I am actually rewriting CIPE-Win32 right now so if we can figure out what
>>causes this before I'm done, I should be able to incorporate the fix or
>>workaround in the new release.
>>*********** REPLY SEPARATOR  ***********
>>On 10/17/00 at 12:47 PM chris wrote:
>>>Hi Damion,
>>>I've been trying to get your CIPE port for Windows to work with my linux
>>CIPE. The latter is version 1.4.2
>>>and the seems to be able to communicate with your Windows port just
>>the cipe device is allocated,
>>>opened, keys set. After the first few or so packets of traffic, the link
>>dies and both daemons enter an infinite
>>>loop of "setkey" commands. Have you seen this before ? Any suggestions ?

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