Date: Wed, 5 Sep 2012 09:15:16 +0700 From: Victor Sudakov <vas@mpeks.tomsk.su> To: freebsd-questions@freebsd.org Subject: Re: Sharing COM ports to Windows hosts Message-ID: <20120905021516.GB38610@admin.sibptus.tomsk.ru> In-Reply-To: <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> <50458b26.tmHtgZn7IH/7r2In%perryh@pluto.rain.com>
next in thread | previous in thread | raw e-mail | index | archive | help
perryh@pluto.rain.com 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. I am fine with that too. Whatever works. > 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. Actually, that was the reason of my question here: perhaps someone has already found a matching pair (freeware if possible). Two commercial solutions have already been named: NetDialout from PCMicro and DialOut/EZ COM Port Redirector from Tactical Software. Eric has mentioned com0com, but I have not been able to make it work (I am not much of a Windows guy, and this software is a good example of Windows hacking, in the good sense of the word, but still, I cannot figure out how to create the configuration described in the README file, some components seem missing). -- Victor Sudakov, VAS4-RIPE, VAS47-RIPN sip:sudakov@sibptus.tomsk.ru
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20120905021516.GB38610>