Peter Åstrand wrote:
Thanks for writing this. I'm trying to figure out how to use this software to connect the serial port from one machine to the serial port of another machine over a network, or at least this is my eventual goal.
./cyclades-ser-cli -x -m 1 -p 7999 /dev/ptypx 172.16.32.3 1 cyclades-ser-cli /dev/ptypx: NOTICE: Using /dev/pts/1 pseudo-tty cyclades-ser-cli /dev/ptypx: NOTICE: Using 172.16.32.3:8000 socket cyclades-ser-cli /dev/ptypx: WARNING: Can't initiate connection on a socket : Connection refused cyclades-ser-cli /dev/ptypx: WARNING: Trying again ... cyclades-ser-cli /dev/ptypx: WARNING: Can't initiate connection on a socket : Connection refused cyclades-ser-cli /dev/ptypx: ERR: signal 2 received ( 21, 0%, 0%, 0%)
What am I doing wrong?
Obviously, 172.16.32.3 does not listen on port 8000. You can verify this with "telnet 172.16.32.3 8000". Have you restarted xinetd, and checked it's log files? You can try running xinetd in debug mode with -d.
When I try connecting to 172.16.32.3 using telnet I get a "Connection refused"
I did try restarting xinetd, I even rebooted just to be sure.
Here is what xinetd spits out when I try and run the cyclades client from the other machine with debug enabled.
05/1/6@10:07:03: DEBUG: {main_loop} select returned 1 05/1/6@10:07:03: DEBUG: {server_start} Starting service telnet 05/1/6@10:07:03: DEBUG: {main_loop} active_services = 2 05/1/6@10:07:03: DEBUG: {exec_server} duping 7
When I kill it it spits this out
05/1/6@10:11:56: DEBUG: {check_flags} flag entry 0 processed 05/1/6@10:11:56: DEBUG: {child_exit} waitpid returned = 2590 05/1/6@10:11:56: DEBUG: {server_end} telnet server 2590 exited 05/1/6@10:11:56: DEBUG: {child_exit} waitpid returned = -1 05/1/6@10:11:56: DEBUG: {main_loop} active_services = 2
running minicom with the command "minicom -p /dev/ptypx" gives me a login prompt to 172.16.32.3 so I think its starting telnet instead of sercd.
-- Conn
***************************************************************** Give a man a match and you heat him for a moment. Set him on fire and you'll heat him for life. *****************************************************************
Conn Clark Engineering Stooge clark@esteem.com Electronic Systems Technology Inc. www.esteem.com
Stock Ticker Symbol ELST
On Thu, 6 Jan 2005, Conn Clark wrote:
Obviously, 172.16.32.3 does not listen on port 8000. You can verify this with "telnet 172.16.32.3 8000". Have you restarted xinetd, and checked it's log files? You can try running xinetd in debug mode with -d.
When I try connecting to 172.16.32.3 using telnet I get a "Connection refused"
...
Here is what xinetd spits out when I try and run the cyclades client from the other machine with debug enabled.
This doesn't make sense to me. If "telnet 172.16.32.3 8000" (you didn't miss 8000, right?) says "Connection refused", then xinetd shouldn't react at all when you start the cyclades client. Assuming that the cyclades client tries to connect to port 8000, of course, but the logs clearly said that.
running minicom with the command "minicom -p /dev/ptypx" gives me a login prompt to 172.16.32.3 so I think its starting telnet instead of sercd.
But if xinetd is starting telnet upon connections to port 8000, then why does "telnet 172.16.32.3 8000" give you "Connection refused"?
I'm puzzled.
Peter Åstrand wrote:
On Thu, 6 Jan 2005, Conn Clark wrote:
Obviously, 172.16.32.3 does not listen on port 8000. You can verify this with "telnet 172.16.32.3 8000". Have you restarted xinetd, and checked it's log files? You can try running xinetd in debug mode with -d.
When I try connecting to 172.16.32.3 using telnet I get a "Connection refused"
...
Here is what xinetd spits out when I try and run the cyclades client from the other machine with debug enabled.
This doesn't make sense to me. If "telnet 172.16.32.3 8000" (you didn't miss 8000, right?) says "Connection refused", then xinetd shouldn't react at all when you start the cyclades client. Assuming that the cyclades client tries to connect to port 8000, of course, but the logs clearly said that.
running minicom with the command "minicom -p /dev/ptypx" gives me a login prompt to 172.16.32.3 so I think its starting telnet instead of sercd.
But if xinetd is starting telnet upon connections to port 8000, then why does "telnet 172.16.32.3 8000" give you "Connection refused"?
I'm puzzled.
Mabey this is the excuse I need to justify the time upgrading from redhat 7.1 ;-)
I'll try switching the client and server boxes. The client I was using is a RH 8 box.
I'll let you know what happens.
-- Conn
***************************************************************** Give a man a match and you heat him for a moment. Set him on fire and you'll heat him for life. *****************************************************************
Conn Clark Engineering Stooge clark@esteem.com Electronic Systems Technology Inc. www.esteem.com
Stock Ticker Symbol ELST
-
Conn Clark -
Peter Åstrand