Henrik Carlqvist wrote:
I haven't tried anything like this myself, but I think something like this
might work:

nc -l -p 23 < /dev/ttyS0 > /dev/ttyS0

I think
nc -lk 23 < /dev/ttyS0 > /dev/ttyS0
is closer to what you want.

I'm looking in to how I can redirect an incoming telnet connection to go
out a serial port. What I'm trying to do is be able to telnet to a Slack
box, have the connection go out the serial port, and go to another (DOS)
box's serial port (via a null modem serial cable). That DOS box is
running a BBS program (PCBoard) which I'd like to make reachable over the
internet via telnet.

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 2009-10-10, Dan C <youmustbejoking at (no spam) lan.invalid> wrote:
I'm looking in to how I can redirect an incoming telnet connection to go
out a serial port. What I'm trying to do is be able to telnet to a Slack
box, have the connection go out the serial port, and go to another (DOS)
box's serial port (via a null modem serial cable). That DOS box is
running a BBS program (PCBoard) which I'd like to make reachable over the
internet via telnet.

Well, perhaps the simplest solution is to setup a dedicated user for
this task, and set it's shell to run something like minicom or cu on
the serial port. Anytime the user logs in, rather than running bash or
what-not, minicom will fire up and contact the DOS box on that serial
port.

- --
It is better to hear the rebuke of the wise,
Than for a man to hear the song of fools.
Ecclesiastes 7:5
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)

iEYEARECAAYFAkrTUZEACgkQNj1TaGS9H5KJCACgpOdcNgcDz8SljJa/oMbY8gB3
1nMAn0IL5vfwpuvF9q4u8Vjr8fYx+BHy
=uKjK
-----END PGP SIGNATURE-----

I'm looking in to how I can redirect an incoming telnet connection to
go out a serial port. What I'm trying to do is be able to telnet to a
Slack box, have the connection go out the serial port, and go to
another (DOS) box's serial port (via a null modem serial cable). That
DOS box is running a BBS program (PCBoard) which I'd like to make
reachable over the internet via telnet.

Well, perhaps the simplest solution is to setup a dedicated user for
this task, and set it's shell to run something like minicom or cu on the
serial port. Anytime the user logs in, rather than running bash or
what-not, minicom will fire up and contact the DOS box on that serial
port.

On Tue, 13 Oct 2009 23:21:23 +1000, Res wrote:

I'm sure it was not a m$ proggy, but, it is a VERY long time ago, I
*think* I might have found it on simtel, that kinda rings a bell, but
its late and i'm not going to stretch the brain any further tonight.

Trumpet? It's been a long time for me as well, but I think I remember
using that ...

On 13 Oct 2009 23:04:28 GMT, Dan C wrote:

... The tricky part is getting the communication from the Linux gateway
to the DOS computer running the BBS. How to connect the "bbs" user to
the outbound serial port of the Linux box? ...

Look at the "cu" command from the UUCP package that ships with
Slackware. I think you *should* be able to set that up, with appropriate
options as your "bbs" user's shell, to have anyone logging into your
system with that be immediately captive to the serial connection to the
BBS system.

I hope this helps ...

On Wed, 14 Oct 2009 03:33:05 +0200, Aragorn wrote:

The other option, which I would not rule out just yet, would be
to implement TCP/IP on the DOS box.

...have been scouring and collecting old files for
attempting to get TCP/IP on the DOS box.

On 14 Oct 2009 03:21:56 GMT,
Dan C <youmustbejoking at (no spam) lan.invalid> wrote:
On Wed, 14 Oct 2009 03:33:05 +0200, Aragorn wrote:

The other option, which I would not rule out just yet, would be to
implement TCP/IP on the DOS box.

...have been scouring and collecting old files for
attempting to get TCP/IP on the DOS box.

Dan, this approach might be possible. Back around the turn of the
millenium I used an HP 200LX as my sole travel computer. It ran DOS
5.0, and with lots of niggling I was able to get it connected to the
internet with TCP/IP over an ethernet PCMCIA card as well as with a
modem. Some of my old notes from those activities (not all of which is
relevant to your request) are here:

http://heise.nu/LXTCP.html

http://heise.nu/LX-LAN.html

The starting point would probably be WATTCP. There is at least one
caveat, this was all done using the 200LX as a client, but it seems if
you could get a TCP/IP connection established, it might be possible to
use the box to serve up services. I do have some dim memory of using
ssh to login to the 200LX over the network.

The other option, which I would not rule out just yet, would be to
implement TCP/IP on the DOS box.