On Fri, Dec 20, 2013 at 11:23 AM, Joseph Spenner <joseph85750 at yahoo.com> wrote: > >>Do you need a real serial port involved at all? It sounds like what >>you really want is a linux device that looks like a tty in terms of >>accepting ioctl's from a program that thinks it is a serial port, but >>actually accepts a tcp connection. I suppose you could rig a >>loopback cable and actually have a separate program writing to the >>serial port with the loopback returning it to your listening >>application. >> > Les: > Actually, no-- I do not really need a physical "port". It could all be virtual. What does the actual application do? If it is just collecting/logging data - or even something slightly more complicated you might be able to replace it with kermit (ckermit package in EPEL) which can work the same way on serial or tcp connections. But, I think socat will do what you need if you can make it connect a PTY (perhaps with optional symlink name) with a TCP4-LISTEN, and have your application open the pty. -- Les Mikesell lesmikesell at gmail.com