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

Subject: Re: Frame errors with Cipe-Win32
From: "Ville Voipio" <ville.voipio,AT,iki,DOT,fi>
Date: Fri, 3 Nov 2000 23:41:40 +0100
In-reply-to: <Pine.OSF.4.10.10011040001440.9505-100000@kosh.hut.fi>

Oh, just one more clue:

I tried again with Cipe-1.4.3 and Cipe-Win32. I logged the debug information
from the NT side. I get the following log when I start the cipe service
(driver is already running):

00000003 37.94024549 [226] Successfully started CIPE daemon v0.125
00000004 37.94048016 [226] Auto key exchange will start immediately
00000005 37.94085563 [226] Shared memory segment is 65552 bytes long
00000006 37.94201639 [226] Detected device [CIPE1]
00000007 37.94264915 [226] [CIPE1] PTP Search of [e165a8c0] yielded [0]
00000008 37.94292740 [226] Adding [CIPE1] [KPat]
00000009 37.94322828 [226] CIPE1 Startup script is []
00000010 37.94347132 [226] CIPE1 Shutdown script is []
00000011 37.94523970 [226] CIPE1 reading static Key from registry
00000012 37.94696534 [226] CIPE1 is using encryption
00000013 37.94717067 [226] CIPE1 key exchange timeout=600000 seconds
00000014 37.94736260 [226] CIPE1 key exchange limit=10000 packets
00000015 37.95106279 [226] CIPE1 opened socket [164]
00000016 41.94866416 [226] CIPE driver already running
00000017 41.94980565 [CIPE1] Querying [OID_GEN_SUPPORTED_LIST]
00000018 41.94984504 [CIPE1] Querying [OID_GEN_SUPPORTED_LIST]
00000019 41.94992885 [CIPE1] [OID_SERVICE_START_SIGNAL]
00000020 41.95016184 [226] Opened [\\.\CIPE1] for [CIPE1] = [Yes]
00000021 41.96678210 [226] [CIPE1:KPat] Assigned MAC address =
[8:0:58:0:0:2]
00000022 127.22959113 [226] [CIPE1] PTP Search of [e165a8c0] yielded
[342a58]
00000023 127.22984004 [226] CIPE1 synthesized ARP reply from [c0a865e1]

Now, what draws my attention is something funny on last two lines (they
emerged when I tried to ping the other end of the tunnel). The IP addresses
on these two lines are in different order. Line 22 shows that [e165a8c0]
(i.e. 225.101.168.192) is being looked for. The next row talks about
[c0a865e1] (i.e. 192.168.101.225). Is this just a printing problem, or is it
really so that the IP addresses are screwed along the process?

Just guessing.

- Ville





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