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

Subject: RE: newbie in trouble with pkcipe on linux
From: Mikko Pasanen <miapasan,AT,cs,DOT,uku,DOT,fi>
Date: Thu, 12 Sep 2002 14:25:59 +0200
In-reply-to: <002701c25a4d$bbb88950$d100010a@avco>

        Ok, this was very informative thanks, but still the problem stays
so these are the config files, problem stays and if i use plain ciped-cb
it works, but i really would like to get the pkcipe to work ...

jupiter:
-----BEGIN PUBLIC KEY-----
-----END PUBLIC KEY-----
ipaddr 10.0.0.12
ptpaddr 10.0.0.11
ping 10
dynip

deimos:
-----BEGIN PUBLIC KEY-----
-----END PUBLIC KEY-----
ipaddr  10.0.0.11
ptpaddr 10.0.0.12
ping 10
dynip

        I initiate connection from jupiter (Which is behind masq firewall)
to deimos, as pkcipe -E -c deimos:port and i get response as:

connect to deimos
starting /usr/local/sbin/ciped-cb for peer deimos

this is the log from the deimos:

Sep 12 15:21:07 deimos pkcipe[23596]: connect from jupiter
Sep 12 15:21:07 deimos pkcipe[23596]: starting /usr/local/sbin/ciped-cb
for peer jupiter
Sep 12 15:21:07 deimos kernel: cipcb: read_lock(&tasklist_lock) at
../cipe/device.c:216
Sep 12 15:21:07 deimos kernel: cipcb: read_unlock(&tasklist_lock) at
../cipe/device.c:220
Sep 12 15:21:27 deimos ciped-cb[23598]: keepalive timeout

and in the jupiter logs i find :

Sep 12 15:26:11 jupiter ciped-cb[13682]: kxchg: recv: Connection refused

(clocks are not in sync ;)

On Thu, 12 Sep 2002, Mark Smith wrote:

> The .info  file distributed with cipe details the pkcipe config file.  All
> of the options go in one file.  Here's mine, as an example:
>
> --- snip ---
> -----BEGIN PUBLIC KEY-----
> <your public key from the other end's public key file>
> -----END PUBLIC KEY-----
> ipaddr 10.0.0.12
> ptpaddr 192.168.0.1
> ping 10
> dynip
> --- end ---
>





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