Looking for a little help
The problem
I need to forward one serial port’s traffic over tcp/ip to a device. The device itself has the actual serial port device hooked up to it, and provides network access to it. I have been unable to find documentation on how to forward my traffic to it. The device itself is a “Systech RCS-3184″ or RCS-3000 series. In windows, this functionality is provided by a program called NativeCom. Searching google only yields spam aggregators.
Got a solution?
Please just leave any possible solutions in comments.
No related posts.
#1 by vom on April 23, 2007 - 1:27 pm
Quote
socat ?
#2 by dummy on April 23, 2007 - 1:30 pm
Quote
Is ser2net what you are looking for?
#3 by Marek on April 23, 2007 - 1:36 pm
Quote
netcat?
#4 by admin on April 23, 2007 - 2:10 pm
Quote
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.
#5 by vom on April 23, 2007 - 2:17 pm
Quote
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 ?
#6 by Rogan on April 23, 2007 - 2:54 pm
Quote
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.
#7 by ranf on April 23, 2007 - 3:01 pm
Quote
Haven’t used it:
http://freshmeat.net/projects/serialoverip/
#8 by admin on April 23, 2007 - 3:49 pm
Quote
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.
#9 by nacho on April 23, 2007 - 4:15 pm
Quote
Could a MOXA help???
#10 by James Stansell on April 23, 2007 - 6:03 pm
Quote
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.
#11 by Martijn on April 24, 2007 - 12:33 am
Quote
The net-tools package contains slattach — which “attaches the serial line to the network” — maybe it’s worth investigating?
#12 by Jim on April 24, 2007 - 12:45 am
Quote
http://www.lspace.nildram.co.uk/freeware.html
#13 by Rogan on April 24, 2007 - 2:26 am
Quote
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.