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
|---------+------------------------------>
| | "Renato Salles" |
| | <rsalles@rsnetservi|
| | ces.com.br> |
| | Sent by: |
| | [email protected]|
| | e |
| | |
| | |
| | 09/15/2003 08:21 PM|
| | Please respond to |
| | rsalles |
| | |
|---------+------------------------------>
>------------------------------------------------------------------------------------------------------------------------------|
| |
| To: [email protected] |
| cc: |
| Subject: Re: CPU Usage CIPE-WIN32 Windows XP |
>------------------------------------------------------------------------------------------------------------------------------|
Mr. bhein:
Please confirm the setup i have here after removing the comments:
<setup>
################
# PEER ONE
################
ptpaddr 192.168.5.102
ipaddr 192.168.5.1
me 0.0.0.0:1734
peer 0.0.0.0:1735
key 00000000010000000002000000000322
ping 10
device cipcb1
dynip 1
maxerr=-1
################
# PEER TWO
################
ptpaddr 192.168.5.103
ipaddr 192.168.5.1
me 0.0.0.0:1736
peer 0.0.0.0:1737
key 00000000010000000002000000000322
ping 10
device cipcb2
dynip 1
maxerr=-1
################
# PEER THREE
################
> Windows 2000:
Local IP Address 0.0.0.0 port 1737
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.
</setup>
This way i have a minimal chance to tell you what could be the probable
cause of all this folish behaviour at the Win2k machine.
I suppose this is the setup you used in the past to stablish a VPN link
with 3 peer's, using 2 linux boxes and one Win2k machine. If i'm wrong,
please correct the lines explained above. BTW, where is the WinXP
computer?
[email protected] disse:
> To respond to a slightly old post, which I just read on the
> internet.......
>
>
>
> I've installed CIPE for win32 on my laptop (win2k professional SP4) and
on
> a freshly loaded Win2kServer. Both are Pentium boxes. The problem is that
>
> 1. upon boot, the CIPE device has yet to work without a service reset
> 2. sometimes after the service has been restarted, its CPU consumption
> skyrockets and remains there, and the system becomes unusable.
> 3. if the ethernet link state goes down (And back up) then the CIPE
> devices
> sometimes becomes unstable and produces unpredictable results. For
> instance
> full CPU consumption, and even BSOD.
>
>>From what I can tell, the problems exist within in the service
>> cipsvr.exe.
> In my humble understanding of NT Services, I know that some services
> depend
> on other services. Perhaps CIPE fails to start because another service
> that
> it needs hasn't yet been started when it is activated. As for the
100%CPU,
> I can't imagine what would cause this. I'm not a yoda programmer, so I
> won't presume to know the cause, or solution.
>
>
> Snippets of my configurations follow. I used grep so that each config
file
> is prefixed with the filename.
>
###############cut###############
>
>
> --Brad
>
Best Regards,
RSalles
--
Renato Salles
Ger.Geral
RSNetServices
--
Message sent by the [email protected] mailing list.
Unsubscribe: mail [email protected], "unsubscribe cipe-l" in body
Other commands available with "help" in body to the same address.
CIPE info and list archive: <URL:
http://sites.inka.de/~bigred/devel/cipe.html>
--
Message sent by the [email protected] mailing list.
Unsubscribe: mail [email protected], "unsubscribe cipe-l" in body
Other commands available with "help" in body to the same address.
CIPE info and list archive: <URL:http://sites.inka.de/~bigred/devel/cipe.html>
lmpx.com only provides a reader for public news (NNTP) servers. It is not
affiliated with the servers or forums shown here and is not responsible for
the content of articles, which is written by their respective authors.