Introduction
Version of TNT described
License, copying, warranty
About Packet Radio and TNT
Why this program?
What's needed?
Mailbox program DPBox
1. Screen layout
1.1. Virtual screens
1.2. Types of virtual screens
1.3. Main statusline
2. Commands
2.1. Keyboard-commands
2.1.1. Cursor movement and miscellaneous
2.1.2. Window movement and control
2.1.3. Screen switching
2.1.4. Keyboard macros
2.2. Commands in command mode
2.2.1. TNC-commands
2.2.2. External commands
2.2.2.1. Saving data to files
2.2.2.2. Sending files
2.2.2.3. Shell,Run,Redirect and Sockets
2.2.2.4. Directory
2.2.2.5. Miscellaneous
2.2.2.6. Routing scripts
2.2.2.7. Extended monitor and boxlist
2.2.2.8. Interface commands
2.2.2.9. DPBox-interface commands
2.2.2.10. Password generation commands
2.2.2.11. Remote-command permissions and access levels
2.2.2.12. Broadcast transmission/receiption
3. Detailled description
3.1. Remote commands
3.1.1. Default access levels for remote-commands
3.1.2. Sysop password validation (//SYSOP)
3.1.3. Shell with root-permissions (//ROOTSH)
3.1.4. Socket connection (//SOCKET)
3.1.5. Dangerous //ECHO command
3.1.6. Handling of unknown remote commands
3.1.7. Extended remote commands
3.2. Umlaut conversion
3.2.1. Display
3.2.2. Sending text
3.2.3. File-receive
3.2.4. File-send
3.3. Using UNIX-features
3.3.1. Shell-login
3.3.2. Redirection
3.3.3. Running programs
3.3.4. Socket server
3.3.4.1. AX25-Server
3.3.4.2. Netcmd
3.3.5. Socket connect
3.4. File transfer methods
3.4.1. AutoBIN file transfer
3.4.2. YAPP file transfer
3.4.3. 7Plus file reception
3.5. Special connect text and files with macros, Name-database
3.6. Routing scripts
3.7. Call update
3.8. Logbook
3.9. Keyboard macros
3.10. Boxlist
3.10.1. General description
3.10.2. Using boxlist
3.10.3. Using keyboard macros
3.10.4. Recognized formats
3.11. Extended monitor
3.12. Use of DPBox
3.12.1. General description
3.12.2. Using unix socket interface
3.12.3. Mailbox screen
3.12.4. Using DPBox via Packet Radio
3.12.5. Autobox and monbox feature
3.12.6. Unproto list handling
3.13. Automatic password generation
3.13.1. General description
3.13.2. DIEBOX
3.13.3. FlexNet
3.13.4. TheNet
3.13.5. Baycom
3.13.6. MD2
3.14. Huffman compression
3.15. Handling Flexnet connection quality checks
3.16. Operating different software with same callsign
3.17. PACSAT broadcast operation
3.18. Autostart on connect
3.19. TNT as daemon, TNTC
4. Description of configuration files
4.1. Main configuration file
4.1.1. Serial and general configuration
4.1.2. Security
4.1.3. Directories, Files and Sockets
4.1.3.1. Directories
4.1.3.2. Files
4.1.3.3. Sockets and Boxfiles
4.1.4. Lines of virtual screens
4.1.5. Display configuration
4.1.6. Screen attributes
4.1.6.1. Color attributes
4.1.6.2. Monochrom attributes
4.1.7. Packet assembly timeout
4.1.8. Additional options
4.2. TNC-configuration files
4.3. Cookie file
4.4. Files for remote commands
4.5. Files for connect text
4.6. Files for names database and routing scripts
4.6.1. Names database
4.6.2. Routing database
4.7. User-Id's and security
4.8. Logfile for resynchronisation
4.9. File for keyboard macros
4.10. File for password generation
4.11. File for sysop authentification
4.12. File for remote commands disabling
4.13. File containing not own callsigns
4.14. File containing Flexnet digipeaters
4.15. File for AX25-server access
4.16. File for autostart on connect
4.17. File for extended remote commands
4.18. Files for BBS features
4.19. Configuration file for TNTC
5. Additional Information
5.1. Options at startup
5.2. Running under X11
5.3. Porting of TNT
A. Appendix
A.1. Static huffman compression table
This program is free software; you can redistribute it and/or modify it under the terms of the GNU General Public License as published by the Free Software Foundation;
This program is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public License for more details (contained in file 'license').
You should have received a copy of the GNU General Public License along with this program; if not, write to the Free Software Foundation, Inc., 675 Mass Ave, Cambridge, MA 02139, USA.
There are some single board computers which implement the AX.25-protocol and contain the modem-interface to the radio-transceiver. The terminal or computer with terminalprogram is connected via a RS232-interface. These single board computers are called Terminal Node Controller (TNC).
For most of these TNCs a special software is available (WA8DED-Software or The Firmware by NORD><LINK) which can be switched to a special protocol (hostmode) at the RS232-interface. If hostmode is selected it is not possible to operate the TNC using a simple terminal, a computer with a special terminalprogram is needed.
The advantage of hostmode is that the terminalprogram can implement virtual screens for the different connections, the command mode and monitor mode. All these will be displayed together on a normal terminal which leads to confusion of the operator.
TNT is such a terminalprogram (TNT stands for TNc Terminalprogram).
If you don't have a TNC with The Firmware or you don't want to change the Software of your TNC, TFKISS may be used. TFKISS is a program running under Linux, which emulates a TNC with The Firmware. It only needs a TNC running KISS or a device which behaves like a TNC using KISS. TFKISS supports standart KISS, KISS with checksum (SMACK) and KISS with checksum used in Flexnet-digipeaters (RMNC-KISS).
Although LINUX is the development platform a porting of TNT to other UNIXes shall be possible because no special functions are used. Other terminals can be used if they have at least line insert and line delete and an entry in /etc/termcap.
The BBS contains almost all features of the known BBS-systems and is capable of performing store and forward with many other systems including packed s&f with F6FBB-BBS's. In addition it can be filled by simply monitoring the frequency. So you will get an up-to-date mailbox without transmitting yourself.
So I decided to try a port of the BBS-part of DP to Linux. Joachim gave me his Pascal-sourcecode and I translated it with P2C by Dave Gillespie (contained in most Linux-distributions) to C. P2C did a terrific job, thanks Dave! Only some minor prework at the sources was needed and P2C created almost executable code. An unix socket interface was added on both sides, TNT and DPBox and the first successful tests were performed.
Many improvements were done since then, even the PACSAT broadcast transmitter/ receiver is included now. The combination TNT and DPBox is running currently in some german full time BBS's and performing good and stable. For more information please consult the DPBox-Documentation.
To see which screen and channel is active and to give global information a statusline is displayed at the bottom of the screen.
All virtual screens (or the two parts of the connect screen) can be configured larger than the real display on the screen. Therefore only a small window of the virtual screen is displayed. The window can be moved by the operator.
To change parameters or give commands to the TNC a command screen is available. To simplify operation all commands can be entered in the connect screens, too by using a colon (:) as the first character.
It is possible to monitor all activity of other stations on the frequency. To display these information a monitor screen is available.
In addition there are some additional screens for special purposes. A screen for the heard stations list, for the extended monitor feature, for the online-help and for the box read generator. If a link to DPBox is active, there is a screen for the box operator- console, too.
If huffman compression is active on the selected channel CONNECT is replaced by CONN(H) and EXTMONI by EXTM(H).
In addition a 'P' will be displayed if the data output is paused, a 'I' if insert mode is active. If the hostmode synchronisation is lost a 'S' will be displayed. If the TNC was busy and a resend of data from the computer is done, a 'B' will be displayed. If a routing script is active a 'X' will be displayed.
If data is received on a channel which is not displayed the channel number will be displayed until it is switched to the connect screen of this channel. If a connection is active on a channel it is displayed by a '+' at the channel position.
If a file is open on the displayed channel, a two-character file type identifier and the filename (only last 14 charcters) will be displayed in the statusline. Files which receive data will be displayed in the first file field, files which transmit data will be displayed in the second file field. The two-character file type identifier will be explained in the file command chapter.
The combination Alt and key generates the code <ESC>key in normal console mode. Under X the Alt-key is not supported in that way. Therefore to activate for example the monitor screen with X you have to type first <ESC> and then M instead of Alt-M.
(*1) : Input part of connect or mailbox screen.
(*2) : Command screen and input part of extended monitor screen.
(*3) : Monitor screen, receive part of connect, extended monitor or
mailbox screen.
(*4) : Command, boxlist, heard and help screen
(*5) : Only on monitor screen
More information about the commands can be found in the documentation of the TNC software (TNC commands of NORD><LINK The Firmware 2.6a). Some of these commands are no longer existing in newer versions (TF 2.7).
DAMAdis,"B" : DAMA timeout
Version,"V" : Shows version of TNC-software
CHeck,"@T3" : Connection timer T3
Connect,"C" : Start connection
CText,"U" : Response text if connect is received by TNC
DIGIpeat,"R" : Digipeat function
Disconne,"D" : End connection
DAYTIme,"K" : Time and date functions
Frack,"F" : Start value of round trip timer for retry timing
FUlldup,"@D" : Fullduplex on modem side
MAXframe,"O" : Maximum number of outstanding packets
Monitor,"M" : Frequency monitor functions
MYcall,"I" : Callsign of the local operator
With MYCALL the call sign is set permanently on this
channel, with "I" only up to the next disconnect.
A permanent MYCALL can be removed by using "$" as call
sign.
Persist,"P" : Persistance value for transmitter keyup
RESptime,"@T2" : Delay before Info-frame will be confirmed (timer T2)
REtry,"N" : Maximum number of retries
SLottime,"W" : Slottime value for transmitter keyup
Txdelay,"T" : Time after transmitter keyup to sending of data
USers,"Y" : Number of channel open for connection
Xmitok,"X" : Locking of transmitter
BUFfers,"@B" : Free buffers of TNC
A1SRTT,"@A1" : A1-value for smoothed round trip timer
A2SRTT,"@A2" : A2-value for smoothed round trip timer
A3SRTT,"@A3" : A3-value for smoothed round trip timer
IPOll,"@I" : Packet length up to which I-Poll mode is used
VALcall,"@V" : Check callsign in connect command
All verbose commands can be abbreviated, the upcase part is mandatory.
If remote is enabled the remote station can give some commands to the program. All remote commands start with a double slash '//'. This double slash must be entered directly at the beginning of a line, otherwise the command is not recognized.
The following remote commands are recognized:
//COMP on/off Enable/disable huffman compression //NAME <name> Store name in database //CSTAT Show all active connections //SHELL Start a UNIX-shell session //TSHELL Start a UNIX-shell session without CR/LF translation //RUN <program> Execute a program //RUNT <program> Execute a program without CR/LF translation //RUN Directory of all available programs //BOX Start DigiPoint Box //COOKIE Send a cookie //DIR <filter> Show directory //DIRLONG <filter> Show directory in long format //FREE Shows space on disks //INFO Info about station //HELP This help-information //NEWS Display news about this station //READ <file> Read a file //BREAK Abort reading file //WRITE <file> Write file to disk //CLOSE End writing file //WPRG <file> Write file to disk using AUTOBIN-protocol //WPRG <file> <rfile> Same as above, but send back //RPRG <rfile> //RPRG <file> Read a file using AUTOBIN-protocol //RPRG <file> <rfile> Same as above, but send back //WPRG <rfile> //WYAPP <file> Write file to disk using YAPP-protocol //RYAPP [file] Read a file using YAPP-protocol //VERSION Show version of software //ECHO <string> Send back string //TIME Send time //RTT [timestring] Calculate round trip timer //RING Ring the bell (call for sysop) //QUIT Disconnect //DISC Disconnect //SYSOP Start sysop password validation //ROOTSH Start a shell with root-permissions //TROOTSH Same as above without CR/LF translation //SOCKET <sock addr> Start a connection to a socket //TSOCKET <sock addr> Same as above without CR/LF translation //COMMAND <command> Execute a valid TNT command
All remote commands are available for everyone (status NORMAL) except for //SHELL, //TSHELL, //ECHO, //COMMAND (status SYSOP), //ROOTSH, //TROOTSH, //SOCKET and //TSOCKET (status ROOT). The command //COMP is available if remote is disabled on the current channel (status ALWAYS). This default configuration can be changed by the command SETACC.
A new extended remote command consists of a valid remote command plus parameters. In addition the access level and the number of significant characters is defined. All data is stored in 'tnt_extremotefile'.
The contents of this file can be displayed by command LSEXTREM. When the file was updated, it can be reread using command LDEXTREM.
To be in line with the end of line convention used in Packet Radio, all line feed characters from the shell will be translated to carriage return and all received carriage return characters will be translated to line feed. This translation can be disabled by using the command TSHELL instead of SHELL or //TSHELL instead of //SHELL as a remote command.
At login time, it is checked, if the callsign of the remote station is a valid user-id. If it does not exist, depending on 'unix_new_user' in the initfile a new user-id is created or the user-id specified by 'remote_user' is used. In all cases the callsign is stored on the environment variable 'CALLSIGN'.
For some configurations it is useful to be able to get a shell with root permissions. This can be done using the command ROOTSH and remote command //ROOTSH or command TROOTSH and remote command //TROOTSH for disabled CR/LF-translation. As giving superuser access to the system is very dangerous, extra care must be taken.
To increase performance, all data will be buffered. This means that data is not sent directly, but if the buffer contains 256 Bytes (the AX25 maximum packetlength) or if for a specific time no new characters were received. This time ('pty_timeout') can be configured in the initialisation file.
REDIR allows to redirect all data of an AX25-channel to any device which is known in the system. Examples are the Linux virtual consoles /dev/ttyX or one part of a tty/pty-pair.
There is no translation of the characters, all data received is given transparently to the device and vice versa. Like for the shell-login all data will be buffered before transmission.
A special directory 'tnt_bin_dir' contains all executable programs. Programs in other directories cannot be executed by this command. Because no login is performed, the program is executed using the default user specified by 'remote_user'. If TNT was invoked not by the superuser root, the user can't be changed. In this case the program is executed under the permission of the userid from which TNT was started. The callsign of the user is stored in the environment variables 'CALLSIGN' and 'LOGNAME'. The callsign including the SSID will be available in the environment variable 'CALLSSID'.
In most cases it is wanted to translate the UNIX-linefeed to Packet-Radio carriage return and vice versa. If no translation of the characters sent and received by the program shall be done, the command RUNT must be used. Like for the shell-login all data will be buffered before transmission.
If your system is used by several people or is part of a network, you may want to give access to Packet Radio to these users. Or you want to use programs on your system, which must be able to perform an outgoing AX25-connect. To handle these requirements the socket server feature (command SOCKET) was implemented.
There are three type of servers, AXSERV, AXSPEC and NETCMD. AXSERV and AXSPEC are almost identical, both define an AX25-server. AXSPEC does not use the usual buffering method for data described for shell-login, but sends data directly on occurence of a line feed or carriage return character. NETCMD is a Wampes-compatible server which allows the usage of programs designed for Wampes (like conversd) together with TNT.
All types of servers need a socket address. This socket address can have different formats.
unix:/tcp/sockets/convers
*:3600 199.199.10.10:ftp foo.bar.com:2000
ASCII selects a translation from line feed to carriage return before transmitting data on the AX25 side and vice versa. This is the default mode.
BINARY selects a transparent connection without any character translation.
CONNECT starts an AX25 connection on a free channel. It needs additional parameters, the syntax is:
CONNECT <transport mode> <destination callsign> [source callsign]The only valid value for 'transport mode' is AX25, other modes will lead to a closing of the connection. The destination callsign must not contain any digipeaters. TNT uses the xconnect-feature to build up the connection, therefore the path must be defined in the routing database. Normally the default callsign entered with the SOCKET command will be used. If a source callsign is given in the CONNECT command, this will be used instead. There will be an automatic SSID-update to allow several connections with the same destination.
After a successful link setup the server will switch to data mode, all received data will be sent to the socket, all data from the socket will be transmitted on the AX25 side.
When the link setup was not successful, the socket connection will be simply disconnected without any further information.
Like for the other UNIX-features there is an option to translate carriage return into line feed and vice versa (command SOCKCON, remote command //SOCKET) or the possibility for a transparent connection (command TSOCKCON, remote command //TSOCKET).
Because there is no access restriction to a socket, you have to be careful with this command. A full connectivity of all sockets shall be allowed only for a sysop. Users shall get only specific sockets by defining extended remote commands ('tnt_extremotefile').
At the end of a successful transfer the elapsed time and the effective Baudrate is displayed. If a file was received, the received checksum and the calculated checksum will be displayed, too. Normally these statistical information will be send to the remote station, too. In case of LOGABIN or AUTOBIN enabled the statistical information will only be displayed (to avoid confusion of some BBSs).
If the transfer was aborted, the connection was disconnected or the calculated checksum is not equal to the received checksum, the received file will be moved to a special directory (abin_dir). In addition the name is changed to a unique name. From time to time it is needed to clean up this directory. Although in most cases these corrupted files are of no interest, for the rare cases where they are needed they are kept in this directory.
In TNT for YAPP the commands READYAPP and SENDYAPP are available, a remote user can use //RYAPP and //WYAPP. To enable the automatic reception of a YAPP-file, you can set AUTOYAPP to on. All files automatically received will be stored in 'yapp_dir' defined in tnt.ini.
In addition a file containing macros can be sent every time you like, not only on connect (command MSEND). All these files must reside in the macro text directory 'macrotext_dir'.
To be more personal and to help remembering the name of the operator of the remote station a name database is included. A name can be entered by the operator using the NAME command or with //NAME given by the remote station. If no name is specified after the command, the current name will be reported.
Following macros are expanded, if found in a connect text or macro file:
%v: Version of TNT running
%c: Call of other station
%n: Name of other station (extract from names database)
%y: Call of own station
%k: Channel number
%t: Current time
%d: Current date
%b: Bell (^G)
%i: Include news-file ('news_file_name')
%z: Timezone
%_: CR/LF
%o: Include a cookie
%?: Send a message if name of other station not contained in
names database
%%: '%' itself
You want to connect DL7ZZZ which is standby on the frequency of the digipeater DB0LUC. Your local digipeater is DB0BLO. Therefore your first command is to connect DB0BLO:
:c db0bloIf the link setup was successful you will send the line
c db0berto the digipeater which then will build up a connection to DB0BER, which is the next digipeater towards DB0LUC. If the connection is established, DB0BLO will send you the message:
*** connected to DB0BER'Now you enter the line
c db0luc db0blnwhich means DB0LUC can be reached from DB0BER via DB0BLN. DB0BLN is not connected, because it uses hop-to-hop acknowledge instead of simple digipeating. Now if the connection was successful, you get the line
BSUED:DB0BER> Connected to DB0LUC via DB0BLNand you can at last try to connect your destination with the line:
c dl7zzzThe successful connection is indicated by the line
*** connected to DL7ZZZ
If you do this manually, you must look at your screen and after each successful connect-message you must enter the new line. The connect-script facility (command XCONNECT) now does all these steps automatically, if you have given the routing information to the program. The routing information will be searched in the routing-database file (route_file_name) and reads for the example as follows:
T>DL7ZZZ Joe; N>DB0LUC T>DL7ZZZ N>DB0LUC Digi Luckau; N>DB0BER F>DB0BLN N>DB0LUC N>DB0BER Digi Tempelhof; N>DB0BLO N>DB0BER N>DB0BLO Digi 9K6
As you can see the routing entries are recursive, you don't have to specify the whole routing for the destination. The characters before the callsigns give the information to the connect script shall connect the digipeater ( N> ) or if the digipeater shall be used in the via path ( F>, D> ). To identify a normal user T> is used, for mailboxes B> can be used.
Some programs used by normal users allow a connect with the command //c <callsign>. If you want to use such a user as part of your path, put a T> in front of the callsign and a '//c <callsign>'-line will be send by the routing script.
If you frequently change your operating frequency, you may want to use the QRG command and want to define routing data only valid for a special frequency ('<IF xxxx> <END>'-clause).
'reconnected to' lines will update the call in the statusline, too, but routing scripts will not send the next command line and the logbook call will not be updated.
If the callsign is changed by a 'connected to' string in normal text, it can be restored by using the CONCALL command.
Example:
Starttime | Endtime | Callsign ------------------------------------------------------------------ 16.03.94 18:08 | 16.03.94 18:09 | DB0BLO 17.03.94 21:32 | 17.03.94 21:37 | GEHREN:DB0LUC, Uplink: DB0BLO
Each line has to begin with a two digit number specifying the keycode and a colon. (01: for <ALT>1 / <ESC>1, 10: for <ALT>0 / <ESC>0). A text line must follow directly after the colon. If the last character of the line is an asterisk '*' a CR will be sent instead of it, otherwise no CR will be sent. A command must be preceeded by an additional colon, a CR is always appended to the command line. The length of the text or command must not exceed the length of the line.
If the length of one line is not sufficient for your text or you want to send a text containing macros like time and callsign, you must specify the commands 'send' or 'msend' instead of a textline. The keyboard macro file is loaded at startup. If you change this file during execution of TNT, you can reload the file with the command 'kmacro'.
The boxlist-feature allows to fetch a file from the BBS by selecting the file (with cursor keys) from the filelist and simply pressing CR.
If an Interface-connection to a DPBox is active and a 'check'-command with bulletin-ID in the list is given, all bulletins which are in the bulletin-ID pool of the DPBox are displayed with a special attribute/colour. That means you get an overview about the bulletins already contained in your own BBS.
<ALT>8 / <ESC>8 : 'logblist' <ALT>9 / <ESC>9 : 'blist' <ALT>0 / <ESC>0 : 'xblist'
These keyboard macros are already included in the sample keyboard macro file.
7 DL4BCU > TERMINE...16 24.09.94 DL 2214 5 2m Mobilfuchsjagd I05 08.
-> R TERMINE 16
263 DL1ZAX 02.11.94 18:03 6763 DL-RUNDSPRUCH NR. 39/94
-> R 263
85 DH3FBI > KENWOOD..423 055514DB0GV DL 851 5 LF & VLF Empfang mit TS-5
-> R KENWOOD 423
DG0XC DIGI......17 28.04.95 2845DB0BALWE DL 1 DB0BRO-1 wieder ok.
-> R DIGI 17
The command EXTMON is used to activate the extended monitor. If you have given the command from an extended monitor screen, the current channel will be taken. On other screens you must give the channel number as an additional parameter before specifying the callsigns. The next free extended monitor channel will be taken if the command EXTAMON is used.
As command parameters you have to specify the callsigns of the connection you want to monitor. Normally this will be 2 callsigns and both directions will be monitored (in different attributes).
Using digipeaters like NETROM/TheNet or RMNC/Flexnet a connection is build up out of 2 connections. First the connection from station 1 to the digipeater (DL9xxx <> DB0xxx) and second the connection from the digipeater to station 2 (DL9xxx-15 <> DG1xxx). In most cases you can only monitor frames sent by the digipeater. In this case you can specify 4 callsigns (DB0xxx DL9xxx DL9xxx-15 DG1xxx) and both directions of the connection will be monitored in the extended monitor screen.
If the monitored connection is huffman-coded, decoding can be activated by
command
EXTCOMP.
The extended monitoring can be finished by the ENDEXTM command.
The command 'finbox' not only closes the connection like 'deactbox', it gives a termination command to the DPBox daemon.
The unix socket name of DPBox must be defined in 'box_socket' in the initfile.
You can either 'quit' or give the command 'endbox' to end your sysop- session.
All features of a normal connect screen are provided including the boxlist. In boxlist mode there is an additional feature. If you select a file and press 'e' instead of CR, the file will erased. 'k' for kill and 'l' for list are available, too. 't' generates a transfer line where you can add an new board name, '0' sets the lifetime of the message to 0.
DPBox is activated only, if the channel is connected.
The 'endbox' command, 'quit' to the box or a disconnect will terminate the box-session.
If you set 'monbox' to on and 'xmon' is on, all monitored frames will be searched for mail headers. If one is found, it is tried to receive the whole mail similar to the extended monitor function. If packets are lost or if any other error occurs, the mail is not accepted. If the mail was correctly received it will be sent to DPBox and will be stored in the corresponding board. All bulletins and all personal mail which contains a callsign out of 'autobox_dir' as sender or receiver will be treated in this way. All mails which will currently be received can be displayed with the 'lmonbox' command.
If some unproto frames were lost, a listening station can request a resend of older messages. To send these requests to DPBox, you have to activate the feature using command ACCUIREQ und you have to define the BBS's callsign with command ACCUICAL. This callsign must be equal to the source-callsign of the unproto frames the BBS is sending.
All these configurations are needed to enable unproto list handling in a real BBS. The other direction, TNT handling unproto lists as a client like TPK or TSTHOST is not implemented up to now.
Up to now only few password systems are implemented in TNT, but it is planned to increase the number of supported systems. If you have added any password system, please contribute!
If you invoke the command 'priv', a 4 character password will be generated out of the logintime and your password file and as a result 'PRIV xxxx' will be sent (xxxx stands for generated password).
The password may contain CR and LF, CR, LF or none of both. TNT will detect this from the length of the file.
Unlike the other password systems the third value in the configuration file is not the filename where the password is stored, but directly the password number.
There is some other software which uses the same password algorithm as FlexNet, but need a different activation string than SYS. In this case a fourth (optional) value can be used to define this activation string.
The third value in the configuration file defines the file where the password is stored.
The fourth value in the configuration file defines if some additional features shall be used. If Bit 0 is set, the password generation is done 3 times, but only one ramdomly selected time the password generation is correct. The other two 2 times a random string is sent instead of the right answer. If Bit 1 is set, the answer is hidden in a 72 character string. If Bit 2 ist set, perfect hiding is used. This means that only characters out of the password string will be used to generate the line. Alternatively you can add a second line to the password file. In this case only characters out of this line will be used.
The TheNet-type password generation is used by other software, too (for example Baycom, DigiPoint).
The syntax is the same as for TheNet, except the fifth parameter (the activation string) can be omitted. The default will be SYS. Because the string is needed only if you defined a special configuration for the user profile in BayBox, it is normally not of any importance.
There is another small difference to the TheNet syntax, the option '3 tries, where only one answer is correct', is not allowed.
XXXBBS> [ABCDEFGHIL]Out of this string an answer is generated, the password algorithm used is 'RSA Data Security, Inc. MD2 Message Digest Algorithm'.
To read a QSO in extended monitor which uses huffman compression the command EXTComp is provided.
The MONBOX feature detects huffman compression and will in most cases catch mails even if they are read in //COMP mode.
Compression is available only if tnt_comp in the configuration file is set. In this case the maximum allowed packet length (file_paclen in configuration file, command FPACLEN) for file sending is 255 Bytes.
The //comp - method was first used by DK4NB in SP 9.00, the translation table is his setup.
So TNT provides a file where the callsigns of Flexnet-digipeaters performing these connection quality checks can be stored (tnt_flchkfile). If a callsign found in this file is connecting, it will get no connect-text, no remote- access and no connection via interface will be started. The logbook will not contain this connection.
The contents of this file can be displayed by command LSTFLCHK. When the file was updated, it can be reread using command LDFLCHK.
The contents of this file can be displayed by command LSNOTOWN. When the file was updated, it can be reread using command LDNOTOWN.
The receiver is enabled by setting DECBCAST to ON. All files received in frames in PACSAT broadcast protocol will be decoded. Depending on the type of the file, a complete file will be stored in 'tnt_bcsavedir' (normal files) or will be sent to DPBox (BBS-files).
If parts of the received file are missing and the broadcast-transmitter allows it by a not permanent transmission, the missing parts can be requested. This is enabled by setting BCRQST to ON.
The status of the broadcast receiver can be displayed by BCRXSTAT. All files successfully received or currently in receiption will be displayed. Some statistical information shows the progress.
The broadcast transmitter is controlled either by DPBox to do a broadcast of BBS-files. More information can be found in the DPBox-documentation. In addition a broadcast transmission of normal files (command SENDBC) is possible, too.
The status of the broadcast transmitter can be displayed by BCTXSTAT. All files currently transmitted are listed including some statistical information.
As the TheFirmware and WA8DED-software does not allow to change the PID used for transmitted frames, the broadcast transmission will be sent using PID F0. This can lead to problems using other software (WISP) as a receiver. TFKISS and a special version of TheFirmware (ask me or DL8HBS for it) allows the change of the PID and therefore the correct broadcast transmission according to the protocol.
To make these application easily accessible and to hide that TNT is doing the work, you can define for specific callsign/SSID combinations an autostart command. This command, which contains any valid remote command plus parameters, will be executed, when the callsign/SSID combination will be connected.
The autostart-feature must be enabled using command AUTOSTRT, by default autostart is disabled.
To be able to connect the callsign/SSID combination, you have to define one or more channels of your TNC to use this callsign (use MYCALL in tnt.up).
The callsign/SSID combinations and the autostart commands are defined in 'tnt_autostartfile'. The actual data can be displayed using LSAUTOST, if the file was changed, it can be reread using LDAUTOST.
- TNT user interface needed on different host - changing between X and terminalmode without terminating TNT - no user interface needed
Therefore TNT can be started as a daemon using the command line parameter '-d' on startup. TNT then accepts socket connect requests on the socket address specified after 'frontend_socket' in tnt.ini. This socket address can have different formats (equal to the definition for socket servers):
unix:tntsock unix:/tcp/sockets/convers
*:3600 199.199.10.10:ftp foo.bar.com:2000
To connect TNT, a remote console program is available: TNTC. It uses its own configuration file tntc.ini, where the home directory and the socket to connect is stored. At start TNTC sends the terminal type (environment entry TERM) and the lines and columns of the display to TNT. Except for the number of columns which are fixed to the value specified after 'input_linelen' in tnt.ini, these values are taken to provide correct screen positioning and attributing.
TNTC can be finished without terminating TNT by giving command QUIT. With EXIT both TNT and TNTC will be terminated.
sample tnt.ini:
# defines if select() shall be used, normally 1, put to 0, if you are # using old kernels (select() produces there a higher CPU-load). use_select 1 # -------------------------------------------------------------------------- # 0 for real TNC at serial port, 1 for TFKISS on a UNIX-socket, # 2 for TFKISS on other socket soft_tnc 0 # serial port to which TNC is connected, UNIX-socket of TFKISS or # other socket for TFKISS device /dev/cua0 # lockfile for serial port or TFKISS tnt_lockfile /usr/spool/uucp/LCK..cua0 # baudrate used, only used if TNC at serial port speed 19200 # timinig parameters for interface to tfkiss (soft_tnc is 1) # 1: fixed wait (10ms) after each hostmode-packet sent to tfkiss fixed_wait 1 # if fixed_wait == 0, number of sent characters to tfkiss after which # tnt will wait 10ms amount_wait 20 # -------------------------------------------------------------------------- # number of channels of TNC tnc_channels 10 # first channel with reduced backscroll buffer r_channels 4 # -------------------------------------------------------------------------- # enable static huffman compression (//COMP) tnt_comp 1 # packet length for transmission of files file_paclen 255 # set to 1 to disconnect all channels on startup disc_on_start 0 # -------------------------------------------------------------------------- # UNIX-user for remote permissions remote_user guest # If set to 1, new users will be created, if set to 0, all new users will # be logged in as user defined by 'remote_user'. unix_new_user 1 # lowest user-id for creation of new users unix_first_uid 410 # group-id for new users unix_user_gid 101 # -------------------------------------------------------------------------- # timeout packet assembly (in seconds) for SHELL/REDIR and interface pty_timeout 2 # -------------------------------------------------------------------------- # set to 1 for request of R:-headers in boxlist read command blist_add_plus 0 # -------------------------------------------------------------------------- # SSID of DPBox (A channel with this SSID must exist in TNC!) tnt_box_ssid 7 # Call and SSID of DPBox (A channel with this Call and SSID # must exist in TNC!) # (If this parameter is used, 'tnt_box_ssid' will be ignored) #tnt_box_call # SSID of a node connect (not yet ready) tnt_node_ssid 9 # Call and SSID of a node connect (not yet ready) #tnt_node_call # -------------------------------------------------------------------------- # main directory tnt_dir /work/tnt/ # remote directory remote_dir remote/ # ctext directory ctext_dir ctext/ # directory for corrupt autobin-files abin_dir abin/ # directory for uploads upload_dir up/ # directory for downloads download_dir down/ # directory for 7plus tnt_7plus_dir 7plus/ # directory for YAPP yapp_dir yapp/ # directory for executable programs tnt_bin_dir bin/ # home-dir for new users unix_user_dir tntusers/ # dir for macro-texts macrotext_dir macro/ # dir for box-broadcastfiles tnt_bcnewmaildir bcast/newmail/ # dir for broadcastfiles tnt_bcsavedir bcast/save/ # dir for temporary broadcastfiles tnt_bctempdir /tmp/ # upfile tnt_upfile tnt.up # downfile tnt_downfile tnt.dwn # file containing process id proc_file tnt.pid # remote infofile rem_info_file tntrem.inf # remote helpfile rem_help_file tntrem.hlp # tnthelpfile tnt_help_file tnt.hlp # cookiefile tnt_cookiefile /usr/games/fortunes/startrek # namesfile name_file_name names.tnt # routesfile route_file_name routes.tnt # newsfile news_file_name news.tnt # connect text tnt_ctextfile ctext.tnt # logbook file tnt_logbookfile log.tnt # password file tnt_pwfile pw.tnt # sysop access files tnt_sysfile sys.tnt # calls with remote disabled tnt_noremfile norem.tnt # calls which do flexnet-linkquality-check tnt_flchkfile flchk.tnt # own call/SSID not allowed for xconnect tnt_notownfile notown.tnt # resync logfile resy_log_file resy.log # broadcast logfile bcast_log_file bcast.log # socket passwordfile sock_passfile netpass.tnt # file for keyboard macros func_key_file fkeys.tnt # file for extended remote commands tnt_extremotefile extrem.tnt # file for autostart on connect tnt_autostartfile autostrt.tnt # socket for digipoint box box_socket /work/box/stat/socket # directory for newmail newmaildir newmail/ # file holding monitored folders autobox_dir autobox.dir # file for boxfile endings tnt_boxender boxender.tnt # file for f6fbb-definitions f6fbb_box /work/box/system/f6fbb.box # socket for tntnode (not yet ready) node_socket /work/tntnode/socket # socket for frontend frontend_socket unix:tntsock # -------------------------------------------------------------------------- # maximum length of input line input_linelen 80 # set to 1 if insertmode shall be active after startup insertmode 0 # maximum number of entries in heardlist num_heardentries 100 # number of lines for backscroll # command-screen lines_command 50 # monitor-screen lines_monitor 400 # input area of connect-screens lines_input 20 # output area of connect-screens lines_output 100 # input area of connect-screens (reduced backscroll) lines_r_input 5 # output area of connect-screens (reduced backscroll) lines_r_output 20 # input/output-lines ratio on real screen (connect) scr_divide 5 # monitor lines on connect-screens lines_moncon 0 # input area of mailbox-screen lines_mbinput 10 # output area of mailbox-screen lines_mboutput 200 # input/output-lines ratio on real screen (mailbox) mbscr_divide 8 # input area of extended monitor screens lines_xmon_pre 10 # output area of extended monitor screens lines_xmon 100 # input/output-lines ratio on real screen (extended monitor) xmon_scr_divide 5 # -------------------------------------------------------------------------- # 0: monochrom, 1: use color attributes if TERM = 'linux' or 'conXXX', # otherwise use monochrom attributes and termcap, 2: use color attributes, # 3: use color attributes and termcap if TERM = 'xterm' color 1 # 0: don't use termcap, 1: use termcap termcap 0 # 1: alternative channel status line altstat 0 # -------------------------------------------------------------------------- # attributes for color # normal characters attc_normal 0x07 # characters in bottom statusline attc_statline 0x10 # characters in monitor-headers attc_monitor 0x06 # characters in channel statusline attc_cstatline 0x1F # control-characters attc_controlchar 0x0F # remote-answers attc_remote 0x06 # special features attc_special 0x01 # -------------------------------------------------------------------------- # attributes for monochrom # normal characters attm_normal 0x00 # characters in bottom statusline attm_statline 0x08 # characters in monitor-headers attm_monitor 0x10 # characters in channel statusline attm_cstatline 0x10 # control-characters attm_controlchar 0x10 # remote-answers and own transmitted text attm_remote 0x10 # special features attm_special 0x10 # -------------------------------------------------------------------------- # these values must remain unchanged using LINUX # 1: terminal puts cursor to a new line after character in last column auto_newline 0 # 1: don't display characters 128-160 supp_hicntl 0 # -------------------------------------------------------------------------- <EOF>
The directory 'tnt_dir' must always contain the complete path. For all other files and directories it depends on the first character of the path. If the first character is a '/', then the path is taken as the complete path. If the first character is not '/', 'tnt_dir' is put in front of the path.
if color == 1 and LINUX-console control codes are selected, but the TERM entry in the environment is not "con..." or "linux", no color and termcap is used.
The attributes are coded in the following manner:
X X X X X X X X
Blink BCo2 BCo1 BCo0 FCo3 FCo2 FCo1 FCo0
Background- Foreground-
Colour Colour
Blink:
0:off, 1:on
Background Color:
BCo2 BCo1 BCo0
Black 0 0 0
Red 0 0 1
Green 0 1 0
orange 0 1 1
blue 1 0 0
magenta 1 0 1
cyan 1 1 0
white 1 1 1
Foreground Color:
FCo3 FCo2 FCo1 FCo0
Black 0 0 0 0
Red 0 0 0 1
Green 0 0 1 0
Orange 0 0 1 1
Blue 0 1 0 0
Magenta 0 1 0 1
Cyan 0 1 1 0
White 0 1 1 1
Grey 1 0 0 0
Light red 1 0 0 1
Light green 1 0 1 0
yellow 1 0 1 1
Light blue 1 1 0 0
Light magenta 1 1 0 1
Light cyan 1 1 1 0
Light white 1 1 1 1
The attributes are coded in the following manner:
X X X X X X X X
Att5 Att4 Att3 Att2 Att1 Att0
Att0: Standout (termcap so/se)
Att1: Underline (termcap us/ue)
Att2: Blink (termcap mb/me)
Att3: Reverse (termcap mr/me)
Att4: Bold (termcap md/me)
Att5: Halfbright (termcap mh/me)
0: off, 1: on
All characters received by a shell or redirection are buffered. If the buffer reaches the maximum packetsize (256 bytes) the buffer is transmitted. After each new character pty_timeout seconds are waited for the next character. If during this time no character is given, the buffer will be sent even if the maximum packetsize is not reached.
To set up different callsigns on specific channels the following command sequence can be used:
... CHANNEL 4 MYCALL DL4YBG-4 CHANNEL 5 MYCALL DL4YBG-5 CHANNEL 6 MYCALL DL4YBG-6 ...
After the EXIT command is given another command script is executed before the termination of the program. The filename must be specified after 'tnt_downfile' in the init file.
The cookie file consists of cookie texts delimited by a line containg a '-' or a '%' as the first character (the rest of the line will be ignored). The minimal size of a cookie file is 2048 bytes.
The data files contained in the 'fortunes' package in most Linux-distributions can be used.
The filename of the cookie file must be given after 'tnt_cookiefile' in the init file.
If the remote command //info is received a file specified after 'rem_info_file' in the init file is transmitted. The file shall contain a description of the station and the used equipment.
If the remote command //news is received a file specified after 'news_file_name' in the init file is transmitted. The file shall contain any news about the station.
All entries in the names database use the following format: T>DL4YBG Mark
If the command NAME or the remote command //NAME is used to update a name, the names database file will be updated.
Unlike the names database file, the routing database is not updated by tnt, any updates must be done with an text editor.
The entries for routing scripts can be recursive, it is not needed to specify the whole path for each callsign. The path is assembled using the relevant entries in the database.
If you frequently change the frequency and the uplink digipeater, you may want to specify for every frequency a different routing database. Therefore <IF xxxxxx> and <END> is included. If for example you operate on 438.300 Mhz, you can specify all routing information valid only on this frequency by:
<IF 438.300> ... <END>
All routing information which is not surrounded by <IF xxxxxx> and <END> is valid on all frequencies. The frequency you are operating on can be specified using the command QRG.
The format of each database entry is as follows:
In front of the callsign a letter specifies the type of the station:
T : Normal user N : Network nodeAll other characters are accepted. The only difference is the treatment of the call in routing scripts.
The database is a text file containing lines like the following:
guest::407:109::/home/guest: dl4ybg::405:101::/home/dl4ybg:
These user-id's must not appear in /etc/shadow (only if shadow passwords are used).
IMPORTANT:
Check the file permissions on your system and use a password for root, now
you are not alone any longer!
# # Function-Key-File # # XX:text # XX::command # # '*' at end sends CR after a text # 01::send .signature 02:***end* 03::c db0abc 04::c db0zzz-8 08::logblist 09::blist 10::xblist <EOF>
# sample password file # all lines must use the following format: # DIEBOX: # <callsign> <password-type> <password-file> # FLEXNET: # <callsign> <password-type> <secret-number> [priv-string] # THENET: # <callsign> <password-type> <password-file> <flags> <priv-string> # BAYCOM: # <callsign> <password-type> <password-file> <flags> [priv-string] # MD2: # <callsign> <password-type> <password-file> # # DieBox DB0XXX DB0XXX-3 DIEBOX /work/tnt/db0xxx_3.pw # FlexNet DB0YYY DB0YYY FLEXNET 02345 # FlexNet DB0YYZ-8 with different activation string DB0YYZ-8 FLEXNET 02345 /SYSop # TheNet DB0ZZZ DB0ZZZ THENET /work/tnt/db0zzz.pw 0 SYS # TheNet DB0ZZA-2 with 3 tries DB0ZZA-2 THENET /work/tnt/db0zza_2.pw 1 SYS # TheNet DB0ZZB with password hiding DB0ZZB THENET /work/tnt/db0zzb.pw 2 SYS # TheNet DB0ZZC-15 with password hiding and 3 tries DB0ZZC-15 THENET /work/tnt/db0zzc_15.pw 3 SYS # TheNet DB0ZZB-1 with perfect password hiding DB0ZZB-1 THENET /work/tnt/db0zzb_1.pw 6 SYS # TheNet DB0ZZC-14 with perfect password hiding and 3 tries DB0ZZC-14 THENET /work/tnt/db0zzc_14.pw 7 SYS # Baycom DB0ZZE-5 DB0ZZE-5 BAYCOM /work/tnt/db0zze_5.pw 0 # Baycom DB0ZZD with password hiding and different activation string DB0ZZD BAYCOM /work/tnt/db0zzd.pw 2 SYS # Baycom DB0ZZD-1 with perfect password hiding and different activation string DB0ZZD-1 BAYCOM /work/tnt/db0zzd_1.pw 6 SYS # MD2 password for DB0ZZF DB0ZZF MD2 /work/tnt/db0zzf.pw <EOF>
# sample access restriction and sysop authentification file # format: # <callsign> <password-file> <sysop-level> # # DL7ZZZ with root access DL7ZZZ /work/tnt/dl7zzz.pw 1 # DL7ZZY with no root access DL7ZZY /work/tnt/dl7zzy.pw 0 <EOF>
# sample file for remote commands disabling # format: # <callsign with SSID> # DB0GR DB0BLO-8 DB0JES-3 DB0TEM-8 <EOF>
# sample file for call/SSID-combinations which are not allowed as # source callsign for xconnects # format: # <callsign with SSID> # DL4YBG DL4YBG-7 <EOF>
# sample file for ignoring Flexnet connection quality checks # format: # <callsign with SSID> # DB0BNO DB0BLN <EOF>
# netpass.tnt - file # Syntax is: # CALL PASSWORD AUTOCONNECT-CALL LEVEL # # Examples # # Next line sets user/pass=dl7zzz/geheim, no default connect, level=9 dl7zzz geheim none 9 # # Next line sets user/pass=dl7zzy/secret, autoconnects # to DB0ZZZ-8 always, and he has command-access-level=3 # This autoconnect-callsign means that dl7zzy CAN'T connect # any other station than DB0ZZZ-8 ! - Excluding if he has level=9 ! dl7zzy secret DB0ZZZ-8 3 <EOF>
# sample autostart file # format: # <callsign+SSID> <tnt command> # # connect dl4ybg-5 -> start convers user-client dl4ybg-5 convers # connect dl4ybg-12 -> get a channel status dl4ybg-12 cs # connect dl4ybg-13 -> get a unix shell dl4ybg-13 shell # connect dl4ybg-14 -> connect to convers-server dl4ybg-14 socket unix:/tcp/sockets/convers <EOF>
# sample file for extended remote commands # format: # <remote command> <access level> <significant chars> <tnt command> # # //SCONvers : connect convers (Unix-)socket sconvers 0 4 socket unix:/tcp/sockets/convers # //AXSERv : connect local ax25 server on port 2001 (only for sysop) axserv 1 5 socket localhost:2001 <EOF>
# # additional strings to detect the end of a mailbox-message # # format: 'xy string' # x: 1 = message complete, 2 = message aborted # y: value from 1 to 4 (up to 4 strings) # # one prompt of baycom-box 11 Help Dir Read Erase Check REPly Send Alter Quit # prompt of diebox, if message read cancelled 21 (H)elp (C)heck (L)ist (R)ead (S)end (E)rase (D)ir (U)sage (Q)uit # flexnet-reconnect 22 *** reconnected to <EOF>
sample f6fbb.box:
# # Definition of F6FBB-Fileheaders for the MonitorCut-Feature of DP # YOU WILL HAVE TO ALTER THESE SETTINGS! # BUT: NEVER CHANGE THE ORDER OF THE DEFINITIONS! # Unfortunately, the f6fbb-soft has two basic types of fileheaders # The first one consists of 5 lines, the second (and newer one) of 7. # Additionally those headers exist in many different lingual versions. # Therefore you are obliged to setup this file for your personal use... # # If the Header Format of your local F6FBB doesn't match to these, # please write me a msg. # # THE '#' STARTS A COMMENT LINE... THE FIRST FOUR UNCOMMENTED LINES # ARE KEPT AS THE KEYWORDS, THE FOLLOWING 12 UNCOMMENTED LINES ARE # THE MONTH IDENTIFIERS AS USED IN YOUR LOCAL F6FBB-BOX # # # An old-style (and dutch language) fbb-header may look like this: # # Van : DC6OQ voor IBM @DL # Type/Status : B$ # Datum/tijd : 21-Mrt 13:55 # Bericht # : 72618 # Titel : hilfe aastor # # Now the definitions: # # first word in header (all signs until the senders callsign): Van : # third word in header voor # # # A new-style (and german language) fbb-header may look like this: # # Von : DG8NBR # Nach : YAESU @EU # Typ/Status : B$ # Datum : 18-Jun 06:44 # BID/MID : 17630BDB0BOX # Meldung # : 85385 # Titel : info > FT 530 # # Now the definitions: # # Denotator in first line: #Von : # Denotator in second line: #Nach : # # # # A new-style (and german language) fbb-header may look like this: # #Von : DG1RFG #An : WINGT@DL #Typ/Status : BF #Datum/Zeit : 28-Apr 08:26 #BID (MID) : DQKBUMDB0BLO #Msg # : 457242 #Titel : TNX ! WinGT und Passwort wer... # # Now the definitions: # # Denotator in first line: Von : # Denotator in second line: An : # # # # month identifiers as used in your local f6fbb-bbs: # (they depend on the selected language, too) # Jan Feb Mar Apr Mai Jun Jul Aug Sep Okt Nov Dez <EOF>
# main directory tntc_dir /work/tnt/ # socket for frontend frontend_socket unix:tntsock <EOF>
Usage : tnt [-i <init-file>] [-l <log-file>] [-u] [-d]
TNT has four startup options. A file after -i is taken as the init file and a file after -l is opened on channel 1 equal to a LOGREC command. The -l option is useful if the TNC holds data from the time without a terminal. If the program was not normally ended and the serial port is locked, the lockfile can be ignored with -u. If TNT shall be started as a daemon without terminal the paramter -d must be specified. A connection to TNT can be established with TNTC.
Usage : tntc [-i <init-file>] [-s <tnt-socket>]
TNTC has two startup options. A file after -i is taken as the init file. A socket specified after -s will be used instead of the 'frontend_socket' defined in tntc.ini.
Thanks to Joerg, DD8FR for providing the code for macro expansion in the connect text and for using more than 80 characters per line.
Patrick (ex DL7AUC), who has ported TNT to ISC Unix and has contributed many ideas and additional code for the socket feature, lost his life in an accident. His work and support was very much appreciated and will be missed very much. He will always be remembered.
Thanks to Joachim, DL8HBS (author of DigiPoint for ATARI) for providing me with his sourcecode. Thanks also for the hours of discussing and planning the porting of the box-part of DP to Linux and for the support during the debugging sessions.
Thanks to Gert, DK3NY for the implementation of the password generation for DIEBOX-BBS's and for several bug reports.
Thanks to Andreas, DK9HE for analysing and fixing the startup problem if TNT was not invoked by root.
Thanks to Werner, DL4NER for code and ideas for the FlexNet password generation.
Thanks to Mario, DL5MLO for providing the code for the alternative statusline, the 'insertmode'-flag in tnt.ini, AUTO7PL and several bugfixes.
Thanks to Oliver, DL8NEG for code for the baycom password, for perfect password hiding and for //RTT.
Thanks to Hansi, DL9RDZ for a bug report concerning unsuccessful socket connect and the solution for it.
Thanks to Claudio, IW0FBB for code for the MD2 password.
Thanks to Martin, DL3FCC for providing a TeX-version of the documentation (this was the trigger to leave the path of a clean ASCII-doc).
Thanks to Bruno, F1IRW and Daniel, F1RMB for the french translation of the documentation.
Thanks to Matthias, DL2SUT for fixes in the daemon code.
The code for YAPP is based on work of Jeff Jacobsen, WA7MBL, Jonathan Naylor, G4KLX and S N Henson.
Thanks to Sanne Graaf for code for //RTT and //RING.
Thanks to Gerd, DK3NZ and Jonny, DG4MMI for bug reports.
Thanks to all who have tested TNT and have given comments.
And last but not least thanks to Linus and all of the Linux-community for giving us a superb operating system. Special thanks to Joseph H. Allen for the JOE-editor and Dave Gillespie for the P2C Pascal to C translator.
If you have questions, comments or bug reports, just write a mail:
Ham Radio : DL4YBG @ DB0GR.#BLN.DEU.EU Internet : wahlm@berlin.snafu.de
73, Mark Wahl (DL4YBG)
ASCII: HUFFMAN ASCII: HUFFMANN
< 0>: 101010110010110 <128>: 100111111110110
< 1>: 101010101000010 <129>: 00100001
< 2>: 100111111100010 <130>: 100111111101110
< 3>: 101010110011110 <131>: 100111111100110
< 4>: 101010110001110 <132>: 111100000
< 5>: 101010101111110 <133>: 011111010111110
< 6>: 101010101110110 <134>: 011111010110110
< 7>: 101010101101010 <135>: 00111010010000
< 8>: 101010101011010 <136>: 101010110100000
< 9>: 1111001101 <137>: 101010110011100
< 10>: 101010101010010 <138>: 101010110011000
< 11>: 011111010110010 <139>: 101010110010100
< 12>: 101010101101110 <140>: 101010110010000
< 13>: 1111010 <141>: 101010110001100
< 14>: 101010101001010 <142>: 1010101101110
< 15>: 100111111111010 <143>: 101010110001000
< 16>: 100111111101010 <144>: 101010110000100
< 17>: 011111010111010 <145>: 101010110000000
< 18>: 101010110100010 <146>: 101010101111100
< 19>: 101010110011010 <147>: 101010101111000
< 20>: 101010110010010 <148>: 001110110
< 21>: 101010110001010 <149>: 101010101110100
< 22>: 101010110000010 <150>: 101010101110000
< 23>: 101010101111010 <151>: 101010101101100
< 24>: 101010101110010 <152>: 101010101101000
< 25>: 10101011011000 <153>: 10101011011001
< 26>: 101010110000110 <154>: 011111010011
< 27>: 101010101100110 <155>: 101010101100100
< 28>: 101010101011110 <156>: 101010101100000
< 29>: 101010101010110 <157>: 101010101011100
< 30>: 101010101001110 <158>: 101010101011000
< 31>: 101010101000110 <159>: 101010101010100
ASCII: HUFFMAN ASCII: HUFFMANN
: 110 <160>: 101010101010000
!: 001110101 <161>: 101010101001100
": 1010101111 <162>: 101010101001000
#: 00000000011 <163>: 101010101000100
$: 011111010100 <164>: 101010101000000
%: 10101011010111 <165>: 100111111111100
&: 000000000000 <166>: 100111111111000
': 10101011010110 <167>: 100111111110100
(: 011111000 <168>: 100111111110000
): 001111001 <169>: 100111111101100
*: 01111101000 <170>: 100111111101000
+: 000000000001 <171>: 100111111100100
,: 0001001 <172>: 100111111100000
-: 0111101 <173>: 011111010111100
.: 101110 <174>: 011111010111000
/: 0011001 <175>: 0011101001011
0: 0010001 <176>: 011111010110100
1: 11110110 <177>: 011111010110000
2: 00111101 <178>: 101010110100011
3: 100111100 <179>: 101010110100001
4: 101111011 <180>: 101010110011111
5: 011111001 <181>: 101010110011101
6: 000000001 <182>: 101010110011011
7: 101010100 <183>: 101010110011001
8: 101111010 <184>: 101010110010111
9: 100111110 <185>: 101010110010101
:: 00000011 <186>: 101010110010011
;: 1010101101111 <187>: 101010110010001
<: 1010101101101 <188>: 101010110001111
=: 001111000 <189>: 101010110001101
>: 001100000 <190>: 101010110001011
?: 00000000001 <191>: 101010110001001
ASCII: HUFFMAN ASCII: HUFFMANN
@: 011111010101 <192>: 101010110000111
A: 0011100 <193>: 101010110000101
B: 0111100 <194>: 101010110000011
C: 1001110 <195>: 101010110000001
D: 1111111 <196>: 101010101111111
E: 001001 <197>: 101010101111101
F: 10111100 <198>: 101010101111011
G: 00000010 <199>: 101010101111001
H: 00000001 <200>: 101010101110111
I: 11110001 <201>: 101010101110101
J: 00000000010 <202>: 101010101110011
K: 00110001 <203>: 101010101110001
L: 11110010 <204>: 101010101101111
M: 0011010 <205>: 101010101101101
N: 0001110 <206>: 101010101101011
O: 0001111 <207>: 101010101101001
P: 1011111 <208>: 101010101100111
Q: 10101011101 <209>: 101010101100101
R: 0011111 <210>: 101010101100011
S: 000101 <211>: 101010101100001
T: 0011011 <212>: 101010101011111
U: 111100111 <213>: 101010101011101
V: 111100001 <214>: 101010101011011
W: 00100000 <215>: 101010101011001
X: 11111100 <216>: 101010101010111
Y: 1001111110 <217>: 101010101010101
Z: 100111101 <218>: 101010101010011
[: 101010111001 <219>: 101010101010001
\: 001110111 <220>: 101010101001111
]: 101010111000 <221>: 001110100111
^: 10101011010101 <222>: 101010101001101
_: 0011101001010 <223>: 101010101001011
ASCII: HUFFMAN ASCII: HUFFMANN
`: 10101011010100 <224>: 101010101001001
a: 10100 <225>: 001100001
b: 000110 <226>: 101010101000111
c: 100110 <227>: 101010101000101
d: 01110 <228>: 101010101000011
e: 010 <229>: 101010101000001
f: 000001 <230>: 100111111111111
g: 101011 <231>: 100111111111101
h: 111110 <232>: 100111111111011
i: 0110 <233>: 100111111111001
j: 0011101000 <234>: 100111111110111
k: 11111101 <235>: 100111111110101
l: 00101 <236>: 100111111110011
m: 101100 <237>: 100111111110001
n: 1000 <238>: 100111111101111
o: 101101 <239>: 100111111101101
p: 0001000 <240>: 100111111101011
q: 011111010010 <241>: 100111111101001
r: 11100 <242>: 100111111100111
s: 10010 <243>: 100111111100101
t: 11101 <244>: 100111111100011
u: 00001 <245>: 100111111100001
v: 11110111 <246>: 011111010111111
w: 1010100 <247>: 011111010111101
x: 011111011 <248>: 011111010111011
y: 1111001100 <249>: 011111010111001
z: 0111111 <250>: 011111010110111
{: 10101011010010 <251>: 011111010110101
|: 0011101001001 <252>: 011111010110011
}: 10101011010011 <253>: 011111010110001
~: 001110100110 <254>: 001110100100011
<127>: 100111111111110 <255>: 001110100100010