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

Subject: Re: Frame errors with Cipe-Win32
From: "Damion K. Wilson" <dkw,AT,rcm,DOT,bm>
Date: Sun, 5 Nov 2000 19:45:48 +0100
In-reply-to: <Pine.OSF.4.10.10011041317490.7547-100000@kosh.hut.fi>

I guess that an SSH (I'm presuming a TCP-based "session" ) approach would
suffer from the same timing issues as PPP over SSH. Secondly, "gluing" an
SSH session/daemon to an emulated Ethernet interface would probably suffer
from performance issues as SSH is not really designed for that.

I am just guessing, though :-)

TUN/TAP does provide a standalone pseudo-Ethernet  adapter for Solaris and
Linux. The rewrite of CIPE-Win23 also will provide a such an adapter for
Windows. I'm sure someone will eventually attempt to do just what you've


*********** REPLY SEPARATOR  ***********

On 11/5/00 at 12:01 AM Les Mikesell wrote:

>----- Original Message -----
>From: "Damion K. Wilson" <dkw,AT,rcm,DOT,bm>
>To: <vvoipio,AT,cc,DOT,hut,DOT,fi>
>Cc: <cipe-l,AT,inka,DOT,de>
>Sent: Saturday, November 04, 2000 2:08 PM
>Subject: Re: Frame errors with Cipe-Win32
>> Yes, I know about the VPN/Vendor issues. Earlier this year, I embarked
>> journey of discovery through the land of VPN solutions and standards. I
>> quickly found out that everything has problems. I gravitated to CIPE
>> because the engineering seemed sound (complete with explanations, thanks
>> Olaf) and it was simple. I looked at TUN/TAP too, but it's more
>> complicated.
>> I only wrote CIPE-Win32 because I needed to support road warriors.
>I'm kind of surprised that there isn't an ssh port forwarding | net
>solution where the net interface doesn't provide any error correction
>or retries.  CIPE with blowfish seems to be the minimalist approach
>that works, but why isn't there a TAP that can be glued portably to
>the end of ssh port forwarding along with passing any needed
>ad hoc route commands over the command line?
>   Les Mikesell
>      lesmikesell,AT,home,DOT,com

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