The latest release of TNOS can always be ftp'd from Brian Lantz's (TNOS author) machine, ftp://ftp.lantz.com/tnos/current. It can also be found at ftp.ucsd.edu in the /hamradio/packet/tcpip/incoming directory a few days after a new version is released. There is also a mirror site of ftp.lantz.com which you will probably get better performance from, Brians net link is 28.8k PPP, this is a T1 link. FTP to ftp.mwmicro.com and look in mirrors/tnos. You will also find all the other goodies from ftp.

TNOS is a multi-threaded application that contains a complete implementation of industry standard TCP/IP with drivers, applications, and support for use in an RF environment, primarily the Amateur Packet Radio environment. There are two versions, one that runs under MS-DOS/PC-DOS/DR-DOS and any multi-taskers that support virtual DOS boxes, and the other which runs as an application under Linux and other unix systems.

Modify the 'autoexec.nos' file for your needs, or convert one from TNOS/Dos or another variant of xNOS Before connecting TNOS/Linux to a TNC: You should look in the /etc/rc.d directory and see if you have an rc.serial file. If you do, examine it, as it MAY need to have some changes made to it before the serial ports will be ready for use.

Tee-NOS, the 'Tee' is pronounced like a tee in golf. Or if you are British, like the tea in a cup of tea :-)

Most certainly yes! There is a very good mailing list for TNOS help and comments, here are the details:- Mailing Lists at lantz.com There are several mailing lists maintained at lantz.com. All are available as regular subscriptions or digest subscriptions. Current TNOS specific mailing lists include: Joining a Mailing List To join one of these mailing lists, send a mail message to listserv@lantz.

To take advantage of the FBB forwarding in TNOS, you need to be running Version 2.0 or later. To set your forwarding sessions to use FBB style forwarding, you should set forward fbb-style on. If you also want the FBB compressed forwarding then use forward fbb-compression on . You should also note that the syntax of the forward.bbs file has changed completely. You can use the cnvfwd program distributed with TNOS 2.0+ releases to convert your old pre-2.0 forward.bbs file to the new format.

It has been noted that starting your servers right at the end of your autoexec.nos file i.e. your 'start' lines, can lead to a more stable system. You should also make sure you are running a fairly recent version of TNOS. At the time of writing this I am running 2.0pl2 for Linux, and it seems to be proving very stable. If you must run an earlier version than 2.0 for Linux, then make sure you do not have the status line turned on, also the tcpgate facility is buggy in earlier versions.

Here are some points from Brian Lantz that should be read and digested before you send your 'bug' report to the Tnos-Topics mailing list :-) DO give as detailed a description as possible, indicating what actions/commands you used, the order used, the given output (if any), and the expected results. DO use the trace function for the feature you are having a problem/question with, if there is one available. DON'T even bother with a report if all you can say is "it don't work!".

I have noticed that Linux TNOS when compared to Dos TNOS, on the same specification hardware will perform faster. Running TNOS under Linux will allow yourself and your users to take advantage of several Linux/unix services, such as ftp, smtp, telnet, httpd, online muti-user games etc. Using TNOS under Linux you will not run into any memory restictions such as you would with the Dos version. You have no need to worry about what options you compile into your version of TNOS i.e. how large it is.

This is probably due to the fact that you are not publishing your TNOS IP address via the Linux kernel IP, thus TNOS will never receive ARP broadcasts for its own address. This is easily fixed by adding a line in your rc.local or rc.inet1 file (or wherever you choose to put it depending on your Linux/unix installation. It is usual to assign a non 44 IP address to TNOS too, when working with a network/internet connection. This is assigned to the TNOS end of the pseudo slip link to the kernel.

Is there a command in TNOS to stop certain mail areas being broadcast with the MAILFOR beacon? I have some message areas I do not want broadcasting over the air!

My setup has ONE port out, to ONE TNC, that forwards to many BBSs. MOST of them go out on ONE RF port. In order to pace the traffic and better use the bandwidth, I place all those that must travel the same RF path into a subchannel together. Ones that travel ANOTHER RF path, go into another subchannel. Then the 'forward subchannel' command allows me to restrict HOW MANY of these will be active at one time (outgoing), and how many I will reverse forward to (incoming).

ctlcheck is a diagnostic tool used to display the raw values of a *.ctl file. It is not normally needed other than for diagnosing problems when altering code that manipulates *.ctl files.

It will run, but only if you use a stripped down version (less features compiled in), and have almost NO drivers, etc loaded into memory. TNOS must exist in conventional memory, and on processors earlier than a 386, you had no support in the CPU for altering memory maps to maximize the conventional memory. I ran TNOS on a 286 for several years, I just needed a good "shoehorn" to get in what features I needed." So there you go.

To do this you must add certain lines to your Linux startup files to add a pseudo slip port to talk to TNOS. First I shall give details of the necessary lines that must be added to your startup files, and then the lines which will need to be added to your TNOS startup file (autoexec.nos). NOTE: You must also have IP_FORWARDING enabled in your Linux kernel. This is set in the make config part of building a kernel. Usually these lines can be put in one of the rc.* files found in # # the /etc/rc.

First make sure you have the patch utility. Assuming you have this then the easiest way is to 'cd' to your source directory and do the following:-

The patch utility for DOS can be found on ftp.lantz.com in /tnos/misc or the mirror site of ftp.mwmicro.com in /mirrors/tnos/misc.

At the date of this FAQ (see top), TNOS has been compiled or run on, most DOS systems, e.g. Microsoft, DR and PC. It works well under OS/2 and recent versions of Linux. TNOS will also run/compile with Free/BSD and with BSD/OS (BSDI). Included makefile for BSD/OS by Dave VK2KFU # USEELF = INSTALL= install -c -g dialer -m 2755 CC = gcc PATCHES = -DIS_LITTLE_ENDIAN -DUSE_SETSTACK -DBSD_RANDOM -DDUMP_CORE SETSTACK= setsp.

Well this depends on what operating system you are running TNOS under. First I will describe one way of doing it under Linux, and then a way of doing it under DOS. Please note. There is another example later in this FAQ from Brian, ko4ks, that details a slightly different way of doing this. Mix 'n' Match :-) Caveat.

This is probably due the the fact you have the smtp hopper code compiled into your TNOS. The smtp hopper defaults to ON, at least in 1.14 TNOS. If the site you are mailing is down stream of a TheNet X1J type node/router, (or indeed any other router that does not handle SMTP connects) and you have a IP route set via one of these nodes, then the smtp hopper code will be trying to deliver your mail to this node!

The function key problem with TNOS under X has to do with the fact that the terminfo entry for xterm is seriously broken in many distributions (I know it is in Slackware through at least 1.2.0). Following is an "xterm.tic" souce file for my hacked version that restores fkey functionality. Run it through tic to generate the new database file, and the problem should be solved in xterms (or rxvts) opened thereafter. BTW -- this problem drove me nuts for almost a month.

The tcpgate facility in TNOS allows you to re-direct incoming IP packets, destined for a particular port, to a different host. To make this clearer here are some examples:- You may not want to use the in built TNOS ftp server, so you could re-direct incoming ftp connections to your Unix ftp server, or another machines ftp server. NOTE I do not presently do this myself, some people have had varying degrees of success doing this.

The cron facility in TNOS is based upon the Unix cron command and crontab file. Basically it allows you to schedule TNOS events for certain times or days/months etc. it is much more flexible than the 'at' command in TNOS and other NOS's. Cron relies on a file to read its schedule of events from, this is the ..tnos/spool/crontab file. Here is an example of the crontab file I use at gb7mbb.ampr.org. TNOS 2.02 crontab file. This file is spool/crontab .

I have noticed that Linux TNOS when compared to Dos TNOS, on the same specification hardware will perform faster. Running TNOS under Unix will allow yourself and your users to take advantage of several Linux/unix services, such as ftp, smtp, telnet, httpd, online muti-user games etc. Using TNOS under Unix you will not run into any memory restictions such as you would with the Dos version. You have no need to worry about what options you compile into your version of TNOS i.e. how large it is.

This is probably due to the fact that you are not publishing your TNOS IP address via the Unix kernel IP, thus TNOS will never receive ARP broadcasts for its own a ddress. This is easily fixed by adding a line in your rc.local or rc.inet1 file (or wherever you choose to put it depending on your Linux/unix installation. It is usual to assign a non 44 IP address to TNOS too, when working with a network/internet connection. This is assigned to the TNOS end of the pseudo slip link to the kernel.