New answers tagged

0

I'm assuming you want this because you need to talk to a device in the other side of the serial port from the ssh connection, and that it's not a modem or some such (where you could use the network stack). If the command that you want to write from can run a command and communicate to that using stdin and stdout, you can just use SSH itself, since SSH ...


0

I'm not totally sure about the first part of the pipe you give as an example, but if you can somehow configure the program that writes to a serial port to use your fake serial port, you can simply write: socat pty,link=$HOME/ttyFAKE,raw,echo=0 - | ssh user@host "tee /dev/ttyREAL" socat will create the device for you.


1

Perhaps you can do something like this example using socat which creates a pseudo-tty and a symbolic link to it in ~/myserialline. When you open it socat runs ssh (in this example to localhost) where it runs socat to join stdin/stdout to a real serial device. socat PTY,link=$HOME/myserialline,raw,echo=0 EXEC:'ssh localhost socat - /dev/ttyS0' You can ...


0

I finally found out what was the issue for this behaviour. I used some busy waiting in my communication loop, which lead to heavy cpu load. I read then, that using SerialPort commands like BytesToRead and Read are not ideal at all: If you must use .NET System.IO.Port.Serialport Therefore I tried using asynchronous functions of ByteStream ReadAsync and ...


1

In RedHat 6 there is an upstart script /etc/init/serial.conf that will ensure the console is designated a secure terminal before starting the getty process, and so ensuring root can login on the console. You may be better off setting the root password to something unknown, thus forcing people to always login as a non-root user and then using sudo to switch ...


0

I have found screen and cu capable of these functions. Assuming that you are doing something like a USB-Serial adapter, the syntax would be: cu -s 115200 /dev/ttyUSB0 screen /dev/ttyUSB0 115200


0

If you are trying to do this through screen on OSX, you can follow the procedure laid out by user32704 with some small modifications. You will need to first build lrzsz from source, which can be found here: https://ohse.de/uwe/releases/lrzsz-0.12.20.tar.gz Then, instead of exec !! sx yourbinary.bin you should use: exec !! lsz -X yourbinary.bin



Top 50 recent answers are included