"'Damion Wilson'" <dwilson,AT,ibl,DOT,bm>,<tparker,AT,netspace,DOT,net,DOT,au>|
RE: CIPE-Win32: communication breakdown|
"Michael Clarke" <mclarke,AT,timetra,DOT,com>|
Fri, 13 Jun 2003 15:38:12 +0100|
It could also be the CIPE driver's queues becoming corrupted bug (no
KeRaiseIrql during IRP_MJ_READs). I'm assuming pings don't work - if
small pings still work after the breakdown, then that would be the MTU
From: owner-cipe-l,AT,inka,DOT,de [mailto:owner-cipe-l,AT,inka,DOT,de On
Sent: 13 June 2003 15:14
Subject: Re: CIPE-Win32: communication breakdown
It might actually be the MTU issue instead. Check the mailing list
for the "fix". Otherwise I or one of the other guys can send you the
registry editor instructions
On Thursday 12 June 2003 07:30 pm, you wrote:
> > If you read Christof's message of June 6, he asserts that there is a
> > negotiation problem over less reliable links due to CIPE
> > 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
> cipe tunnel from a windows server to a linux client. Every now and
> the tunnel dies and I can't get it to come back. I guess restarting
> win32 service might work, but I generally use the opportunity to
> entirely. Nothing I do to the linux end seems to be able to
> 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).
> This email was sent from Netspace Webmail: http://www.netspace.net.au
Message sent by the cipe-l,AT,inka,DOT,de mailing list.
Unsubscribe: mail majordomo,AT,inka,DOT,de, "unsubscribe cipe-l" in body
Other commands available with "help" in body to the same address.
CIPE info and list archive: