Date: Mon, 03 Sep 2012 22:01:26 -0700 From: perryh@pluto.rain.com To: vas@mpeks.tomsk.su Cc: freebsd-questions@freebsd.org Subject: Re: Sharing COM ports to Windows hosts Message-ID: <50458b26.tmHtgZn7IH/7r2In%perryh@pluto.rain.com> In-Reply-To: <20120903072449.GA92658@admin.sibptus.tomsk.ru> References: <20120903030217.GA79339@admin.sibptus.tomsk.ru> <50443766.4020705@boosten.org> <5044b978.qFhU35CVsU8J/nET%perryh@pluto.rain.com> <20120903072449.GA92658@admin.sibptus.tomsk.ru>
next in thread | previous in thread | raw e-mail | index | archive | help
Victor Sudakov <vas@mpeks.tomsk.su> 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.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?50458b26.tmHtgZn7IH/7r2In%perryh>