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

To: cipe-l,AT,inka,DOT,de
Subject: Re: CPU Usage CIPE-WIN32 Windows XP
From: "Renato Salles" <rsalles,AT,rsnetservices,DOT,com,DOT,br>
Date: Tue, 16 Sep 2003 13:11:31 -0300 (BRT)
Importance: Normal
In-reply-to: <OFD3FEA4BF.EF2618D7-ON85256DA3.004469CD@bmc-pos.com>
References: <OFD3FEA4BF.EF2618D7-ON85256DA3.004469CD@bmc-pos.com>
Reply-to: rsalles,AT,rsnetservices,DOT,com,DOT,br

Hello, Brad,

bhein,AT,bmc-pos,DOT,com disse:

So, let's try to figure out what could be happen with those peers:

>
> The config files match.
>
> As listed below, peers two and three are running when the problem occurs.
> Peer one was another computer that isn't being used in my lab here at the
> office.
>
>
> --Brad
> <setup>
>
###########PEER ONE SKIPED#############
> ################
> # PEER TWO
> ################
> ptpaddr         192.168.5.103
> ipaddr          192.168.5.1
> me              0.0.0.0:1736
> peer            0.0.0.0:1737
# ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
# This is a cause of a loop between ports 1736 & 1737
# When you define 0.0.0.0 as peer, you difine your own address too.
# because 0.0.0.0 stays as "all addresses". Locally configured like
# that is OK, but as peer parameter is a call for problem.
# Use: FQDN:1737 or IP ADDRESS:1737
> key             00000000010000000002000000000322
> ping 10
> device cipcb2
# Why, how many cipcbx interfaces have you running at this moment?
# Why not cipcb0 if it's the first/unique interface?
> dynip 1
> maxerr=-1
######********#######
# Missing Parameters (i have here those configured and let's insert them
# just for a "doesn't hurt" procedure: it can be removed later if it has
# proved not necessary:
# ONBOOT parameter as "yes" or "no", define as you want, but use
# "ifconfig cipcbn up" to get the link running.
# USERCTL=no (this is the more common case).
# TYPE=CIPE ( it is RH tou're running isn't it?). As this is default, let
# as is.
# TUNNELDEV=ethx # In the case you have 2/more interfaces - optional.
#
######********#######

> ################
> # PEER THREE
> ################
>> Windows 2000:
> Local IP Address 0.0.0.0 port 1737

# Where is the "Local PTP address" parameter?
# This is the ip address of the VPN interface.
# You better fill this before continue.

> Peer IP Address my.outside.IP.addrses 1736
> Peer PTP Address 192.168.5.1
>> I'm using a 32-byte key, blowfish, and a 600 second timeout value.
# I hope is exactly the same as above in the "ket" parameter for peer 2
>
> </setup>
>

###########cut###########

Try these corrections and let me know the results.

Best Regards,

RSalles

-- 
Renato Salles
Ger.Geral
RSNetServices


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