-
Notifications
You must be signed in to change notification settings - Fork 1
/
faq-tnc.html
91 lines (69 loc) · 3.15 KB
/
faq-tnc.html
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
<!doctype html>
<html lang=en>
<meta charset=utf-8>
<title>HamBSD FAQ: Terminal Node Controllers</title>
<meta name="description" content="HamBSD FAQ: Terminal Node Controllers">
<meta name="viewport" content="width=device-width, initial-scale=1">
<link rel="stylesheet" type="text/css" href="openbsd.css">
<link rel="canonical" href="https://hambsd.org/faq-tnc.html">
<h2 id="HamBSD">
<a href="index.html">
<b>Ham</b><i>BSD</i></a>
FAQ: Terminal Node Controllers
<small>
<a href="faq.html">[FAQ Index]</a>
</small>
</h2>
<hr>
<ul>
<li><a href="#supported" >Supported TNCs</a>
<li><a href="#config" >Configuring a TNC as a network interface</a>
<li><a href="#init" >Automatically initialising a TNC</a>
<li><a href="#kisstcp" >Using KISS-over-TCP</a>
</ul>
<hr>
<h2 id="supported"><a class="permalink" href="#supported">Supported TNCs</a></h2>
<p>
A list of TNCs that are known to work with HamBSD's kiss(4) driver are maintained in
the <a href="https://man.hambsd.org/kiss.4">manual page</a>. Most, if not all, TNCs that
implement the KISS protocol over a serial interface should be supported. This includes
those with RS-232 interfaces, USB-to-serial interfaces, or using a pseudo-terminal
(<a href="https://man.hambsd.org/pty.4">pty(4)</a>).
<h2 id="config"><a class="permalink" href="#config">Configuring a TNC as a network interface</a></h2>
<p>
To configure a TNC to be used as an <a href="https://man.hambsd.org/ax25.4">AX.25</a> network
interface on boot, create a <a href="https://man.hambsd.org/hostname.if.5">hostname.if(5)</a>
file. For the first interface on the system this should be named <code>/etc/hostname.axkiss0</code>.
<pre>lladdr MYCALL up
!ldattach -s 1200 kiss cua00</pre>
Replace <em>MYCALL</em> with your callsign. This also assumes the TNC's serial port (not on-air
baud rate) operates at 1200 baud and is connected to the first serial port. For USB-to-serial
interfaces, the first interface will be <em>cuaU0</em>.
<h2 id="init"><a class="permalink" href="#init">Automatically initialising a TNC</a></h2>
<p>
A <a href="https://man.hambsd.org/chat.8">chat(8)</a> script may be used to
initialise a TNC that requires configuration before it enters KISS mode. The
following example works for the Kenwood TM-D700E:
<pre>cmd:--cmd: 'kiss on'
cmd: 'mon off'
cmd: restart</pre>
<p>
This script can be stored as <code>/etc/kiss.chat</code> and run automatically
by adding the following to the relevant <a href="https://man.hambsd.org/hostname.if.5">hostname.if(5)</a>
file before calling ldattach:
<pre>!stty -f /dev/cuaXX 9600
!chat -t 5 -f /etc/kiss.chat <>/dev/cuaXX >&0</pre>
<h2 id="kisstcp"><a class="permalink" href="#kisstcp">Using KISS-over-TCP</a></h2>
To use KISS-over-TCP, for example with Dire Wolf, the <a
href="https://man.hambsd.org/rkissd.8">rkissd(8)</a> daemon can be used.
<p>
To start an interface automatically at boot, create a new <a
href="https://man.hambsd.org/hostname.if.5">hostname.if(5)</a> file for a
<code>kiss</code> interface (e.g. <code>/etc/hostname.kiss0</code>):
<pre>!rkissd 192.168.0.10 8001</pre>
<p>
To start an interface manually:
<pre>ifconfig create kiss0
rkissd 192.168.0.10 8001</pre>
</body>
</html>