Comments on: Serial port over TCP/IP http://www.sharms.org/blog/2007/04/23/serial-port-over-tcpip/ Technology, Linux, Life Wed, 10 Mar 2010 22:35:45 +0000 http://wordpress.org/?v=2.9.2 hourly 1 By: Rogan http://www.sharms.org/blog/2007/04/23/serial-port-over-tcpip/comment-page-1/#comment-492 Rogan Tue, 24 Apr 2007 06:26:15 +0000 http://www.sharms.org/blog/?p=94#comment-492 Yeah, the example was primarily to illustrate creating a local device that your serial comms program can open. You naturally don't have to use EXEC:SSH to connect to the other end. just use a TCP4:IP:port syntax instead. Yeah, the example was primarily to illustrate creating a local device that your serial comms program can open. You naturally don’t have to use EXEC:SSH to connect to the other end. just use a TCP4:IP:port syntax instead.

]]> By: Jim http://www.sharms.org/blog/2007/04/23/serial-port-over-tcpip/comment-page-1/#comment-490 Jim Tue, 24 Apr 2007 04:45:54 +0000 http://www.sharms.org/blog/?p=94#comment-490 http://www.lspace.nildram.co.uk/freeware.html http://www.lspace.nildram.co.uk/freeware.html

]]> By: Martijn http://www.sharms.org/blog/2007/04/23/serial-port-over-tcpip/comment-page-1/#comment-489 Martijn Tue, 24 Apr 2007 04:33:36 +0000 http://www.sharms.org/blog/?p=94#comment-489 The net-tools package contains slattach -- which "attaches the serial line to the network" -- maybe it's worth investigating? The net-tools package contains slattach — which “attaches the serial line to the network” — maybe it’s worth investigating?

]]> By: James Stansell http://www.sharms.org/blog/2007/04/23/serial-port-over-tcpip/comment-page-1/#comment-484 James Stansell Mon, 23 Apr 2007 22:03:38 +0000 http://www.sharms.org/blog/?p=94#comment-484 rtelnet was the first thing I thought of when I read your post so you might try to find information about it. Google doesn't return much about it, but you might look here: http://www.protocolbase.net/protocols/protocol_RTELNET.php The 2nd thought I had was Conserver; does it sound any better? http://www.conserver.com/consoles/Training/login-story.html Regards, -james. rtelnet was the first thing I thought of when I read your post so you might try to find information about it. Google doesn’t return much about it, but you might look here: http://www.protocolbase.net/protocols/protocol_RTELNET.php

The 2nd thought I had was Conserver; does it sound any better?
http://www.conserver.com/consoles/Training/login-story.html

Regards,

-james.

]]> By: nacho http://www.sharms.org/blog/2007/04/23/serial-port-over-tcpip/comment-page-1/#comment-483 nacho Mon, 23 Apr 2007 20:15:28 +0000 http://www.sharms.org/blog/?p=94#comment-483 Could a MOXA help??? Could a MOXA help???

]]> By: admin http://www.sharms.org/blog/2007/04/23/serial-port-over-tcpip/comment-page-1/#comment-481 admin Mon, 23 Apr 2007 19:49:48 +0000 http://www.sharms.org/blog/?p=94#comment-481 The socat example doesn't work because I can't run anything on the server side as it is an embedded device. I am thinking that it is the right utility though. The socat example doesn’t work because I can’t run anything on the server side as it is an embedded device. I am thinking that it is the right utility though.

]]> By: ranf http://www.sharms.org/blog/2007/04/23/serial-port-over-tcpip/comment-page-1/#comment-480 ranf Mon, 23 Apr 2007 19:01:28 +0000 http://www.sharms.org/blog/?p=94#comment-480 Haven't used it: http://freshmeat.net/projects/serialoverip/ Haven’t used it:
http://freshmeat.net/projects/serialoverip/

]]> By: Rogan http://www.sharms.org/blog/2007/04/23/serial-port-over-tcpip/comment-page-1/#comment-478 Rogan Mon, 23 Apr 2007 18:54:51 +0000 http://www.sharms.org/blog/?p=94#comment-478 Socat is the right option. From the man page: (socat PTY,link=$HOME/dev/vmodem0,raw,echo=0,waitslave EXEC:'"ssh modemserver.us.org socat - /dev/ttyS0,nonblock,raw,echo=0"') Generates a pseudo terminal device (PTY) on the client that can be reached under the symbolic link $HOME/dev/vmodem0. An application that expects a serial line or modem can be configured to use $HOME/dev/vmodem0; its traffic will be directed to a modemserver via ssh where another socat instance links it with /dev/ttyS0. Socat is the right option. From the man page:

(socat PTY,link=$HOME/dev/vmodem0,raw,echo=0,waitslave EXEC:’”ssh modemserver.us.org socat – /dev/ttyS0,nonblock,raw,echo=0″‘)

Generates a pseudo terminal device (PTY) on the client that can be reached under the symbolic link $HOME/dev/vmodem0. An application that expects a serial line or modem can be configured to use $HOME/dev/vmodem0; its traffic will be directed to a modemserver via ssh where another socat instance links it with /dev/ttyS0.

]]> By: vom http://www.sharms.org/blog/2007/04/23/serial-port-over-tcpip/comment-page-1/#comment-477 vom Mon, 23 Apr 2007 18:17:21 +0000 http://www.sharms.org/blog/?p=94#comment-477 A little more detail on socat: http://www.linux.com/article.pl?sid=07/03/23/1513256 Just change one of your endpoints to TCP4-LISTEN or something. This seems to be exactly what you are looking for, no ? A little more detail on socat:

http://www.linux.com/article.pl?sid=07/03/23/1513256

Just change one of your endpoints to TCP4-LISTEN or something. This seems to be exactly what you are looking for, no ?

]]> By: admin http://www.sharms.org/blog/2007/04/23/serial-port-over-tcpip/comment-page-1/#comment-475 admin Mon, 23 Apr 2007 18:10:05 +0000 http://www.sharms.org/blog/?p=94#comment-475 It looks like I want the opposite of ser2net. I have a server that is listening for a TCP connection, and local programs that want to access the serial port that is really on the device listening for TCP. It looks like I want the opposite of ser2net. I have a server that is listening for a TCP connection, and local programs that want to access the serial port that is really on the device listening for TCP.

]]>