[Date Prev] [Date Index] [Date Next] [Thread Prev] [Thread Index] [Thread Next]
Bryan Stansell bryan@conserver.com
Thu, 6 Jun 2002 10:33:55 -0700 (PDT)
i'm sorry to say that, nope, conserver isn't the right tool for that. if you wanted to briefly interact with the serial port, you could use things like: (echo "AT"; sleep 5) | console -f remconsole and you'd be able to see the response to the AT command, but it doesn't provide a non-interactive two-way communication (although i've put some thought into the client code required for that - unfortunately, it's not as straightforward as you might think). i remember that livingston (the portmaster folks) had an app that would allow pseudo-serial ports (local devices) access to the serial ports on their terminal servers. that kind of thing sounds like what you'd need. obviously, their particular app won't work for you, since it's made for livingston products, but maybe this will trigger something in someone's mind about an app that would do what you want, in a similar way. sorry i couldn't really help, but i've got to believe that something like what you're looking for exists. Bryan On Thu, Jun 06, 2002 at 02:57:46AM -0700, gdsmarshall@hushmail.com wrote: > I have installed conserver client and server on two separate Linux > (x86) machines (A and B respectively), the B has a modem on /dev/modem, > the A does not. > > I would like to run a program on A (say minicom) which talks to the > modem on B, but thinks it is talking to /dev/modem on A, will conserver > do the job? if so, what should the start up parameters be please? I > have run conserver client and server and typed AT commands in on A, and > the modem reacts on B. Nice program, I like it. However, I do not > understand if or how I can talk to /dev/modem (using say minicom) on A > and using conserver client and server be actually talking to the modem > on B. > > Any help will be much appreciated. > > Many thanks, > > Spencer