| To: | tparker,AT,netspace,DOT,net,DOT,au |
| Subject: | Re: CIPE-Win32: communication breakdown |
| From: | Damion Wilson <dwilson,AT,ibl,DOT,bm> |
| Date: | Fri, 13 Jun 2003 11:14:17 -0300 |
| Cc: | cipe-l,AT,inka,DOT,de |
| In-reply-to: | <1055457057.3ee8ff214eab8@webmail.netspace.net.au> |
| References: | <1055457057.3ee8ff214eab8@webmail.netspace.net.au> |
It might actually be the MTU issue instead. Check the mailing list archives for the "fix". Otherwise I or one of the other guys can send you the registry editor instructions DKW On Thursday 12 June 2003 07:30 pm, you wrote: > Hi, > > > If you read Christof's message of June 6, he asserts that there is a key > > negotiation problem over less reliable links due to CIPE invalidating the > > key before the NK_ACK and CIPE-Win32 continuing to use the key until > > the NK_ACK. > > I see a problem like this quite often. I play mp3s across 802.11 via a > cipe tunnel from a windows server to a linux client. Every now and then > the tunnel dies and I can't get it to come back. I guess restarting the > win32 service might work, but I generally use the opportunity to reboot > entirely. Nothing I do to the linux end seems to be able to re-establish > the tunnel. > > This key exchange problem might be what I'm seeing (since the link is > fairly busy streaming music and unreliable being 802.11). > > Cheers, > Tom > > > > ------------------------------------------------------------ > This email was sent from Netspace Webmail: http://www.netspace.net.au