- To: mikebw@IDS.JVNC.NET (Mike Bilow, firstname.lastname@example.org)
- Subject: TTYLINK Question
- From: email@example.com (Jon Zeeff)
- Date: Wed, 8 Jan 92 23:07:20 EST
> >>>Has anybody tweaked the ttylink code to allow a ttylink connection (telnet
> >>>port 87) to be re-directed to a COM# async port? My reason for wanting this
> >>>is to allow access to a RS232-equipped instrument to be accessed over the
> >I'm working on making a telnet to port 23 do this. Basically, turning ka9q
> >into a modem or async host (or whatever you want to attach) server.
> It is possible to connect to the mailbox by AX.25 or telnet and issue
> the sysop ("@") command. If the proper bit mask is set in the FTPUSERS
> file so that the user has sysop privileges, this command gives remote
> access to the "net>" prompt. It is then legal to make routing changes,
> start and stop processes, and so forth, as long as the commands issued
So I assume you could do what we want by using the @ command and then the
tip command. The result is that a user coming in on a telnet conenction can
talk directly to an async port?
Of course the @ command really give the user to much control - my code
will just automatically connect someone to a free async port.
> Do you really want a remote user to have to capability to send raw data
> directly to an interface? This starts to get far afield of what most
Yes, a modem server or a connection to some async only host can be