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

To: James Knott <james.knott,AT,rogers,DOT,com>, CIPE <cipe-l,AT,inka,DOT,de>
Subject: Re: Setting up CIPE on XP
From: Phil Scarratt <fil,AT,draxsen,DOT,com>
Date: Wed, 13 Aug 2003 12:11:34 +1000
Organization: Draxsen Technologies

This is really getting confusing. If I get a chance I'll drop into a place that has XP and see if there is anything special or whatever about the setup.

Have you tried playing around with the metric's of the 192.168.2. routes? My metrix setting is automatic and they all appear as 1.

I just tried setting NONE for cipher on Windows - it does NOT work with cipcbx on linux end. The log reports errors of "got bogus length". This makes sense of course, as the linux end is still expecting cipher'd data (and I can't remember for the life of me how I managed to get linux cipe to not encrypt). However, the confusing part is that you should still see something with ethereal or tcpdump. In any case, it might be worth a try going back to the drawing board and setting the cipher to blowfish (or whatever) and using a really simple key on both ends (eg 123456789abcdef123456789...etc) so that it's easy to type in without any "invisible" characters.

A whole lot of messages as per below in the firewall's log means the communication is working:
Aug 13 11:52:39 iserve kernel: cipcb1: cipe_recvmsg
Aug 13 11:52:59 iserve kernel: cipcb1: cipe_sendmsg
Aug 13 11:52:59 iserve kernel: cipcb1: setkey
Aug 13 11:52:59 iserve kernel: cipcb1: cipe_recvmsg
Aug 13 11:52:59 iserve kernel: cipcb1: setkey
Aug 13 11:52:59 iserve kernel: cipcb1: cipe_recvmsg
Aug 13 11:52:59 iserve kernel: cipcb1: cipe_sendmsg
Aug 13 11:52:59 iserve kernel: cipcb1: cipe_recvmsg


What version of cipe and cipe-win32 are you running? From experience it doesn't really matter but it's worth checking.

Fil


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