Hi all, first of all, thanx a lot for this useful software. Suddendly i tried it to use it but i didnt make it work for me. I'm using a single linux machine (bot client and server, for testing porpuse), and i'm using cyclades-serial-client-0.93 as client. I want to make available an addictional serial port which actually is a virtual one connected via Tcp/ IP to the real one. In fact the final application will consist of such a modem over ip emulation. Thanx in advance
Suddendly i tried it to use it but i didnt make it work for me. I'm using a single linux machine (bot client and server, for testing porpuse), and i'm using cyclades-serial-client-0.93 as client. I want to make available an addictional serial port which actually is a virtual one connected via Tcp/ IP to the real one. In fact the final application will consist of such a modem over ip emulation.
Tell us a bit more about your setup:
* Which inetd program are you using? (inetd/xinetd/other)
* Do you start cyclades-ser-cli manuelly, or from the cyclades-serial-client script? I usually start it manually, with arguments like:
./cyclades-ser-cli -x -m 1 -p 6999 /tmp/ttyS0 localhost 1
Give us the output from this command.
* Which applications are you trying to use? Remember you need to set LD_PRELOAD. You also either need to set the environment variable CYCLADES_DEVICES, or adapt /etc/cyclades-devices.
Btw, I recommand that you try the CVS version of cyclades-serial-client. I've done some enhancements to the preload library recently. There are still problems, though. I think the largest problem is lack of support for the ioctl TIOCMGET.
Thanx a lot for you suggestions, now with them i made it work. I'm using xinetd, and i configured it as usual. I just noticed that if i bind sercd to port 7000 (say n), i have to specify 6999 (n-1) as cyclades command line parameter. Is it a little bug or a feature? In terms of packaging, i noticed that in the CVS tree of cyclades-serial-client lacks the file <cyclades-serial-client-src-root>/inc/conf.h.in The configure script (produced by autoconf) complains about it, so I copied it from the tarball distribution and it works well for me, but i can't say if it's a solution.. Thanx a lot again for you software and help. i hope i can contribute more in the future... Francesco Ciacca On Friday 07 May 2004 19:01, you wrote:
Suddendly i tried it to use it but i didnt make it work for me. I'm using a single linux machine (bot client and server, for testing porpuse), and i'm using cyclades-serial-client-0.93 as client. I want to make available an addictional serial port which actually is a virtual one connected via Tcp/ IP to the real one. In fact the final application will consist of such a modem over ip emulation.
Tell us a bit more about your setup:
Which inetd program are you using? (inetd/xinetd/other)
Do you start cyclades-ser-cli manuelly, or from the
cyclades-serial-client script? I usually start it manually, with arguments like:
./cyclades-ser-cli -x -m 1 -p 6999 /tmp/ttyS0 localhost 1
Give us the output from this command.
- Which applications are you trying to use? Remember you need to set
LD_PRELOAD. You also either need to set the environment variable CYCLADES_DEVICES, or adapt /etc/cyclades-devices.
Btw, I recommand that you try the CVS version of cyclades-serial-client. I've done some enhancements to the preload library recently. There are still problems, though. I think the largest problem is lack of support for the ioctl TIOCMGET.
Thanx a lot for you suggestions, now with them i made it work.
Great.
I'm using xinetd, and i configured it as usual. I just noticed that if i bind sercd to port 7000 (say n), i have to specify 6999 (n-1) as cyclades command line parameter. Is it a little bug or a feature?
I guess this is some kind of feature. As you might know, this software was originally written by Russell Coker at Cyclades. As I understand it, it was originally designed to be a good client for Cyclades terminal servers, rather than a generic RFC2217 client.
I think there are two future paths for this software:
1) Keep the support for all kinds of Cyclade hardware. This will eventually require that some developers actually have access to the hardware, and are willing to do som testing.
2) Drop the support for non-RFC2217 Cyclade hardware, and turn this software into a genric RFC2217 client.
Currently, I'm the only active developer, and I have no access to or interest in the Cyclades hardware, so currently, it seems like we are slowly heading towards alternative 2...
In terms of packaging, i noticed that in the CVS tree of cyclades-serial-client lacks the file <cyclades-serial-client-src-root>/inc/conf.h.in The configure script (produced by autoconf) complains about it, so I copied it from the tarball distribution and it works well for me, but i can't say if it's a solution..
conf.h.in should be generated by "autoheader". It gets created when I run ./bootstrap on my FC1 machine. You might try to run "autoheader" manually, or verify that your Autotools are up to date.
-
Francesco Ciacca (Consultant) -
Peter Astrand