I gota say that tnt gets a 'no fun' rating for ease of installation/configuration. ;-) The single port multi-channel thing is weird. I can connect on one port but the other says Terminal of KO6RI off. Leave msg and //Q This may have something to do with what I did with tfkiss. I have one copy of tfkiss listening to ax0 and another on ax1. Both are putting their output into the single file that tnt reads. It's real odd how it works cuz those are my loopback interfaces. I do like tfkiss. I think I can use that to connect fbb to my ports and lose the kernel stuff that requires root level access to enable all the features. What I was looking for was a TNC emulator. I want a user to be able to telnet in and turn on his TNC. I wanted it to have a little mailbox like a tnc. The only thing fancy I wanted was a feature that allowed mail left for the owner of the mailbox to be forwarded as internet mail. It should be called from ax25d. The out going connect request should use call. Monitoring should be done by listen. It sounds like two apps to me.... a users mail box and a TNC emulator that look and feel like a Kantronics TNC. I might be able to do part of it with a smarter users interface for call and listen. Hummm, I have no idea how I could get perl to listen for users keystrokes when listen is dumping its output on stdin..... Oh well I can make call a lot smarter and I can get my script that writes my ax25d.conf file to look in the users directory for configuration information. I can worry about how the user can accept incoming connections after I create the mail box and that ought to keep me busy until the end of the world.... When is that anyway... next month isn't it. The king of terror and all that.... ;-) Bob
