![]() |
The Digi PortServer II can split its serial ports up to multiple servers using its "realport" driver. It's kind of like doing a VLAN but for serial. For example, let's say you have a 16 port unit. Port 1-4 could be dedicated to an NT box. Port 5-12 could be for a linux/hylafax box. Port 13-16 could be for a novell. So you can have two linux boxes "mount" their own set of "/dev/ttyPSxx" serial ports. This consolidates phone lines to one area. Thanks to the "realport" driver. This is how I got around the limitation of faxq not being able to hand a job off to another hfaxd process and keep up with status. -eric wood ----- Original Message ----- > On Thu, Sep 26, 2002 at 09:43:59AM -0700, Lee Howard wrote: > > > I've also thought of running a daemon on the second server that > > > listens > > > on a TCP port and acts as a TCP <=> serial port pass-through. On the > > > first server, I would have a client for this that listens on a FIFO, > > > and configure the FIFO as a `modem' for Hylafax to use. In this case, > > > there wouldn't need to be a Hylafax server running on the second box > > > at > > > all. Has anyone had any experience with a setup like this? (I realize > > > it's a dirty hack, but it should be at least possible, right?) > > > > This would be a very cool arrangement... if it worked. What package > > would do the TCP <=> serial port pass-through? > > umodem. It makes a program that *wants* a serial port talk through a > telnet connection instead, eg: > > ATDT"remote.example.com:236 > > You have to run the program as a child of umodem, though, so I don't > know how easy it would be to make faxgetty use it. ____________________ HylaFAX(tm) Users Mailing List _______________________ To subscribe/unsubscribe, click http://lists.hylafax.org/cgi-bin/lsg2.cgi On UNIX: mail -s unsubscribe hylafax-users-request@hylafax.org < /dev/null *To learn about commercial HylaFAX(tm) support, mail sales@hylafax.org.*