From owner-freebsd-questions@FreeBSD.ORG Mon Sep 3 22:13:43 2012 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 0AC5C1065670 for ; Mon, 3 Sep 2012 22:13:43 +0000 (UTC) (envelope-from perryh@pluto.rain.com) Received: from agora.rdrop.com (agora.rdrop.com [IPv6:2607:f678:1010::34]) by mx1.freebsd.org (Postfix) with ESMTP id D99068FC12 for ; Mon, 3 Sep 2012 22:13:42 +0000 (UTC) Received: from agora.rdrop.com (66@localhost [127.0.0.1]) by agora.rdrop.com (8.13.1/8.12.7) with ESMTP id q83MDfQq082729 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Mon, 3 Sep 2012 15:13:42 -0700 (PDT) (envelope-from perryh@pluto.rain.com) Received: (from uucp@localhost) by agora.rdrop.com (8.13.1/8.14.2/Submit) with UUCP id q83MDfrL082728; Mon, 3 Sep 2012 15:13:41 -0700 (PDT) (envelope-from perryh@pluto.rain.com) Received: from fbsd81 ([192.168.200.81]) by pluto.rain.com (4.1/SMI-4.1-pluto-M2060407) id AA06031; Mon, 3 Sep 12 15:01:33 PDT Date: Mon, 03 Sep 2012 22:01:26 -0700 From: perryh@pluto.rain.com To: vas@mpeks.tomsk.su Message-Id: <50458b26.tmHtgZn7IH/7r2In%perryh@pluto.rain.com> References: <20120903030217.GA79339@admin.sibptus.tomsk.ru> <50443766.4020705@boosten.org> <5044b978.qFhU35CVsU8J/nET%perryh@pluto.rain.com> <20120903072449.GA92658@admin.sibptus.tomsk.ru> In-Reply-To: <20120903072449.GA92658@admin.sibptus.tomsk.ru> User-Agent: nail 11.25 7/29/05 Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Cc: freebsd-questions@freebsd.org Subject: Re: Sharing COM ports to Windows hosts X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 03 Sep 2012 22:13:43 -0000 Victor Sudakov wrote: > In fact, the question is whether there is a standards compliant > (not written for some proprietary hardware terminal server > protocol) driver for Windows. Not exactly a FreeBSD question, > I know :) Finding a Windows driver that will work with an existing FreeBSD program is certainly one possible approach. Another, which I understood to be the intent of the original inquiry, is finding a FreeBSD solution that will work with an existing Windows driver. There's surely no reason why a FreeBSD system _can't_ support a protocol originally developed by a hardware terminal server manufacturer, as vpnc does for the Cisco VPN protocol.