On Wed, 27 Oct 1999, Chris Ruffin wrote:
> -Connect the TNC to a serial port on the linux machine, run
> kissattach.
> -Connect the windows and linux machines together using the
> serial ports. Run kiss mode software on the windows station,
> run kissattach on the linux machine on that serial interface.
> -Route the packets to/from the windows station with
> axparms -forward. If you set up all the ax ports right, it
> should forward the packets to and from the windows station.
This is _exactly_ what I wrote rxecho for. So instead of axparms
-forward (which I think wouldn't work, not sure though) use that.
Our club BBS used to be a DOS FBB (Linux FBB wasn't quite mature at the
time) and I wanted to connect all the radios to a Linux machine without
the BBS users even noticing anything. So the DOS box was connected to
the Linux box with a serial cable running multi-kiss (one channel for
each radio port and one channel for the traffic between the two machines)
and the radios to the Linux box.
> Doing things this way will allow arbitrary software to be able to
> run on the windows station, since it will think that it is
> connected directly to the TNC.
In our case the DOS box thought it was talking to several TNCs
multidropped on one serial line.
> The big concern I have is the kiss connection from the linux
> station to the windows station. I've read over the kiss spec,
> and it would *seem* that it would work. But if it does seem that
> way, then it would also seem that you could connect two TNCs
> directly together and have them complement each other, i.e. all
> packets received on one TNC will be transmitted by the other, and
> vice versa. That doesn't seem right to me for some reason.
That's the way it works...
--
--- Tomi Manninen / [EMAIL PROTECTED] / OH2BNS @ OH2RBI.FIN.EU ---
