Date: Wed, 5 Sep 2012 09:06:36 +0700 From: Victor Sudakov <vas@mpeks.tomsk.su> To: freebsd-questions@freebsd.org Subject: Re: Sharing COM ports to Windows hosts Message-ID: <20120905020636.GA38610@admin.sibptus.tomsk.ru> In-Reply-To: <20120903125210.GA5387@external.screwed.box> References: <20120903030217.GA79339@admin.sibptus.tomsk.ru> <86wr0binyc.fsf@srvbsdfenssv.interne.associated-bears.org> <20120903072920.GB92658@admin.sibptus.tomsk.ru> <20120903125210.GA5387@external.screwed.box>
next in thread | previous in thread | raw e-mail | index | archive | help
Peter Vereshagin wrote: > Depending on a task I think the most interactive user-friendly solution here is > a minicom(s) each in its own ssh'ed jail(s). There is special Windows software for managing Natex MUXes. It works with those MUXes via an RS232 port only. I want to be able to run it from a remote location. Solution 1. A hardware RS232 portserver (e.g. Moxa) and a special Windows driver for COM-port redirection. Works great. Disadvantage: it's pretty expensive and occupies additional rack space. Solution 2. Using an existing networked FreeBSD box sitting next to the MUX, it already has COM ports. Advantage: cheap, no additional rack space and power. Disadvantage: doubts if this solution is feasible, especially on the Windows side. A minicom or any other interactive terminal emulation software is out of the question. The MUX managing software uses its own protocol over RS323 and insists that it be a "real" port. Perhaps my English is so poor that I could not present the task correctly from the very beginning. Sorry for that. -- 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?20120905020636.GA38610>