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

Subject: Re: Cipe for Windows
From: "Damion K. Wilson" <dkw,AT,rcm,DOT,bm>
Date: Wed, 18 Oct 2000 03:07:11 +0200
In-reply-to: <200010171247030374.00C02502@mail.sprint.ca>

None. I've never seen that before. It may be that the protocol has changed
slightly and that CIPE-Win32 is placing values in fields that CIPE-1.4.2
doesn't understand anymore. I don't have a Cipe-1.4.x setup anywhere so I
can't reproduce your problem. Can anyone else reproduce this problem ?

DKW

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

On 10/17/00 at 5:17 PM chris wrote:

>Thanks, been going through the protocol description. Here is what happens
on the UNIX side when
>the error condition occurs :  Following an NK_REQ or NK_IND every single
NK_ACK debug message
>says "unknown" followed by a 000000A9 or 000000D4 or similar hex number
with mostly zeroes.
>
>Such as [NK_ACK] unknown 000000D4
>
>Ideas ?
>
>
>
>*********** REPLY SEPARATOR  ***********
>
>On 10/17/00 at 6:07 PM Damion K. Wilson wrote:
>
>>I think so. The driver also takes the option cipe_debug or something like
>>that at load time. Look in the cipe.info documentation file.
>>
>>DKW
>>
>>*********** REPLY SEPARATOR  ***********
>>
>>On 10/17/00 at 4:44 PM chris wrote:
>>
>>>>Try two things: Setup another CIPE-Win32 instance and point it at the
>>first
>>>>and see if the same behaviour occurs. Turn on the logs in CIPE 1.4.2
and
>>>>see what causes it to initiate a key exchange.
>>>
>>>How do I do this ? In /etc/cipe/options ?
>>>
>>>
>>>Chris
>>>kohlhepp,AT,iosphere,DOT,net
>
>
>Chris
>kohlhepp,AT,iosphere,DOT,net





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