LinuxHam - User contributions [en]

AMPRnet / IP-Address Assignment

2014-03-30T08:29:47Z

Tom: Update remote website

For Amateur Radio operators there is a Class A-Subnet reserved.

This IPv4 Network 44/8 is known as the AMPRNet, named from "AMateur Packet Radio Network".

The ampr.org domain is administered by Brian Kantor, WB6CYT. He delegated lower Levels of the name space to "local coordinators" (by geographical or political entities) who assign addresses to ham radio operators in their area.

If you need an address for e.g. IP over AX25 check the AMPRNet [http://www.ampr.org/ main website] for general information and a list of local AMPRNet coordinators or/and have a look at your local Packet Radio BBS to search for your "local local coordinator".

[[de:AMPRNet_/_IP-Adressen]]

Main Page

2007-07-27T11:49:31Z

Tom: Kernel-versions now up-to-date

__NOEDITSECTION__
{| style="width:100%;"
|-
|
<div style="background:#e0e0ff;border:1px solid #cfcfff;padding:1em;padding-top:0.5em;padding-bottom:0.5em; color:black;">
<big>'''Protocols'''</big><br>
[[AX.25]] – [[NET/ROM]] – [[ROSE]] – [[6PACK]] – [[KISS]] – [[TCP/IP]]

<big>'''Net Resources'''</big><br>
[[Net_Resources#Mailing_Lists|Mailing Lists]] – [[Net_Resources#IRC|IRC]] – [[Net_Resources#Convers|Convers]] – [[CVS]]

<big>'''Software'''</big><br>
[[Distributions]] – [[Packet Radio]] – [[Morse Code]] – [[PSK31]] – [[AMTOR]] – [[PACTOR]] – [[SSTV]] – [[FAX]]

<big>'''Misc'''</big><br>
[[AMPRnet / IP-Address Assignment]] – [[Design and Construction Software]] – [[Satellite Software]] – [[Shack Automation Software]] – [[Training and Educational Software]]
|}

{| style="width:100%;"
|- style="vertical-align:top;"
| style="width:66%;background:#ffe0c0;border:1px solid #ffd0b0;padding:1em; color: black;" |
== News ==
2006-04-19 Start German version of the site.

2006-04-15 The former non-public ham.linux-mips.org moves to it's new home at www.linux-ax25.org.

== Old News ==
[[2005]]

| style="background:#e0e0ff;border:1px solid #c6c9ff;padding:1em; color: black;" |
<div style="text-align: center;">
== Latest Versions ==
Linux 2.6.22<br>
Linux 2.4.35<br>
</div>

[[de:Hauptseite]][[fr:Accueil]]

Distributions

2007-05-16T00:37:08Z

Tom: /* Novell-SuSE / openSUSE */ ISO-fy date, update URL SuSE-10.1-repository

The aggregation of a Linux kernel, other system software such as a boot loader and applications are called '''distributions''' Distributions differ in their ''philosophy'' such as being for free or commercial, the targeted audience, distribution medium, added value for example in form of software for installation and system maintenance and the way that support is handled. Another differenciating factor - and the reason for the existence of this page is the degree of support for amateur radio. This page is trying to give an overview.

Live CDs for one thing are meant for trying out things for Linux beginners as they usually don't change the existing system. They also are useful for testing to what degree a computer system is supported by Linux. Live CDs are usually for the i386 architecture and are frequently based on Knoppix (http://www.knopper.net/knoppix/) which against is rooted on Debian. Live CDs are interesting because some are optimized for amateur radio.

== Full distributions ==
=== Debian ===
[http://www.debian.org/ Debian] is supporting 11 different hardware architectures and comes with a vast collection of amateur collection. Basically there are three version of Debian available:

* [http://www.debian.org/releases/woody/ oldstable] (aka Woody) http://packages.debian.org/oldstable/hamradio/<br>for the predecessor of Sarge security updates will be available until at least May 2006. For new installations generally Sarge is recommended.
* [http://www.debian.org/releases/stable/ stable] (aka Sarge) http://packages.debian.org/stable/hamradio/<br>The current and recommended Debian release. It consists of sofware which is considered stable and well tested and receives updates for usage and security critical problems. 2.4 and 2.6 kernel can be choosen during installation.
* [http://www.debian.org/releases/testing/ testing] (aka Etch) http://packages.debian.org/testing/hamradio/<br>contains software which is intended for the next stable Debian distribution. Usually works very without problems but isn't automatically updated in case of usage or security critical problems.
* [http://www.debian.org/releases/unstable/ unstable] (aka Sid) http://packages.debian.org/unstable/hamradio/<br>contains new, not yet well tested programs and versions.

Mailing list:
[http://lists.debian.org/debian-hams/ debian-hams]

=== Gentoo ===
* [http://www.gentoo.org/ Gentoo]<br>[http://www.gentoo-portage.com/media-radio/ amateur radio software]

=== Novell-SuSE / openSUSE ===
Novell-SuSE doesn't activly support amateur radio software in its distribution any more.
Despite that Novell-SuSE 9.3 and 10.0 i386 amateur radio software packages are getting maintained by JÃ¶rg, DL1BKE in his spare time. They can be installed through SuSE's system management tool YOU/YAST. All it takes for example for SuSE 9.3 is adding

<pre>
ftp://ftp.suse.com/pub/projects/ham/9.3-i386
</pre>
as an installation source.

Upto SuSE 9.0 or 9.1 amateur radio applications were still shipping on all installation media. Later versions had them only on the DVD version. For SuSE Live CDs amateur radio software had to be installed from the internet.

SuSE has changed the "time base" in their kernels for SuSE 9.2 and 9.3 without fixing the timing for [[AX.25]] under <tt>/proc/sys/net/ax25</tt>. Without change a connection attempt will timeout after 0.3s instead of 300s.

Mailing list: [http://lists.suse.com/archive/suse-ham/ SuSE-ham] - mostly german spoken on this list.<br>
For further instructions e-mail the lists' robot suse-ham-help@suse.com.

* [http://de.opensuse.org/ openSUSE]
The PPC architecture is supported since openSUSE 10.0.

NOTE: mkiss is broken in SUSE 10.0.

2006-12-21
Tim Fischer, DG7GT is now maintaining Ham Radio packages for openSUSE. Both 10.1 and 10.2 are available in x86 and x86_64 and the kernel is still compiled with AX.25 support modules included. The packages are found at
<pre>
http://dg7gt.osth.de/SUSE_Linux_10.1/
http://dg7gt.osth.de/openSUSE-10.2-ham/
</pre>
and are mirrored at
<pre>
http://ftp.w1nr.net/suse-ham/dg7gt.osth.de/suse-10.1-ham-extended/ (may not be up-to-date - check!)
http://ftp.w1nr.net/suse-ham/dg7gt.osth.de/openSUSE-10.2-ham/
</pre>

Set up the appropriate YaST installation source pointing to one of the above. ftp.w1nr.net supports both http and ftp protocols. The mailing list has been migrated to http://lists.opensuse.org/opensuse-ham/

=== Redhat / Fedora Core ===
None of the Redhat Linux rsp. Fedora Core distributions did every ship with amateur radio software. For [[packet radio]] even the kernel will have to be replaced with a kernel that has the necessary features built in since the distribution kernels don't come with AX.25 and the necessary drivers.
* [http://www.redhat.com/ Red Hat]

=== Ubuntu ===
[http://www.ubuntulinux.org/ Ubuntu] is debian-based and is therefore compareable to debian in respect to amateur radio support. Note that in order to install most of the amateur radio related packages, you need to edit your /etc/apt/sources.list file and un-comment the lines which talk about the "universe" repository.

== Live-CDs build for amateur radio support ==
=== AR-Knoppix/Afu-Knoppix ===
[http://www.afu-knoppix.de/neu/index.php?lng=1 AR-Knoppix] current version is V3.7 dated January 2005 (based on Knoppix 3.7 from December 2004)

=== Hamshack-Hack ===
[http://hamshack-hack.sourceforge.net/ Hamshack-Hack] is based on Knoppix, too. Release:????

[[de:Distributionen]]

Main Page

2007-05-16T00:11:34Z

Tom: update on kernel versions

__NOEDITSECTION__
{| style="width:100%;"
|-
|
<div style="background:#e0e0ff;border:1px solid #cfcfff;padding:1em;padding-top:0.5em;padding-bottom:0.5em; color:black;">
<big>'''Protocols'''</big><br>
[[AX.25]] – [[NET/ROM]] – [[ROSE]] – [[6PACK]] – [[KISS]] – [[TCP/IP]]

<big>'''Net Resources'''</big><br>
[[Net_Resources#Mailing_Lists|Mailing Lists]] – [[Net_Resources#IRC|IRC]] – [[Net_Resources#Convers|Convers]] – [[CVS]]

<big>'''Software'''</big><br>
[[Distributions]] – [[Packet Radio]] – [[Morse Code]] – [[PSK31]] – [[AMTOR]] – [[PACTOR]] – [[SSTV]] – [[FAX]]

<big>'''Misc'''</big><br>
[[AMPRnet / IP-Address Assignment]] – [[Design and Construction Software]] – [[Satellite Software]] – [[Shack Automation Software]] – [[Training and Educational Software]]
|}

{| style="width:100%;"
|- style="vertical-align:top;"
| style="width:66%;background:#ffe0c0;border:1px solid #ffd0b0;padding:1em; color: black;" |
== News ==
2006-04-19 Start German version of the site.

2006-04-15 The former non-public ham.linux-mips.org moves to it's new home at www.linux-ax25.org.

== Old News ==
[[2005]]

| style="background:#e0e0ff;border:1px solid #c6c9ff;padding:1em; color: black;" |
<div style="text-align: center;">
== Latest Versions ==
Linux 2.6.21.1<br>
Linux 2.4.34.4<br>
</div>

[[de:Hauptseite]][[fr:Accueil]]

AMPRnet / IP-Address Assignment

2006-12-02T22:57:10Z

Tom: Link to german page

For Amateur Radio operators there is a Class A-Subnet reserved.

This IPv4 Network 44/8 is known as the AMPRNet, named from "AMateur Packet Radio Network".

The ampr.org domain is administered by Brian Kantor, WB6CYT. He delegated lower Levels of the name space to "local coordinators" (by geographical or political entities) who assign addresses to ham radio operators in their area.

If you need an address for e.g. IP over AX25 check the AMPRNet [http://hamradio.ucsd.edu/ main website] for general information and a list of local AMPRNet coordinators or/and have a look at your local Packet Radio BBS to search for your "local local coordinator".

[[de:AMPRNet_/_IP-Adressen]]

AMPRnet / IP-Address Assignment

2006-12-02T21:48:33Z

Tom: Version 0.1

For Amateur Radio operators there is a Class A-Subnet reserved.

This IPv4 Network 44/8 is known as the AMPRNet, named from "AMateur Packet Radio Network".

The ampr.org domain is administered by Brian Kantor, WB6CYT. He delegated lower Levels of the name space to "local coordinators" (by geographical or political entities) who assign addresses to ham radio operators in their area.

If you need an address for e.g. IP over AX25 check the AMPRNet [http://hamradio.ucsd.edu/ main website] for general information and a list of local AMPRNet coordinators or/and have a look at your local Packet Radio BBS to search for your "local local coordinator".

Main Page

2006-12-02T21:39:10Z

Tom: new: AMPRNet/IP Address Assignment; beautify

__NOEDITSECTION__
{| style="width:100%;"
|-
|
<div style="background:#e0e0ff;border:1px solid #cfcfff;padding:1em;padding-top:0.5em;padding-bottom:0.5em; color:black;">
<big>'''Protocols'''</big><br>
[[AX.25]] – [[NET/ROM]] – [[ROSE]] – [[6PACK]] – [[KISS]] – [[TCP/IP]]

<big>'''Net Resources'''</big><br>
[[Net_Resources#Mailing_Lists|Mailing Lists]] – [[Net_Resources#IRC|IRC]] – [[Net_Resources#Convers|Convers]] – [[CVS]]

<big>'''Software'''</big><br>
[[Distributions]] – [[Packet Radio]] – [[Morse Code]] – [[PSK31]] – [[AMTOR]] – [[PACTOR]] – [[SSTV]] – [[FAX]]

<big>'''Misc'''</big><br>
[[AMPRnet / IP-Address Assignment]] – [[Design and Construction Software]] – [[Satellite Software]] – [[Shack Automation Software]] – [[Training and Educational Software]]
|}

{| style="width:100%;"
|- style="vertical-align:top;"
| style="width:66%;background:#ffe0c0;border:1px solid #ffd0b0;padding:1em; color: black;" |
== News ==
2006-04-19 Start German version of the site.

2006-04-15 The former non-public ham.linux-mips.org moves to it's new home at www.linux-ax25.org.

== Old News ==
[[2005]]

| style="background:#e0e0ff;border:1px solid #c6c9ff;padding:1em; color: black;" |
<div style="text-align: center;">
== Latest Versions ==
Linux 2.6.19<br>
Linux 2.4.33.4<br>
</div>

[[de:Hauptseite]][[fr:Accueil]]

Main Page

2006-12-02T20:11:06Z

Tom: update to current kernel release

__NOEDITSECTION__
{| style="width:100%;"
|-
|
<div style="background:#e0e0ff;border:1px solid #cfcfff;padding:1em;padding-top:0.5em;padding-bottom:0.5em; color:black;">
<big>'''Protocols'''</big><br>
[[AX.25]] – [[NET/ROM]] – [[ROSE]] – [[6PACK]] – [[KISS]] – [[TCP/IP]]

<big>'''Net Resources'''</big><br>
[[Net_Resources#Mailing_Lists|Mailing Lists]] – [[Net_Resources#IRC|IRC]] – [[Net_Resources#Convers|Convers]] – [[CVS]]

<big>'''Software'''</big><br>
[[Distributions]] – [[Packet Radio]] – [[Morse Code]] – [[PSK31]] – [[AMTOR]] – [[PACTOR]] – [[SSTV]] – [[FAX]]

<big>'''Misc'''</big><br>
[[Satellite Software]]  – [[Shack Automation Software]] – [[Design and Construction Software]] – [[Training and Educational Software]]
|}

{| style="width:100%;"
|- style="vertical-align:top;"
| style="width:66%;background:#ffe0c0;border:1px solid #ffd0b0;padding:1em; color: black;" |
== News ==
2006-04-19 Start German version of the site.

2006-04-15 The former non-public ham.linux-mips.org moves to it's new home at www.linux-ax25.org.

== Old News ==
[[2005]]

| style="background:#e0e0ff;border:1px solid #c6c9ff;padding:1em; color: black;" |
<div style="text-align: center;">
== Latest Versions ==
Linux 2.6.19<br>
Linux 2.4.33.4<br>
</div>

[[de:Hauptseite]][[fr:Accueil]]

Main Page

2006-10-17T13:52:34Z

Tom: update info abt kernel releases

__NOEDITSECTION__
{| style="width:100%;"
|-
|
<div style="background:#e0e0ff;border:1px solid #cfcfff;padding:1em;padding-top:0.5em;padding-bottom:0.5em; color:black;">
<big>'''Protocols'''</big><br>
[[AX.25]] – [[NET/ROM]] – [[ROSE]] – [[6PACK]] – [[KISS]] – [[TCP/IP]]

<big>'''Net Resources'''</big><br>
[[Net_Resources#Mailing_Lists|Mailing Lists]] – [[Net_Resources#IRC|IRC]] – [[Net_Resources#Convers|Convers]] – [[CVS]]

<big>'''Software'''</big><br>
[[Distributions]] – [[Packet Radio]] – [[Morse Code]] – [[PSK31]] – [[AMTOR]] – [[PACTOR]] – [[SSTV]] – [[FAX]]

<big>'''Misc'''</big><br>
[[Satellite Software]]  – [[Shack Automation Software]] – [[Design and Construction Software]] – [[Training and Educational Software]]
|}

{| style="width:100%;"
|- style="vertical-align:top;"
| style="width:66%;background:#ffe0c0;border:1px solid #ffd0b0;padding:1em; color: black;" |
== News ==
2006-04-19 Start German version of the site.

2006-04-15 The former non-public ham.linux-mips.org moves to it's new home at www.linux-ax25.org.

== Old News ==
[[2005]]

| style="background:#e0e0ff;border:1px solid #c6c9ff;padding:1em; color: black;" |
<div style="text-align: center;">
== Latest Versions ==
Linux 2.6.18.1<br>
Linux 2.4.33.3<br>
</div>

[[de:Hauptseite]]

Main Page

2006-06-19T15:33:42Z

Tom: new kernel-release

__NOEDITSECTION__
{| style="width:100%;"
|-
|
<div style="background:#e0e0ff;border:1px solid #cfcfff;padding:1em;padding-top:0.5em;padding-bottom:0.5em; color:black;">
<big>'''Protocols'''</big><br>
[[AX.25]] – [[NET/ROM]] – [[ROSE]] – [[6PACK]] – [[KISS]] – [[TCP/IP]]

<big>'''Net Resources'''</big><br>
[[Net_Resources#Mailing_Lists|Mailing Lists]] – [[Net_Resources#IRC|IRC]] – [[Net_Resources#Convers|Convers]] – [[CVS]]

<big>'''Software'''</big><br>
[[Distributions]] – [[Packet Radio]] – [[Morse Code]] – [[PSK31]] – [[AMTOR]] – [[PACTOR]] – [[SSTV]] – [[FAX]]

<big>'''Misc'''</big><br>
[[Satellite Software]]  – [[Shack Automation Software]] – [[Design and Construction Software]] – [[Training and Educational Software]]
|}

{| style="width:100%;"
|- style="vertical-align:top;"
| style="width:66%;background:#ffe0c0;border:1px solid #ffd0b0;padding:1em; color: black;" |
== News ==
2006-04-19 Start German version of the site.

2006-04-15 The former non-public ham.linux-mips.org moves to it's new home at www.linux-ax25.org.

== Old News ==
[[2005]]

| style="background:#e0e0ff;border:1px solid #c6c9ff;padding:1em; color: black;" |
<div style="text-align: center;">
== Latest Versions ==
Linux 2.6.17<br>
Linux 2.4.33<br>
</div>

[[de:Hauptseite]]

Distributions

2006-05-09T18:07:18Z

Tom:

The aggregation of a Linux kernel, other system software such as a boot loader and applications are called '''distributions''' Distributions differ in their ''philosophy'' such as being for free or commercial, the targeted audience, distribution medium, added value for example in form of software for installation and system maintenance and the way that support is handled. Another differenciating factor - and the reason for the existence of this page is the degree of support for amateur radio. This page is trying to give an overview.

Live CDs for one thing are meant for trying out things for Linux beginners as they usually don't change the existing system. They also are useful for testing to what degree a computer system is supported by Linux. Live CDs are usually for the i386 architecture and are frequently based on Knoppix (http://www.knopper.net/knoppix/) which against is rooted on Debian. Live CDs are interesting because some are optimized for amateur radio.

== Full distributions ==
=== Debian ===
[http://www.debian.org/ Debian] is supporting 11 different hardware architectures and comes with a vast collection of amateur collection. Basically there are three version of Debian available:

* [http://www.debian.org/releases/woody/ oldstable] (aka Woody) http://packages.debian.org/oldstable/hamradio/<br>for the predecessor of Sarge security updates will be available until at least May 2006. For new installations generally Sarge is recommended.
* [http://www.debian.org/releases/stable/ stable] (aka Sarge) http://packages.debian.org/stable/hamradio/<br>The current and recommended Debian release. It consists of sofware which is considered stable and well tested and receives updates for usage and security critical problems. 2.4 and 2.6 kernel can be choosen during installation.
* [http://www.debian.org/releases/testing/ testing] (aka Etch) http://packages.debian.org/testing/hamradio/<br>contains software which is intended for the next stable Debian distribution. Usually works very without problems but isn't automatically updated in case of usage or security critical problems.
* [http://www.debian.org/releases/unstable/ unstable] (aka Sid) http://packages.debian.org/unstable/hamradio/<br>contains new, not yet well tested programs and versions.

Mailing list:
[http://lists.debian.org/debian-hams/ debian-hams]

=== Gentoo ===
* [http://www.gentoo.org/ Gentoo]<br>[http://www.gentoo-portage.com/media-radio/ amateur radio software]

=== Novell-SuSE / openSUSE ===
Novell-SuSE doesn't activly support amateur radio software in its distribution any more.
Despite that Novell-SuSE 9.3 and 10.0 i386 amateur radio software packages are getting maintained by JÃ¶rg, DL1BKE in his spare time. They can be installed through SuSE's system management tool YOU/YAST. All it takes for example for SuSE 9.3 is adding

<pre>
ftp://ftp.suse.com/pub/projects/ham/9.3-i386
</pre>
as an installation source.

Upto SuSE 9.0 or 9.1 amateur radio applications were still shipping on all installation media. Later versions had them only on the DVD version. For SuSE Live CDs amateur radio software had to be installed from the internet.

SuSE has changed the "time base" in their kernels for SuSE 9.2 and 9.3 without fixing the timing for [[AX.25]] under <tt>/proc/sys/net/ax25</tt>. Without change a connection attempt will timeout after 0.3s instead of 300s.

Mailing list: [http://lists.suse.com/archive/suse-ham/ SuSE-ham] - mostly german spoken on this list.<br>
For further instructions e-mail the lists' robot suse-ham-help@suse.com.

* [http://de.opensuse.org/ openSUSE]
The PPC architecture is supported since openSUSE 10.0

=== Redhat / Fedora Core ===
None of the Redhat Linux rsp. Fedora Core distributions did every ship with amateur radio software. For [[packet radio]] even the kernel will have to be replaced with a kernel that has the necessary features built in since the distribution kernels don't come with AX.25 and the necessary drivers.
* [http://www.redhat.com/ Red Hat]

=== Ubuntu ===
[http://www.ubuntulinux.org/ Ubuntu] is debian-based and is therefore compareable to debian in respect to amateur radio support.

== Live-CDs build for amateur radio support ==
=== AR-Knoppix/Afu-Knoppix ===
[http://www.afu-knoppix.de/neu/index.php?lng=1 AR-Knoppix] current version is V3.7 dated January 2005 (based on Knoppix 3.7 from December 2004)

=== Hamshack-Hack ===
[http://hamshack-hack.sourceforge.net/ Hamshack-Hack] is based on Knoppix, too. Release:????

[[de:Distributionen]]

Distributions

2006-05-09T18:05:51Z

Tom: sync with german page

The aggregation of a Linux kernel, other system software such as a boot loader and applications are called '''distributions''' Distributions differ in their ''philosophy'' such as being for free or commercial, the targeted audience, distribution medium, added value for example in form of software for installation and system maintenance and the way that support is handled. Another differenciating factor - and the reason for the existence of this page is the degree of support for amateur radio. This page is trying to give an overview.

Live CDs for one thing are meant for trying out things for Linux beginners as they usually don't change the existing system. They also are useful for testing to what degree a computer system is supported by Linux. Live CDs are usually for the i386 architecture and are frequently based on Knoppix (http://www.knopper.net/knoppix/) which against is rooted on Debian. Live CDs are interesting because some are optimized for amateur radio.

== Full distributions ==
=== Debian ===
[http://www.debian.org/ Debian] is supporting 11 different hardware architectures and comes with a vast collection of amateur collection. Basically there are three version of Debian available:

* [http://www.debian.org/releases/woody/ oldstable] (aka Woody) http://packages.debian.org/oldstable/hamradio/<br>for the predecessor of Sarge security updates will be available until at least May 2006. For new installations generally Sarge is recommended.
* [http://www.debian.org/releases/stable/ stable] (aka Sarge) http://packages.debian.org/stable/hamradio/<br>The current and recommended Debian release. It consists of sofware which is considered stable and well tested and receives updates for usage and security critical problems. 2.4 and 2.6 kernel can be choosen during installation.
* [http://www.debian.org/releases/testing/ testing] (aka Etch) http://packages.debian.org/testing/hamradio/<br>contains software which is intended for the next stable Debian distribution. Usually works very without problems but isn't automatically updated in case of usage or security critical problems.
* [http://www.debian.org/releases/unstable/ unstable] (aka Sid) http://packages.debian.org/unstable/hamradio/<br>contains new, not yet well tested programs and versions.

Mailing list:
[http://lists.debian.org/debian-hams/ debian-hams]

=== Gentoo ===
* [http://www.gentoo.org/ Gentoo]<br>[http://www.gentoo-portage.com/media-radio/ amateur radio software]

=== Novell-SuSE / openSUSE ===
Novell-SuSE doesn't activly support amateur radio software in its distribution any more.
Despite that Novell-SuSE 9.3 and 10.0 i386 amateur radio software packages are getting maintained by JÃ¶rg, DL1BKE in his spare time. They can be installed through SuSE's system management tool YOU/YAST. All it takes for example for SuSE 9.3 is adding

<pre>
ftp://ftp.suse.com/pub/projects/ham/9.3-i386
</pre>
as an installation source.

Upto SuSE 9.0 or 9.1 amateur radio applications were still shipping on all installation media. Later versions had them only on the DVD version. For SuSE Live CDs amateur radio software had to be installed from the internet.

SuSE has changed the "time base" in their kernels for SuSE 9.2 and 9.3 without fixing the timing for [[AX.25]] under <tt>/proc/sys/net/ax25</tt>. Without change a connection attempt will timeout after 0.3s instead of 300s.

Mailing list: [http://lists.suse.com/archive/suse-ham/ SuSE-ham] - mostly german spoken on this list.<br>
For further instructions e-mail the lists' robot suse-ham-help@suse.com.

* [http://de.opensuse.org/ openSUSE]
The PPC architecture is supported since openSUSE 10.0

=== Redhat / Fedora Core ===
None of the Redhat Linux rsp. Fedora Core distributions did every ship with amateur radio software. For [[packet radio]] even the kernel will have to be replaced with a kernel that has the necessary features built in since the distribution kernels don't come with AX.25 and the necessary drivers.
* [http://www.redhat.com/ Red Hat]

=== Ubuntu ====
[http://www.ubuntulinux.org/ Ubuntu] is debian-based and is therefor compareable to debian respective to amateur radio support.

== Live-CDs build for amateur radio support ==
=== AR-Knoppix/Afu-Knoppix ===
[http://www.afu-knoppix.de/neu/index.php?lng=1 AR-Knoppix] current version is V3.7 dated January 2005 (based on Knoppix 3.7 from December 2004)

=== Hamshack-Hack ===
[http://hamshack-hack.sourceforge.net/ Hamshack-Hack] is based on Knoppix, too. Release:????

[[de:Distributionen]]

PR430

2006-05-09T17:01:53Z

Tom: typos

The '''PR430''' is a small device integrating a [[TNC]] and a 70cm 6W-transceiver optimized for [[packet radio]] (1200 Bd. AFSK & 9600 Bd. FSK) use. It is connected to the host system through a [[RS232]] interface using the common 9-pin sub-D connector. It is running enhanced [[6pack]] as the line protocol. <br> The PR430 can also be used as a FM-TRX and as [[POCSAG]]-TX. It was developed by the German company SR-Systems.

== Linux support ==
Currently Linux does not support enhanced 6pack, therefor special drivers patches are needed. The patch is available at http://www.linux-mips.org/pub/linux/mips/people/ralf/pr430. The enhanced 6PACK driver is configured via [[sysfs]]. To configure the (first) device to a receive frequency of 438.350MHz with a shift of -7.6MHz use the following commands:
<code><pre>
echo 438350000 > /sys/class/net/sp0/tnc/qrg
echo -7600000 > /sys/class/net/sp0/tnc/shift
</pre></code>

The FM-Transceiver and POCSAG transmitter mode are currently not supported.

== See also ==
* [http://www.sr-systems.de/V02/content.php?show=PR430&lng=en&style=std SR-Systems PR430 page]
* [http://www.adacom.org/index.php?option=com_content&task=view&id=56&Itemid=9 The PR430 as POCSAG transmitter] (German)

[[de:PR430]]

PR430

2006-04-29T14:15:24Z

Tom: URL to SR-Systems, typos etc.

The '''[http://www.sr-systems.de/V02/content.php?show=PR430&lng=en&style=std PR430]''' is a small device integrating a [[TNC]] and a 70cm 6W-transceiver optimized for [[packet radio]] (1200 Bd. AFSK & 9600 Bd. FSK) use. It is connected to the host system through an [[RS232]] interface using the common 9-pin sub-D connector. It is running enhanced [[6pack]] as the line protocol. <br> The PR430 can also be used as a FM-TRX and as [[POCSAG]]-TX.

== Linux support ==
Currently Linux does not support enhanced 6pack, therefor special drivers patches are needed. The patch is available at http://www.linux-mips.org/pub/linux/mips/people/ralf/pr430.

[[de:PR430]]

Main Page

2006-04-25T12:54:31Z

Tom: added "KISS"

__NOEDITSECTION__
{| style="width:100%;"
|-
|
<div style="background:#e0e0ff;border:1px solid #cfcfff;padding:1em;padding-top:0.5em;padding-bottom:0.5em; color:black;">
<big>'''Protocols'''</big><br>
[[AX.25]] – [[NET/ROM]] – [[ROSE]] – [[6PACK]] – [[KISS]] – [[TCP/IP]]

<big>'''Net Resources'''</big><br>
[[Net_Resources#Mailing_Lists|Mailing Lists]] – [[Net_Resources#IRC|IRC]] – [[Net_Resources#Convers|Convers]] – [[CVS]]

<big>'''Misc'''</big><br>
[[Satellite Software]]  – [[Shack Automation Software]] – [[Design and Construction Software]] – [[Training and Educational Software]]

<big>'''Applications'''</big><br>
[[Packet Radio]] – [[Morse Code]] – [[PSK31]] – [[AMTOR]] – [[PACTOR]] – [[SSTV]] – [[FAX]]
|}

{| style="width:100%;"
|- style="vertical-align:top;"
| style="width:66%;background:#ffe0c0;border:1px solid #ffd0b0;padding:1em; color: black;" |
== News ==
2006-04-19 Start German version of the site.

2006-04-15 The former non-public ham.linux-mips.org moves to it's new home at www.linux-ax25.org.

== Old News ==
[[2005]]

| style="background:#e0e0ff;border:1px solid #c6c9ff;padding:1em; color: black;" |
<div style="text-align: center;">
== Latest Versions ==
Linux 2.6.16<br>
Linux 2.4.33<br>
</div>

[[de:Hauptseite]]

DPTNT Terminal and DPBOX BBS

2006-04-21T13:48:17Z

Tom: /* Authors */

== Authors ==
Mark Wahl, DL4YBG, DL4YBG@DB0GR.#BLN.DEU.EU, wahlm@berlin.snafu.de and Joachim Schurig, DL8HBS, DL8HBS@DB0GR.#BLN.DEU.EU, jschurig@zedat.fu-berlin.de

== Description ==
A suite of programs that provide BBS and Terminal programs for Linux.

== Status ==
Stable and working.

== System requirements ==
[[TNC]] supporting WA8DED hostmode or [[KISS]] protocols.

== Detail ==
TNT is a full featured hostmode terminal program. Compiling it on Linux is as difficult as untarring the source and typing `make'. It provides both a `dumb' terminal and X11 version. It comes with some comprehensive documentation which describes its features in some detail. Its main features are:

=== Multiple sessions ===
TNT supports multiple packet radio connections on virtual screens that you can switch between. Each session window provides split screen (seperate transmit and receive text) operation with a status line. Commands can be entered in either a command session, or in any terminal session using a command key. Each of the virtual screens can be larger than the physical screen and can be scrolled around.

=== Data capture, file transfer and logging ===
A number of options are available for logging received text to files. You can log transmit, receive or both to a log file. You can overwrite or append received data to existing files. You can use the `autobin' protocol to transmit or receive binary files.

=== Remote Shell operation ===
You can provide a shell to remote users so that they can access other programs on your computer. You can also run a program and direct its input/output to a channel so that users can use it.

=== Redirection of devices to a channel ===
TNT allows you to redirect input/output from a channel to a device, a modem for example.

=== Umlaut conversion ===
TNT provides umlaut conversion if necessary.

=== Remote mode ===
Remote users can issue command themselves if allowed to do so.

=== Socket mode ===

You can configure tnt so that it opens a socket for users to telnet to that allows them operation just as you have from the console. This is useful where your linux machine is on an ethernet and you want other terminal on the net to have use of your radio.

DPBOX is a full featured BBS supporting the following features:

* F6FBB, W0RLI, TheBox style forwarding protocols.
* 8-bit transparent handling of messages using AutoBIN protocol.
* BBS data compressed to save space on disk, forwarding and downloading.
* "Live message capture" off BBS frequency, saves network traffic.
* PACSAT style bulletin broadcast transmitter and receiver.
* up to 200 simultaneous users.

== Where and How to obtain it ==
TNT by itself is available by anonymous ftp from: ftp.funet.fi. The DPTNT package may be found at: ftp.funet.fi, or ftp.tapr.org, or ftp.ucsd.edu.

The Home Pages of the developers are at: DL4YBG and DL8HBS

== License ==
The TNT and DPBOXT programs are covered by the GNU Public License. The TFKISS program is covered by ALAS (a german license for Amateur Radio use), and the DPBOX program is freely distributable for Amateur Radio use.

== See also ==
* [http://home.snafu.de/wahlm/ DPTNT & DPBOX BBS package] TNT (outdated)
* [http://www.wspse.de/WSPse/Packet.php3?lang=en TNT V1.91] (mostly in German)

KISS

2006-04-19T14:09:47Z

Tom: URL to KA9Qs' kiss paper and fix some typos

[http://www.ka9q.net/papers/kiss.html '''KISS'''] (Keep It Simple, Stupid) is probably the most common protocol used to communicate between host systems and [[TNC]]s. It's simplicity has also made it a popular protocol for inter-application communication over pseudo-ttys. The protocol was originally developed by Phil Karn KA9Q. Due to better control of the transmitter and realtime communication [[6PACK]] is the prefered protocol for use with TNC.

== Configuring KISS on Linux ==

<pre>
Kernel Compile Options:

Amateur Radio support --->
[*] Amateur Radio support
--- Packet Radio protocols
<*> Amateur Radio AX.25 Level 2 protocol
...
AX.25 network device drivers --->
--- AX.25 network device drivers
<*> Serial port KISS driver
...
</pre>

Probably the most common configuration will be for a [[KISS]] [[TNC]] on a serial port. You will need to have the TNC preconfigured and connected to your serial port. You can use a communications program like minicom or seyon to configure the TNC into kiss mode.

To create a KISS device you use the kissattach program. In it simplest form you can use the kissattach program as follows:

<pre>
# /usr/sbin/kissattach /dev/ttyS0 radio 44.135.96.242
# kissparms -p radio -t 100 -s 100 -r 25
</pre>

The kissattach command will create a KISS network device. These devices are called `ax[0-9]'. The first time you use the kissattach command it creates `ax0', the second time it creates `ax1' etc. Each KISS device has an associated serial port.

The kissparms command allows you to set various KISS parameters on a KISS device.

Specifically the example presented would create a KISS network device using the serial device `/dev/ttyS0' and the entry from the /etc/ax25/axports with a port name of `radio'. It then configures it with a txdelay and slottime of 100 milliseconds and a ppersist value of 25.

Please refer to the man pages for more information.

It is possible and occasionally useful to manually reissue the kissparms command, with your desired parameters as shown above, if you occasionally need to reload the specific parameters into a TNC that has had to be restarted or power-cycled, and the parameters are those that are not default for what the TNC comes up with when brought up cold. It can also be useful to include such a kissparms command on a crontab line so this happens periodically if the station is unattended and something goes wrong with the TNC. Kissparms output to the TNC also is displayed by the listen(1) monitoring command, if running with the -a switch which displays outgoing as well as incoming packets. -WB5AOH-

== Configuring for Dual Port TNC's ==

The mkiss utility included in the ax25-utils distribution allows you to make use of both modems on a dual port TNC. Configuration is fairly simple. It works by taking a single serial device connected to a single multiport TNC and making it look like a number of devices each connected to a single port TNC. You do this before you do any of the AX.25 configuration. The devices that you then do the AX.25 configuration on are pseudo-TTY interfaces, (/dev/ttyq*), and not the actual serial device. Pseudo-TTY devices create a kind of pipe through which programs designed to talk to tty devices can talk to other programs designed to talk to tty devices. Each pipe has a master and a slave end. The master end is generally called `/dev/ptyq*' and the slave ends are called `/dev/ttyq*'. There is a one to one relationship between masters and slaves, so /dev/ptyq0 is the master end of a pipe with /dev/ttyq0 as its slave. You must open the master end of a pipe before opening the slave end. mkiss exploits this mechanism to split a single serial device into separate devices.

Example: if you have a dual port TNC and it is connected to your /dev/ttyS0 serial device at 9600 bps, the command:

<pre>
# /usr/sbin/mkiss -s 9600 /dev/ttyS0 /dev/ptyq0 /dev/ptyq1
# /usr/sbin/kissattach /dev/ttyq0 port1 44.135.96.242
# /usr/sbin/kissattach /dev/ttyq1 port2 44.135.96.242
</pre>

would create two pseudo-tty devices that each look like a normal single port TNC. You would then treat /dev/ttyq0 and /dev/ttyq1 just as you would a conventional serial device with TNC connected. This means you'd then use the kissattach command as described above, on each of those, in the example for AX.25 ports called port1 and port2. You shouldn't use kissattach on the actual serial device as the mkiss program uses it.

The mkiss command has a number of optional arguments that you may wish to use. They are summarized as follows:

; -c : enables the addition of a one byte checksum to each KISS frame. This is not supported by most KISS implementations, it is supported by the G8BPG KISS ROM.
; -s <speed> : sets the speed of the serial port.
; -h : enables hardware handshaking on the serial port, it is off by default. Most KISS implementation do not support this, but some do.
; -l : enables logging of information to the syslog log file.

6PACK

2006-04-18T20:48:30Z

Tom: added external link (hb9jnx) and one typo less

==6PACK a "real time" PC to TNC protocol==

by Matthias Welwarsky, DG2FEF @ DB0KLN.DEU.EU, Am Pelz 77c, 64295 Darmstadt, Germany<br/>
translated by [http://www.baycom.org/~tom/ Thomas Sailer], HB9JNX @ HB9W.CHE.EU, WeinbergstraÃŸe 76, 8408 Winterthur, Switzerland<br/>
converted to HTML and indexed by Alexander Stohr, DG3MMF @ OE9XPI.AUT.EU, SchÃ¶nauer Str. 5, 88131 Lindau, Germany<br/>

===Introduction===

During the development of the PC/FlexNet software package, there was a strong desire to use the existing hardware, especially the very widespread TNC2, which populates almost every packet radio station nowadays. Sysops of TheNetNode digipeaters also showed much interest, since many TNN nodes use TNC2 devices connected using a KISS token ring.

Existing TNC protocols have severe disadvantages. The KISS protocol does not allow much influence on the channel access. This prevents the implementation of alternative channel access schemes, such as DAMA or OPTIMA. The so-called "WA8DED Hostmode" does not provide data transparency, and its throughput is very limited.

The basic concept of 6PACK was developed at the end of 1993 by Ekki Plicht, DF4OR, Henning Rech, DF9IC and Gunter Jost, DK7WJ. It was further developed for use in the PC/FlexNet software package by Gunter Jost, DK7WJ, and Matthias Welwarsky, DG2FEF. The protocol then did not support multiple TNCs connected in a ring topology. It only allowed for one TNC per asynchronous serial interface. It was then found that a ring topology required different protocol features than a simple point to point connection.

The current revision of the protocol has many additional features compared to the first version. It now allows a ring topology of up to eight TNCs connected to a single asynchronous serial interface of the computer. The ring wiring is hardware compatible with the existing token rings used by the "TheNetNode" software.

6PACK provides:

* Data transparency
* predictable capacity requirements on the ring
* data and realtime information is distinguished
* fast response to changing channel usage, even under high loading and multiple TNCs on the ring
* automatic ring setup replaces a channel number "patched" into the (EP)ROM
* data is protected by a checksum

===Basics===

The asynchronous serial interface parameters are: 8 data bits, 1 stop bit, no parity bit. The baud rate on the ring must be at least twice the highest HDLC bit rate of the TNCs connected to the ring. RTS/CTS is ignored, RTS however should toggle about every 10ms to reset an eventually connected hardware watchdog. The TNC software should implement another watchdog which terminates any transmission if no further data is received from the PC. To reset this watchdog, any command sent to the TNC will do, for example an LED control command. Bits 6 and 7 of every byte distinguish between channel data and control codes.

{| border="1" cellspacing="0" cellpadding="3"
! 76 543210
! Meaning
|-
| 00 xxxxxx
| channel data
|-
| 01 xxxccc
| status/protocol data
|-
| 1x xxxccc
| status/protocol data
|-
| x
| data
|-
| c
| channel address
|}

Control codes always consist of only one byte. Code groups of more than one byte are never used. Therefore, control codes require little transmission capacity. Control codes are completely independent from previous or following control codes. This makes the protocol very robust. An exception to this rule is, as in the KISS protocol, the "start/end" command, which always belongs to a data packet, and the channel data itself. Because two bits are used to distinguish between channel data and control codes, only six bits per byte are available for channel data. Therefore, three data bytes have to be encapsulated into four "6PACKs", according to the following scheme. Note that a channel data byte does not correspond directly to a byte on the asynchronous serial interface.

{| border="1" cellspacing="0" cellpadding="3"
!
! 1st 6PACK
! 2nd 6PACK
! 3rd 6PACK
! 4th 6PACK
|-
| Codes
| 00xx.xxxx
| 00xx.yyyy
| 00yy.yyzz
| 00zz.zzzz
|-
| Bits
| 54.3210
| 76.3210
| 76.5410
| 76.5432
|}

The symbols "x", "y" and "z" with the corresponding bit numbers represent the channel data. This rather complex scheme was chosen since it requires the least possible shift operations to extract the channel data from the 6PACKs.

The fast transmission of real time events is achieved by using priority codes. The TNC for example transmits an appropriate command code at every change of the DCD line. Additionally, the TNC sends the DCD state about every second to allow recovering of a potentially lost command code.

The coding of the command codes is shown in Table 1. The code 0xC0 (1100 0000) is not used in 6PACK; this should prevent an accidentally connected KISS TNC from sending.

===The data transmission between TNC and PC===

The following simple rules govern the data transmission between the TNCs and the PC.

* Channel data is always transmitted in whole packets. Every packet is enclosed with a pair of "start/end" commands. The channel number carried in the starting "start/end" command defines the source or destination of the packet. The first data byte carries the TX delay, either the TX delay that should be used by the transmitter, or the one measured by the receiver, depending on the data direction. The last data byte carries the checksum. It is adjustet so that the sum over the whole packet (including TX delay and checksum byte) plus the channel number add up to 0xFF (8bit two's complement arithmetic)
* Priority commands must be processed before ordinary data. If a TNC receives a priority code with an address that does not match its own, it must immediately retransmit the command, even if it is just sending a packet.
* A packet of channel data must not be interrupted by another packet of channel data. The TNC may only place its own packets onto the ring either before or after packets from other TNCs.

Each packet of channel data has the following structure:

{| border="1" cellspacing="0" cellpadding="3"
! SOF
! TXD
! DATA
! CS
! SOF
|}

where:

; SOF: Start/end of Frame
; TXD: TX delay in units of 10ms
; DATA: Channel data
; CS: Checksum byte

This structure results after extracting the data from the 6PACKs. The TX delay can be reconstructed only after the second 6PACK with channel data.

{| border="1" cellspacing="0" cellpadding="3"
! HÂÂÂ ÂÂÂL
! command
! direction
|-
| 0100 0ccc
| start/end of frame
| PC <--> TNC
|-
| 0100 1ccc
| TX underrun
| TNC --> PC
|-
| 0101 0ccc
| RX overrun
| TNC --> PC
|-
| 0101 1ccc
| RX buffer overflow
| TNC --> PC
|-
| 011x yccc
| LED: STA=x; CON=y
| PC --> TNC
|-
| 10xy zccc
| priority message:<br/> x = TX counter + 1<br/> y = RX counter + 1<br/> z = DCD state
| <br/>PC <--> TNC<br/> TNC --> PC<br/> TNC --> PC
|-
| 1100 0000
| not used (KISS FEND)
|
|-
| 1110 0ccc
| send calibration pattern for 15s<br/> calibration terminated
| PC --> TNC<br/> TNC --> PC
|-
| 1110 1ccc
| TNC address
| PC <--> TNC
|-
|}

Table 1

=== Transmission sequence on the radio port ===

Transmission on the radio port take place according to the following scheme:

# The PC sends a "TX counter + 1" command to the TNC. The TNC then keys the transmitter (i.e. it activates the PTT line) and increments an internal counter. The PC also increments an internal counter associated with that TNC. This counter serves the PC as a PTT indicator.
# the PC sends the packet onto the ring
# As soon as the TX delay value arrives in the TNC, it decides whether enough time has passed already since the transmitter was keyed on. If not, keying up the transmitter is continued until the specified amount of time passed. When the next data byte arrives, the transmission begins, even if the whole packet has not arrived yet.
# If the TNC receives the "start/end" command and the received checksum was bad, it must send an ABORT sequence on the radio port.
# As soon as the TNC completes transmitting a packet on the radio port, it sends a "TX counter + 1" command to the PC and decrements its internal counter. Because every packet is preceded by a "TX counter + 1" command from the PC, the TNC always knows how many packets will follow in the current transmission. The transmitter must stay keyed until the last packet is sent.
# The PC receives the "TX counter + 1" command from the TNC and decrements its associated internal counter. If this counter reaches zero, then the transmission terminates.

The transmission of the channel data packets from the TNC to the PC takes place similarly, with the exception that the PC does not acknowledge a received packet. Every packet the TNC receives on its radio port is sent onto the ring, preceded by an "RX counter + 1" command.

===Automatic configuration of the TNC addresses===

Automatic configuration of the TNC addresses is achieved by the following simple scheme.

# The TNC receives an address command (1110 1ccc) and sets its own address to the value contained in the command (the ccc bits).
# The TNC increments the address contained in the command by one and retransmits the command.

Since every TNC on the ring behaves according to these rules, TNC addresses are allocated sequentially. The command transmitted by the last TNC and received by the PC contains the number of connected TNCs.

===KISS versus 6PACK===

6PACK provides some advantages over KISS, most notably the ability to transmit real time data and thus the ability to implement the channel access algorithm in the PC.

KISS achieves data transparency by prefixing some data bytes by an escape code. This means that the transmission capacity needed to transmit a data packet depends largely on the contents of the packet. In the worst case, twice the bandwith is needed. With 6PACK, the transmission capacity needed is exactly predictable, if one neglects the real time commands inserted into the data stream.

If one continues the comparison and compares 6PACK rings to KISS token rings, the advantages of 6PACK become even clearer. With a KISS token ring, the response time of the system depends on the loading of the ring. Since the token ring does not transmit DCD and PTT states, each TNC needs to implement its own channel access algorithm, and usually a rather primitive SlotTime/p-Persistence algorithm is used. Also, there is no timing relation between the receipt of a packet over the air and the arrival of the packet in the PC. The PC does not know when the packet is actually sent. (Note by the translator: When the FRACK timer expires and the PC retransmits a frame, the original frame may still wait for transmission, since the channel was busy all the time. Then the retransmission of the frame produces additional unnecessary load on an already congested channel)

This usually leads to the transmission of frames with outdated sequence numbers and to strange effects if one tries to implement a DAMA master on a KISS token ring. With high HDLC bit rates and high load on the ring, the transmitter may be interrupted between packets, which leads to a much increased collision probability.

6PACK provides no mechanisms which would allow the TNC to implement its own channel access. Therefore, the channel access has to be done in the PC. This is a significant advantage, especially on half duplex links.

Short response times, which are needed by, for example, a DAMA slave, cannot be achieved with KISS. The transmitter keying is always delayed by the time it takes to transmit the packet on the asynchronous serial interface.

With 6PACK, real time data and channel data are distinguishable. Therefore, the delay of real time data does not depend on the ring loading, and it can be calculated from the ring bit rate and the number of TNCs on the ring. Each TNC delays the byte by between 10 and 20 bits, which is 260 to 520 Âµs at 38.4kBit/s. The longest possible delay at 38.4kBit/s is therefore 8 * 520 Âµs = 4.2 ms.

This means that it does not take more than 4.2 ms to key the transmitter of a particular TNC, or to communicate the DCD state to the PC. This way, even a ring of TNCs may be controlled quite precisely, but the additional delay of a ring may increase the collision probability slightly on a half duplex channel.

A flaw of 6PACK is that the TX delay may be longer than requested. This happens every time a packet is delayed more than the requested TX delay compared to its preceding "TX counter + 1" command. However, measures should be taken to prevent the peer station from complaining about the too long TX delay.

Last, but not least: Unlike with KISS, the TNC LEDs can be controlled by the host PC directly. They are used just like the LEDs on the RMNC3 card.

===Some remarks from the translator===

http://private.freepage.de/alexs/xfr/flexnet/6pack_en/figure1.gif

Figure 1 shows the wiring of a TNC ring.

FlexNet allows different channel access algorithms to be used. It may use a modified p- persistence algorithm, [[DAMA]], or [[OPTIMA]] in the future. FlexNet allows even multiple data rates and modulation schemes to share one radio channel. For example, combined 1200 Baud AFSK / 9600 Baud FSK user accesses can be found in Europe, since it is often not possible to get different frequencies for both modes, because the 70cm and 23cm bands are very crowded. In this case, a 1200 baud AFSK and a 9600 baud FSK modem are connected to the same transmitter in parallel. Thus the channel access algorithm spans multiple channels. In PC/FlexNet, the channel access for radio channels is done in the L2 kernel. So L1 drivers and 6PACK TNCs must not implement their own channel access algorithm.

TX delay is the time between keying the transmitter and starting to send the first packet. This time allows the radio to start the transmitter. HDLC flags are usually sent during this time. TX delay is specified in 10ms units. FlexNet also monitors the TX delay of the other stations on the channel, and complains if a station uses an excessively long TX delay (more than 100ms in excess to what the transmitter needs). PC/FlexNet L1 drivers and thus 6PACK TNCs should listen for a series of HDLC flags preceding a data packet and report the duration of this sequence in the TX delay byte of the received data packet. Note that only error free reception of the flags should be accepted. In the unlikely event that the hardware does not support the measuring of the TX delay, zero should be returned. Zero may also be returned for every packet other than the first of a particular transmission. If, due to overload on the ring, the required TX delay cannot be met, the sending station must make sure the peer does not complain about the long TX delay. This can be done by inserting an ABORT sequence, for example.

Note that for the sake of fast retransmission of priority commands, hardware FIFOs in the asynchronous serial interface should not be used.

The translator would like to thank Matthias Welwarsky DG2FEF and Gunter Jost DK7WJ for the assistance, and Esther Oswald for correcting this translation.

===Related literature===

[1] Karn, Phil KA9Q, and Mike Chepponis K3MC, The KISS TNC: A simple Host-to-TNC communications protocol, 1990

[2] Welwarsky, Matthias DG2FEF, DAMA und OPTIMA, TheFirmware Version 2.7, 1994

Packet Radio

2005-08-11T16:26:27Z

Tom:

The term [[packet radio]] is generally used to mean the same as [[AX.25]]. Here's a list of packet-related Linux sites and software packages:

* AX25-HowTo
** [http://www.tldp.org/HOWTO/AX25-HOWTO/ V2.0] 2001-09-19
** [http://www.linuxhaven.de/dlhp/HOWTO/DE-AX25-HOWTO.html V1.6-2] 1999-07-08, german version
* [http://www.swiss-artg.ch/xnet/ (X)Net-Software] german site
* [[monax25]]
* [[splitscreen]]
* [[talk-ax25]]
* [[7Plus]]
* [[TNOS]]
* [[N0ARY Packet BBS]]
* [[LBBS - Linux BBS message gateway]]
* [[MBL/RLI message to NNTP and email converter]]
* [[Packet Cluster Node Software]]
* [[Single Floppy disk AX.25 router]]
* [http://home.snafu.de/wahlm/ DPTNT & DPBOX BBS package] TNT outdated ->
* [http://www.wspse.de/WSPse/Packet.php3?lang=en TNT V1.91] (mostly in German)
* [[IPIP encapsulation daemon]]
* [[AXIP encapsulation daemon]]
* Ping-Pong Convers Server software
**[http://x-berg.in-berlin.de/cgi-bin/viewcvs.cgi/ampr/conversd-saupp/ DL9SAUs' saupp]
* [[RSPF Daemon]]
* [[Michael Westfall's ttylink Daemon]]
* [[Craig Small's ttylink Daemon]]
* [http://radio.linux.org.au/ Hamsoft Database]