Skip site navigation (1)Skip section navigation (2)
Date:      Mon, 3 Sep 2012 14:24:49 +0700
From:      Victor Sudakov <vas@mpeks.tomsk.su>
To:        freebsd-questions@freebsd.org
Subject:   Re: Sharing COM ports to Windows hosts
Message-ID:  <20120903072449.GA92658@admin.sibptus.tomsk.ru>
In-Reply-To: <5044b978.qFhU35CVsU8J/nET%perryh@pluto.rain.com>
References:  <20120903030217.GA79339@admin.sibptus.tomsk.ru> <50443766.4020705@boosten.org> <5044b978.qFhU35CVsU8J/nET%perryh@pluto.rain.com>

next in thread | previous in thread | raw e-mail | index | archive | help
perryh@pluto.rain.com wrote:
> > > There is a FreeBSD box with several RS232 ports. Can those ports
> > > be accessed by Windows hosts over the network?
> >
> > If I understand your question correctly, then AFAICT the only way to 
> > access serial ports over the network is with a piece of additional 
> > hardware, like a terminal server, for instance:
> >
> > http://www.perle.com/products/Terminal-Server.shtml?utm_source=ppc&utm_medium=cpc&utm_campaign=server
> 
> I believe the OP wants to use a FreeBSD machine, that has several
> serial ports and a network connection, _as_ a terminal server.

Correct.

> 
> I can think of no reason why such an arrangement could not be made
> to work; the question is whether someone has already written the
> necessary FreeBSD code to accept a telnet/ssh/whatever connection,

There are several in the ports collection. Some even implement
RFC2217. Some work and some don't.

> initiated by a Windows terminal-server driver, and _transparently_
> connect the session to a serial port on the FreeBSD machine 

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 :)

-- 
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?20120903072449.GA92658>