Configuring KISS-over-TCP Ports

KISS TNCs can be accessed over a TCP/IP connection. This port type supports such connections; however, it assumes that the other software providing the TCP/IP server socket will handle all issues of ensuring the TNC (software or hardware) is in KISS mode over the socket connection, or that the user will have pre-configured the TNC is KISS mode (or used a KISS-only TNC) prior to starting YAAC.

To add a new KISS-over-TCP port, click the Add button on the Configure Ports tab. The port editing dialog will appear. Set the port type to KISS-over-TCP.

KISS-over-TCP port configuration panel

The other parameters you will need to specify for the port are:

Once you have the settings the way you want them, click OK. Ensure that the KISS-over-TCP service providing software is running on the target host before you click OK. At that time, YAAC will begin using the KISS protocol over the TCP/IP socket connection as a communications proxy.

Should the remote TNC you have connected to actually be an instance of W1HKJ's FLDIGI program, invoking the configuration window when the connection is established will display additional information:

KISS-over-TCP configuration panel showing FLDIGI modem choices

To the right will be displayed a list of all the FLDIGI OpModes (or modems) that the attached instance of FLDIGI supports in KISS mode (i.e., capable of sending 8-bit binary data packets) with FLDIGI's currently selected mode also selected on the list. Clicking on an entry in the list will command FLDIGI to switch to that OpMode.

If you want to create a KISS-over-TCP port on a new installation of YAAC using the -createport option, the port_description is of the format:


where serverhostname is the domain name or numeric IP address of the KISS-over-TCP server instance you wish to connect to, such as, portNumber is the TCP port number of the KISS-over-TCP server (8001 if accessing DireWolf, other values for other servers), the extra comma after callsign is to skip the unused passcode field, transmitEnabled is either "true" or "false" (without the quotes) depending on whether you want this port able to transmit packets. Any digipeatAlias specified here must also already be specified on the expert-mode configuration dialog's Digipeat tab.