LinuxHam - User contributions [en]

Main Page

2021-08-25T21:03:13Z

DL5RB: Remove link to the French version. Sadly it was never actively used.

__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]] – [[GIT]]

<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 ==
{| border="0" cellpadding="4" cellspacing="0" valign="top" style="margin: 1em 1em 1em 0; background: #ffe0c0; border-collapse: collapse;"
|-valign="top"
| 2021-08-24
| linux-ax25.org is once again undergoing massive updates all across resulting in repeated downtime.
|-valign="top"
| 2015-04-30
| linux-ax25.org is undergoing massive updates of its slightly dated infrastructure. As the result there will outages of services or the entire system over several days.
|-valign="top"
| 2011-11-04
| All SSL certificates for linux-ax25.org have been refreshed. As a reminder, linux-ax25.org uses [http://www.cacert.org CAcert] certificates and the root certificate for CAcert.org (available [http://www.cacert.org/index.php?id=3 here] is not included with all operating systems and browsers yet so you may have to manually install it if you want to use linux-ax25.org's services encryptedly.
|-valign="top"
| 2011-09-07
| The recent [http://lwn.net/Articles/457142/ compromise] of a kernel.org servers has resulted in some of kernel.org's servers providing DNS service to linux-ax25.org becoming unavailable. A temporary solution is now in place.
|-valign="top"
| 2011-08-18
| A fix for [http://www.cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2011-2910 CVE-2011-2910] ([https://www.redhat.com/security/data/cve/CVE-2011-2910.html Red Hat CVE database], [https://bugzilla.redhat.com/show_bug.cgi?id=730783 Red Hat Bug 730783], [https://bugzilla.redhat.com/show_bug.cgi?id=730784 Red Hat Bug 830784], [http://security-tracker.debian.org/tracker/CVE-2011-2910 Debian security tracker], [http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=638198 Debian Bug 638198]) has been checked into [[CVS]]. The impact of this issue is low as the circumstances that trigger the issue should not normally encountered on a correctly configured system. See also related [http://www.openwall.com/lists/oss-security/2011/08/ discussion] on the oss-security mailing list under the subject "CVE request (and disclosure): ax25d missing setuid return code check".
|-valign="top"
| 2010-06-10
| Linux-ax25.org now is SSL-enabled.
|-valign="top"
| 2010-03-29
| Due to hardware defects the site was running from an outdated copy for a while. The problem has been rectified now. Sorry for the inconvenience.
|-valign="top"
| 2009-12-15
| Since about two weeks linux-ax25.org is suffering from occasional ISP outages. We apologise.
|-valign="top"
| 2009-12-08
| On Friday, 2009-12-11 between 12:00 and 18:00 UTC there is a likely outage for exchange of a broken electricity meter.
|-valign="top"
| 2009-11-20
| linux-ax25.org's software will be upgraded during the next days resulting in downtime of a few hours.
|-valign="top"
| 2009-07-13
| The ISP of linux-ax25.org has announced some scheduled downtime for 2009-08-12. The exact time might change at short notice.
|-valign="top"
| 2009-05-31
| Linux-ax25.org now has an ftp site [ftp://ftp.linux-ax25.org ftp.linux-ax25.org] which hosts historic and current versions of [[ax25-apps]], [[ax25-tools]] and [[libax25]].
|-valign="top"
| 2009-05-29
| The site has moved to a new temporary server system.
|-valign="top"
| 2006-04-19
| Start German version of the site.
|-valign="top"
| 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 ==
[http://www.linux-ax25.org/pub/ax25-apps/ax25-apps-{{Latest-stable-ax25-apps-version}}.tar.gz AX.25 Apps {{Latest-stable-ax25-apps-version}}]<br>
[http://www.linux-ax25.org/pub/ax25-tools/ax25-tools-{{Latest-stable-ax25-tools-version}}.tar.gz AX.25 Tools {{Latest-stable-ax25-tools-version}}]<br>
[http://www.linux-ax25.org/pub/libax25/libax25-{{Latest-stable-libax25-version}}.tar.gz AX.25 Library {{Latest-stable-libax25-version}}]<br>
</div>

[[de:Hauptseite]]

Main Page

2021-08-24T21:48:25Z

DL5RB:

Template:Latest-stable-ax25-apps-version

2019-04-03T22:30:49Z

DL5RB: ax25-apps 0.0.8-rc5

0.0.8-rc5

Template:Latest-stable-ax25-tools-version

2019-04-03T22:30:46Z

DL5RB: ax25-tools 0.0.10-rc5

0.0.10-rc5

Template:Latest-stable-libax25-version

2019-04-03T22:30:41Z

DL5RB: libax25 0.0.12-rc5

0.0.12-rc5

GIT

2016-11-24T19:05:10Z

DL5RB: /* See also */ Fix stale URLs, switch to protocol agnostic URLs

<h4 style="background-color:#efefff;border-bottom: 0px;border: 1px solid #1e90ff;text-align:left;padding-top:4px;margin-top:5px; ">
::We will hereby start scouring the net for people who say git is hard to
::understand and use, and just kill them. They clearly are just polluting
::the gene pool.
:
::::Linus
</h4>
<div style="padding-left:2em;padding-right:2em;">

All right, we're not quite that bad. Yet. These days the Linux world has largely switched to '''GIT''' as its SCM. Git is a fairly low-level thing, more the backing store of an SCM - or ''plumbing'' in Linus's words - than a full-blown SCM but it's growing up very quickly. Linux-ax25.org has used [[CVS]] since [[2001]] and so naturally is a little more conservative in switching to a new tools as we don't want to drop all the history that's hidden in these trees.

== Accessing GIT repositories ==
The GIT repositories can be accessed by <tt>git://git.linux-ax25.org/pub/scm</tt>. The http and rsync protocols are also supported but not recommended. Here are two example commands using the <tt>libax25.git</tt> repository; you can substitute the name of another repository (see further below) for <tt>libax25.git</tt> in the examples.

=== Cloning a repository ===

git clone git://git.linux-ax25.org/pub/scm/libax25

This will create a new directory under the current working directory called linux.
To use a different name specify it on the command line as an additional argument and it will become the target.
Here is an alternate form of the command which creates a local directory called libax25.git instead of libax25.

git clone git://git.linux-ax25.org/pub/scm/libax25 linux.git

=== Updating a repository ===
When the repository was cloned the upstream URL was saved into the file <tt>.git/remotes/origin</tt>.
This is the default location for git to pull updates.
If you wish to modify the default URL you may edit that file directly.

From the top directory of your local repository (that is, the directory which contains the <tt>.git</tt> subdirectory) run the following command:

git pull

This will pull updates from the repository and merge them into your local repository.

It is also possible to specify an alternate URL by specifying it on the command line.

git pull git://git.linux-ax25.org/pub/scm/libax25

Typing in URLs can be tedious. You may create shortcuts to repeatedly used URLs by saving them in a remotes file.
Alternate URLs may be saved in the <tt>.git/remotes/REMOTENAME</tt> file where the <tt>REMOTENAME</tt> string is the name that you wish to call that source location. Let's say that that you wanted to clone this long URL
<tt>git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git</tt> but find that a lot to type repeatedly.
If that is specified in a remotes file <tt>linus</tt> then the following command would pull from it. <tt>git pull linus</tt>

=== Which git protocol to use ===
Generally these days the git protocol (the <tt>git://</tt>) URLs) is the prefered protocol.
* git Git's own protocol which tries to heavily optimize the amount of bandwidth used and thus is generally very efficient for updates. An issue with the git protocol is its use of TCP port 9418 which [[Wikipedia:Paranoia|paranoid]] firewall admins may have blocked.
* http Rather inefficient usage of bandwith and CPU but since http is generally enabled in firewalls it exists for those poor souls suffering from [[Wikipedia:Fascist|fascist]] firewall admins.
* https More secure than http but otherwise pretty much the same thing. linux-ax25.org uses SSL certificates from cacert.org and CACERT's root certificate is not included with most operating systems. A notable exception is Debian however. So if attempts to access a linux-ax25.org repository via https fail with an error message about an invalid SSL certificate, you can:
** use one of the other protocols listed in this section
** disable the verification of the SSL certificate. On a UNIX or Linux type of system you do this by setting the GIT_SSL_NO_VERIFY variable, for example: <code>GIT_SSL_NO_VERIFY=yes git clone https://git.linux-ax25.org/pub/scm/libax25.git</code>. Note that this disables the verification of the certificate thus leaving you vulnerable to the same attacks as plain http.
** manually import the root certificate. The preferable but also most complicated approach.
* rsync The oldest git protocol, deprecated and supposed to eventually go away. Suffers from a low probability race condition. Its advantage is the lowest CPU usage on the server side. Also some firewalls that don't allow git git protocol will allow rsync. Not recommended for pulling or fetching. Heck, it really should be considered the last alternative. Rsync is not what in git parlance is called an intelligent transport which means that all new pack files on the server side will be transfered to the client even if only a single object from the pack would need to be transfered.

== Status of CVS to GIT conversion ==

All development has been moved to git. For the time being the CVS Server is still running to maintain the history and help users with existing CVS checkouts however there will be ''no'' more CVS checkins.

It has been attempted to convert the entire history of CVS with some of the details that CVS doesn't record manually restructed and the tarball history which predates the CVS history. Various generated files, even some binaries were checked into the CVS history and often these files were deleted or regenerated for the distributed archives, so there is no 100% equivalence between the tagged versions and corresponding tarballs.

== Checking out a tagged release with git ==
This is how to list the available tags:

<pre>
[ralf@dea linux-git]$ git tag -l
$ git tag -l
libax25-0.0.10
libax25-0.0.11
libax25-0.0.12-rc1
libax25-0.0.12-rc2
libax25-0.0.12-rc3
...
</pre>

The actual list of tags is longer. Okay, so let's assume we want to checkout the <tt>libax25-0.0.11</tt> release:

<pre>
[ralf@dea linux-git]$ git checkout -b my-0.0.11 libax25-0.0.11
</pre>

What this exactly does is creating a ''new'' branch named <tt>my-0.0.11</tt> at <tt>linux-0.0.11</tt> and checking out it's HEAD.

== Gitweb ==
Gitweb allows simple browsing of git repositories in a web browser. Git web is available at http://git.linux-ax25.org.

== See also ==
* [[Compilation]] How to build <tt>libax25</tt>, <tt>ax25-tools</tt> or <tt>ax25-apps</tt> from source.
* [//kernel.org/pub/software/scm/git/docs/gittutorial.html A short git tutorial] at [//www.kernel.org kernel.org]
* [//git-scm.com The GIT homepage]
* [//www.ibm.com/developerworks/library/l-vercon/ A nice SCM article] by IBM giving an overview what SCM is and several popular SCM systems.

[[Category:git]]

BPQ

2015-07-21T16:47:46Z

DL5RB: Some more technical details

''Bpqether'' is a Linux kernel driver which allows the use of [[AX.25]] over ethernet-like networks such as Ethernet, 802.11 family Wifi networks but also virtual devices such as the Linux software bridge, VLANs and more.

== Unsupported networking technologies ==
Technologies which are similar to Ethernet but not supported are [[FDDI]], [[HIPPI]]. It might be a matter of testing but as long as this has not positively tested the kernel will not allow configuring BPQ over these devices.

== Configuration ==
Up to Linux 4.1 the behaviour is that when the bpqether driver is built into the kernel or loaded as a module a network interface named bpq followed by a small decimal number is created for every ethernet-like device. Details can be seen in /proc/net/bpqether which might look like:

<pre>
dev ether destination accept from
bpq5 vnet1 ff:ff:ff:ff:ff:ff *
bpq3 vbridge ff:ff:ff:ff:ff:ff *
bpq2 virbr0 ff:ff:ff:ff:ff:ff *
bpq1 wlan0 ff:ff:ff:ff:ff:ff *
bpq0 eth0 ff:ff:ff:ff:ff:ff *
</pre>

So bpq0 maps to eth0, bpq to the wireless interface wlan0 and bpq2..bpq5 map to virtual interfaces and bridges related to hosting KVM machines. Each of these machines can be configured as usual, for example to assign the callsign <tt>ABCDEF-7</tt> and IP address 172.20.4.1 with a /24 prefix equivalent to a 255.255.255.0 netmask:

<pre>
ifconfig bpq0 hw ax25 abcdef-7 172.20.4.1/24
</pre>

By default a BPQ interface will accept traffic from any sender and the destination address is a broadcast address. While this minimizes the configuration required it results in unnecessary load for others than the intended destination system. So it is preferrable to set a specific destination address as long as all outgoing BPQ traffic on this interface is targeted for the same destination system. Similarly it is possible to limit from which Ethernet address a packet is accepted.

== Security ==
The accept from and destination settings are not a suitable security mechanism. They should rather be considered as a mechanism to limited the impact of gross missconfiguration of a network and performance optimization.

== BPQ Multicast address ==
Some systems are using the ethernet address 01:42:50:51:00:00 as the BPQ multicast address. Most Ethernet NICs will accept address that has the lowest bit of its first byte set as a multicast address and accept that as a broadcast packet

== RLI encapsulation ==
also known as BPQENET is a minor but incompatible variant of BPQ encapsulation. Like BPQ encapsulation it's using Ethernet packet type 0x08ff but has an extra 3 byte header following that Ethernet type. Linux does not support this type of encapsulation. RLE originated in Hank W0RLI's SNOS.

== Rewrite of bpqether ==
One of the problems of the bpqether driver is that it creates lots of unnecessary interfaces. This is in particular a problem on big systems with many ethernet interfaces or KVM hosts systems. There is also no guarantee that on each bootup a particular bpq interface will map to the same ethernet interface. And bpq needs to be configured with bpqparms which uses bpqether-specific ioctls, both practices which are frowned upon for many years.

A new mechanism is based on the standard rtnetlink protocol and ip(8) utility and is available in

http://git.linux-ax25.org/cgit/ralf/linux-rose.git/
http://git.linux-ax25.org/cgit/ralf/iproute2.git/

The most significant change is that bpq interfaces are no longer created automatically. Instead a command like
ip link add link eth0 name bpq0 type bpq

is required to configure the interface. Note that this is possible even using an old iproute2 version that doesn't contain support for BPQ. Advanced configuration, that is setting the accepted and destination ethernet addresses currently requires the iproute2 version from above GIT repository. This allows for example to

ip link add link eth0 name bpq0 type bpq accept 24:74:71:15:74:fc destination 00:25:91:ac:91:f0
ip link set dev eth0 accept 24:74:71:15:74:fc destination 00:25:91:ac:91:f0

to be used. You also may leave out the "name bpq0" part in which case the kernel will pick a name starting with "bpq" followed by the first available number. This avoids conflicts but also means you no longer have a predictable name.

The old ioctl configuration mechanism and bpqparms are deprecated but retained for the time being, that is the existing ''bpqparms" program can continue to be used.

Axassociate

2015-07-17T19:29:14Z

DL5RB: Add the obsolete axassociate(8) man page.

This page documents the prehistoric ''axassociate(8)'' command. Its functionality was replaced by <tt>axparms --assoc</tt> in 1995 between ''AX25.028'' and ''ax25-utils 1.3.30''.

== NAME ==
axassociate \- Control the callsign/uid map table

== SYNOPSIS ==
:axassociate <callsign> <username>
:axassociate <callsign> delete
:axassociate policy [default|deny]

== DESCRIPTION ==
:'''Axassociate''' mainpulates the kernel uid/callsign mapping table, allowing callsigns to be associated and dis-associated with a user. The
''policy'' option permits the superuser to have all other uids either default to the actual port name, or to block traffic.

:At power up the table is blank and the policy is 'default', which is thus backward compatible.

== SEE ALSO ==
[[ax25(4)]]

== BUGS ==
If you have a user called 'delete' you have a problem.

Axattach

2015-07-13T22:17:10Z

DL5RB: add man page for the obsolete axattach command.

This page documents the obsolete '''axattach''' command. Axcommand has been renamed to [[kissattach]] already for [[ax25-utils]] 2.0.12c which was released about [[1996]]-12-25.

== NAME ==
: ''axattach - Attach a KISS interface

== SYNOPSIS ==
: axattach [-i inetaddr] [-l] [-m mtu] [-v] tty port

== DESCRIPTION ==
: Attach a SLIP interface in KISS mode to what is normally a tty line connected to a TNC in KISS mode. This program will turn itself into a background process. To down an interface send its axattach process a SIGKILL.

: Axattach takes many of the parameters for the port from the axports(5) file. If the speed parameter in the file is not equal to zero then it is used for the serial port speed, a zero value means that no speed is set. The paclen parameter is used for the device mtu unless overridde by a value on the command line.

:The tty argument will typically be that of a serial port with a KISS TNC attached, although it could be a psuedo tty or a KISS port emulator such as an SCC card. The port arguments is the name of a port as given in the axports(5) file.

== OPTIONS ==
:{|
| -i inetaddr || Set the internet address of the interface. This address may either be a dotted decimal address or a host name.
|-
| -l || Log messages to the system log, the default is not to.
|-
| -m mtu || Sets the mtu of the interface. If this value is not given then the value is taken from the paclen parameter in axports.
|-
| -v || Display the version.
|}

== SEE ALSO ==
: kill(1), stty(1), ax25(4), axparms(4), axports(5), ifconfig(8).

== AUTHOR ==
: Alan Cox GW4PTS <alan@cymru.net>
: Jonathan Naylor G4KLX <jsn@cs.nott.ac.uk>

NET/ROM

2015-07-13T21:58:50Z

DL5RB: axattach has been renamed to kissattach a very, very long time ago.

'''NET/ROM''' was the first layer 3 protocol providing transparent routing to the packet radio user thus enabled less constraint growth of the packet radio network.

The NET/ROM protocol relies on, and uses the AX.25 ports you have created. The NET/ROM protocol rides on top of the AX.25 protocol. To configure NET/ROM on an AX.25 interface you must configure two files. One file describes the NET/ROM interfaces, and the other file describes which of the AX.25 ports will carry NET/ROM. You can configure multiple NET/ROM ports, each with its own callsign and alias, the same procedure applies for each.

== NET/ROM Configuration ==
=== Configuring /etc/ax25/nrports ===

The first is the /etc/ax25/nrports file. This file describes the NET/ROM ports in much the same way as the /etc/ax25/axports file describes the AX.25 ports. Each NET/ROM device you wish to create must have an entry in the /etc/ax25/nrports file. Normally a Linux machine would have only one NET/ROM device configured that would use a number of the AX.25 ports defined. In some situations you might wish a special service such as a BBS to have a separate NET/ROM alias and so you would create more than one.

This file is formatted as follows:

name callsign alias paclen description

Where:

;name
:is the text name that you wish to refer to the port by.
;callsign
:is the callsign that the NET/ROM traffic from this port will use. Note, this is not that address that users should connect to to get access to a node style interface. (The node program is covered later). This callsign/ssid should be unique and should not appear elsewhere in either of the /etc/ax25/axports or the /etc/ax25/nrports files.
;alias
:is the NET/ROM alias this port will have assigned to it.
;paclen
:is the maximum size of NET/ROM frames transmitted by this port.
;description
:is a free text description of the port.

An example would look something like the following:

netrom VK2KTJ-9 LINUX 236 Linux Switch Port

This example creates a NET/ROM port known to the rest of the NET/ROM network as `LINUX:VK2KTJ-9'.

This file is used by programs such as the call program.
=== Configuring /etc/ax25/nrbroadcast ===

The second file is the /etc/ax25/nrbroadcast file. This file may contain a number of entries. There would normally be one entry for each AX.25 port that you wish to allow NET/ROM traffic on.

This file is formatted as follows:

axport min_obs def_qual worst_qual verbose

Where:

;axport
:is the port name obtained from the /etc/ax25/axports file. If you do not have an entry in /etc/ax25/nrbroadcasts for a port then this means that no NET/ROM routing will occur and any received NET/ROM broadcasts will be ignored for that port.
;min_obs
:is the minimum obselesence value for the port.
;def_qual
:is the default quality for the port.
;worst_qual
:is the worst quality value for the port, any routes under this quality will be ignored.
;verbose
:is a flag determining whether full NET/ROM routing broadcasts will occur from this port or only a routing broadcast advertising the node itself.

An example would look something like the following:

radio 1 200 100 1

=== Creating the NET/ROM Network device ===

When you have the two configuration files completed you must create the NET/ROM device in much the same way as you did for the AX.25 devices. This time you use the nrattach command. The nrattach works in just the same way as the [[kissattach]] command except that it creates NET/ROM network devices called `nr[0-9]'. Again, the first time you use the nrattach command it creates the `nr0' device, the second time it creates the `nr1' network devices etc. To create the network device for the NET/ROM port we've defined we would use:

# nrattach netrom

This command would start the NET/ROM device (nr0) named netrom configured with the details specified in the /etc/ax25/nrports file.

=== Starting the NET/ROM daemon ===

The Linux kernel does all of the NET/ROM protocol and switching, but does not manage some functions. The NET/ROM daemon manages the NET/ROM routing tables and generates the NET/ROM routing broadcasts. You start NET/ROM daemon with the command:

# /usr/sbin/netromd -i

You should soon see the /proc/net/nr_neigh file filling up with information about your NET/ROM neighbours.

Remember to put the /usr/sbin/netromd command in your rc files so that it is started automatically each time you reboot.

=== Configuring NET/ROM routing ===

You may wish to configure static NET/ROM routes for specific hosts. The nrparms command enables you to do this. Again, the man page offers a complete description, but a simple example might be:

# /usr/sbin/nrparms -nodes VK2XLZ-10 + #MINTO 120 5 radio VK2SUT-9

This command would set a NET/ROM route to #MINTO:VK2XLZ-10 via a neighbour VK2SUT-9 on my AX.25 port called `radio'.

You can manually create entries for new neighbours using the nrparms command as well. For example:

# /usr/sbin/nrparms -routes radio VK2SUT-9 + 120

This command would create VK2SUT-9 as a NET/ROM neighbour with a quality of 120 and this will be locked and will not be deleted automatically.

== The NET/ROM protocol ==
The original NET/ROM protocol was defined by a company named Software 2000 many years ago for their commercial ROMs for the [[TNC2]]. Later implementations such as by [[The/NET]] were implementing supersets of the protocol.

NET/ROM packets start with a a 5 byte long transport layer folling the [[AX.25]] layer's headers. This header is looking as follows:
<pre>
Offset Use
0 Circuit Index
1 Circuit ID
2 TX Sequence Number
3 RX Sequence Number
4 Opcode and Flags
</pre>
The ''Opcode and Flags'' field is constructed as follows:
<pre>
Bits Use
0 - 3 Opcode
4 Reserviert
5 More Follows Flag
6 NAK Flag
7 Choke
</pre>
NET/ROM implements seven operations for the opcode field. Opcodes 0..6 were already defined in the original Software 2000 NET/ROM specification.
<pre>
0 Protocol Extension
1 Connect Request
2 Connect Acknowledge
3 Disconnect Request
4 Disconnect Acknowledge
5 Information
6 Information Acknowledge
7 Reset
</pre>

=== G8PZT Reset ===
The <tt>Reset</tt> operation was designed by G8PZT. It solves the problem that NET/ROM has nothing equivalent to TCP's RST flag to tell the remote side that a connection does no longer exist on the local side. Strict NET/ROM has no other way of dealing with this case than letting the connection timeout - a <em>very</em> slow recovery method. To avoid reset wars Linux will never reply to a Reset packet with another Reset packet. For paranoia reasons the G8PZT Reset extension is currently disabled by default; it needs to be explcitly enabled by:

<pre>
sysctl -w net.netrom.reset=1
</pre>

The intent is to change the default to enabled after Linux 2.6.17 has been released and no issues have been found.

LinuxAX25

2015-07-09T20:01:00Z

DL5RB: CVS is dead and in general this page was not very wikiish.

This is the one and only official home of the linux AX.25 tools ''libax25'', ''ax25-apps'' and ''ax25-tools''.

Maintainers:
{| {{PrettyTable}}
| Ralf Baechle DL5RB <ralf@linux-mips.org><br>
Thomas Osterried DL9SAU <ax25@x-berg.in-berlin.de>
|}

Please send error-reports or patches to us. Get involved.
You're welcome.

== Reporting bugs ==
Numerous bugs have been found and fixed in the ancient code and numerous more are probably still lurking there. We recommend to test first if the problem still exists in the [[GIT]] version.

On packet radio you can reach the maintainers in realtime on wconvers #275.

We have plans for a public developer mailinglist for this project in order to make strategic discussions or long-term debuging easier. We'll come back to this if the community grows.

If you are a package maintainer of a linux distribution: please contact us.

== See also ==
* [[LinuxAX25_History|Linux/AX.25 History]]

== Links ==
* http://www.linux-ax25.org/wiki/GIT How to download and compile
* http://git.linux-ax25.org/ History and code change documentation

BPQ

2015-07-05T21:38:28Z

DL5RB:

''Bpqether'' is a Linux kernel driver which allows the use of [[AX.25]] over ethernet-like networks such as Ethernet, 802.11 family Wifi networks but also virtual devices such as the Linux software bridge, VLANs and more.

== Unsupported networking technologies ==
Technologies which are similar to Ethernet but not supported are [[FDDI]], [[HIPPI]]. It might be a matter of testing but as long as this has not positively tested the kernel will not allow configuring BPQ over these devices.

== Configuration ==
Up to Linux 4.1 the behaviour is that when the bpqether driver is built into the kernel or loaded as a module a network interface named bpq followed by a small decimal number is created for every ethernet-like device. Details can be seen in /proc/net/bpqether which might look like:

<pre>
dev ether destination accept from
bpq5 vnet1 ff:ff:ff:ff:ff:ff *
bpq3 vbridge ff:ff:ff:ff:ff:ff *
bpq2 virbr0 ff:ff:ff:ff:ff:ff *
bpq1 wlan0 ff:ff:ff:ff:ff:ff *
bpq0 eth0 ff:ff:ff:ff:ff:ff *
</pre>

So bpq0 maps to eth0, bpq to the wireless interface wlan0 and bpq2..bpq5 map to virtual interfaces and bridges related to hosting KVM machines. Each of these machines can be configured as usual, for example to assign the callsign <tt>ABCDEF-7</tt> and IP address 172.20.4.1 with a /24 prefix equivalent to a 255.255.255.0 netmask:

<pre>
ifconfig bpq0 hw ax25 abcdef-7 172.20.4.1/24
</pre>

By default a BPQ interface will accept traffic from any sender and the destination address is a broadcast address. While this minimizes the configuration required it results in unnecessary load for others than the intended destination system. So it is preferrable to set a specific destination address as long as all outgoing BPQ traffic on this interface is targeted for the same destination system. Similarly it is possible to limit from which Ethernet address a packet is accepted.

== Security ==
The accept from and destination settings are not a suitable security mechanism. They should rather be considered as a mechanism to limited the impact of gross missconfiguration of a network and performance optimization.

== Rewrite of bpqether ==
One of the problems of the bpqether driver is that it creates lots of unnecessary interfaces. This is in particular a problem on big systems with many ethernet interfaces or KVM hosts systems. There is also no guarantee that on each bootup a particular bpq interface will map to the same ethernet interface. And bpq needs to be configured with bpqparms which uses bpqether-specific ioctls, both practices which are frowned upon for many years.

A new mechanism is based on the standard rtnetlink protocol and ip(8) utility and is available in

http://git.linux-ax25.org/cgit/ralf/linux-rose.git/
http://git.linux-ax25.org/cgit/ralf/iproute2.git/

The most significant change is that bpq interfaces are no longer created automatically. Instead a command like
ip link add link eth0 name bpq0 type bpq

is required to configure the interface. Note that this is possible even using an old iproute2 version that doesn't contain support for BPQ. Advanced configuration, that is setting the accepted and destination ethernet addresses currently requires the iproute2 version from above GIT repository. This allows for example to

ip link add link eth0 name bpq0 type bpq accept 24:74:71:15:74:fc destination 00:25:91:ac:91:f0
ip link set dev eth0 accept 24:74:71:15:74:fc destination 00:25:91:ac:91:f0

to be used. You also may leave out the "name bpq0" part in which case the kernel will pick a name starting with "bpq" followed by the first available number. This avoids conflicts but also means you no longer have a predictable name.

The old ioctl configuration mechanism and bpqparms are deprecated but retained for the time being, that is the existing ''bpqparms" program can continue to be used.

G8BPQ

2015-07-03T13:30:47Z

DL5RB: Create redirect G8BPQ -> BPQ

#redirect [[BPQ]]

Bpqether

2015-07-03T13:29:57Z

DL5RB: Create redirect bpqether -> BPQ

#redirect [[BPQ]]

BPQ

2015-07-03T13:28:15Z

DL5RB: Document the use and current developments of bpq

''Bpqether'' is a Linux kernel driver which allows the use of [[AX.25]] over ethernet-like networks such as Ethernet, 802.11 family Wifi networks but also virtual devices such as the Linux software bridge, VLANs and more.

== Unsupported networking technologies ==
Technologies which are similar to Ethernet but not supported are [[FDDI]], [[HIPPI]]. It might be a matter of testing but as long as this has not positively tested the kernel will not allow configuring BPQ over these devices.

== Configuration ==
Up to Linux 4.1 the behaviour is that when the bpqether driver is built into the kernel or loaded as a module a network interface named bpq followed by a small decimal number is created for every ethernet-like device. Details can be seen in /proc/net/bpqether which might look like:

<pre>
dev ether destination accept from
bpq5 vnet1 ff:ff:ff:ff:ff:ff *
bpq3 vbridge ff:ff:ff:ff:ff:ff *
bpq2 virbr0 ff:ff:ff:ff:ff:ff *
bpq1 wlan0 ff:ff:ff:ff:ff:ff *
bpq0 eth0 ff:ff:ff:ff:ff:ff *
</pre>

So bpq0 maps to eth0, bpq to the wireless interface wlan0 and bpq2..bpq5 map to virtual interfaces and bridges related to hosting KVM machines. Each of these machines can be configured as usual, for example to assign the callsign <tt>ABCDEF-7</tt> and IP address 172.20.4.1 with a /24 prefix equivalent to a 255.255.255.0 netmask:

<pre>
ifconfig bpq0 hw ax25 abcdef-7 172.20.4.1/24
</pre>

By default a BPQ interface will accept traffic from any sender and the destination address is a broadcast address. While this minimizes the configuration required it results in unnecessary load for others than the intended destination system. So it is preferrable to set a specific destination address as long as all outgoing BPQ traffic on this interface is targeted for the same destination system. Similarly it is possible to limit from which Ethernet address a packet is accepted.

== Security ==
The accept from and destination settings are not a suitable security mechanism. They should rather be considered as a mechanism to limited the impact of gross missconfiguration of a network and performance optimization.

== Rewrite of bpqether ==
One of the problems of the bpqether driver is that it creates lots of unnecessary interfaces. This is in particular a problem on big systems with many ethernet interfaces or KVM hosts systems. There is also no guarantee that on each bootup a particular bpq interface will map to the same ethernet interface. And bpq needs to be configured with bpqparms which uses bpqether-specific ioctls, both practices which are frowned upon for many years.

A new mechanism is based on the standard rtnetlink protocol and ip(8) utility and is available in

http://git.linux-ax25.org/cgit/ralf/linux-rose.git/
http://git.linux-ax25.org/cgit/ralf/iproute2.git/

The most significant change is that bpq interfaces are no longer created automatically. Instead a command like
ip link add link eth0 name bpq0 type bpq

is required to configure the interface. Note that this is possible even using an old iproute2 version that doesn't contain support for BPQ. Advanced configuration, that is setting the accepted and destination ethernet addresses currently requires the iproute2 version from above GIT repository. This allows for example to

ip link add link eth0 name bpq0 type bpq accept 24:74:71:15:74:fc destination 00:25:91:ac:91:f0
ip link set dev eth0 accept 24:74:71:15:74:fc destination 00:25:91:ac:91:f0

to be used. The old ioctl configuration mechanism and bpqparms are deprecated but retained for the time being.

ROSE

2015-06-15T23:20:01Z

DL5RB: /* See also */ Add RFCs about X.25-over-TCP and IP-over-X.25

The '''ROSE''' (RATS Open Systems Environment) protocol was conceived and first implemented by Tom Moulton W2VY and is an implementation of the [[X.25]] [[packet layer protocol]] ([[PLP]]) and is designed to operate with [[AX.25]] as its datalink layer protocol. It too provides a network layer. ROSE addresses take the form of 10 digit numbers. The first four digits are called the [[Data Network Identification Code]] ([[DNIC]]) and are taken from Appendix B of the [[Wikipedia:ITU-T ITU-T]] [[Wikipedia:X.121|X.121]] recommendation. The kernel based ROSE support is a modified version of the [http://rose.fpac.free.fr/rubrique.php3?id_rubrique=1 FPAC] Rose implementation. Installing FPAC as a wrapper around ROSE makes for a much
easier use and operation of the protocol, there is also ongoing work on FPAC under Linux.

These days ROSE is a ''rare'' protocol; islands in Australia, France and the United States (Florida and Michigan) are known to still use the protocol.

The ROSE packet layer protocol protocol relies on, and uses the AX.25 ports you have created. The ROSE protocol rides on top of the AX.25 protocol. To configure ROSE you must create a configuration file that describes the ROSE ports you want. You can create multiple ROSE ports if you wish, the same procedure applies for each.

== Configuring /etc/ax25/rsports ==

The file where you configure your ROSE interfaces is the /etc/ax25/rsports file. This file describes the ROSE port in much the same way as the /etc/ax25/axports file describes the AX.25 ports.

This file is formatted as follows:

name address description

Where:

; name : is the text name that you wish to refer to the port by.
; address : is the 10 digit ROSE address you wish to assign to this port.
; description : is a free text description of the port.

An example would look something like the following:

rose 5050294760 Rose Port

Note that ROSE will use the default callsign/ssid configured on each AX.25 port unless you specify otherwise.

To configure a separate callsign/ssid for ROSE to use on each port you use the rsparms command as follows:

<pre>
# /usr/sbin/rsprams -call VK2KTJ-10
</pre>

This example would make Linux listen for and use the callsign/ssid VK2KTJ-10 on all of the configured AX.25 ports for ROSE calls.

== Creating the ROSE Network device ==

When you have created the /etc/ax25/rsports file you may create the ROSE device in much the same way as you did for the AX.25 devices. This time you use the rsattach command. The rsattach command creates network devices named `rose[0-5]'. The first time you use the rsattach command it create the `rose0' device, the second time it creates the `rose1' device etc. For example:

<pre>
# rsattach rose
</pre>

This command would start the ROSE device (rose0) configured with the details specified in the /etc/ax25/rsports file for the entry named `rose'.

== Configuring ROSE Routing ==

The ROSE protocol currently supports only static routing. The rsparms utility allows you to configure your ROSE routing table under Linux.

For example:

<pre>
# rsparms -nodes add 5050295502 radio vk2xlz
</pre>

would add a route to ROSE node 5050295502 via an AX.25 port named `radio' in your /etc/ax25/axports file to a neighbour with the callsign VK2XLZ.

You may specify a route with a mask to capture a number of ROSE destinations into a single routing entry. The syntax looks like:

<pre>
# rsparms -nodes add 5050295502/4 radio vk2xlz
</pre>

which would be identical to the previous example except that it would match any destination address that matched the first four digits supplied, in this case any address commencing with the digits 5050. An alternate form for this command is:

<pre>
# rsparms -nodes add 5050/4 radio vk2xlz
</pre>

which is probably the less ambiguous form.

== See also ==
* [[Wikipedia:X.25|X.25]] on Wikipedia
* [[Wikipedia:X.121|X.121]] on Wikipedia
* http://www.itu.int/rec/T-REC-X.25-199610-I/E Recommendation ITU-T X.25 (10/96)
* http://www.itu.int/rec/T-REC-X.25-199809-I!Cor1/E Recommendation ITU-T X.25 (10/96) Corrigendum 1
* http://www.itu.int/rec/T-REC-X.121-200010-I/E Recommendation ITU-T X.121 (10/00)
* [http://web.archive.org/web/*/http://www.rats.org/ RATS website] on [http://www.archive.org archive.org]
* [http://www.rfc-editor.org/rfc/rfc1356.txt RFC1356] ''Multiprotocol Interconnect on X.25 and ISDN in the Packet Mode''
* [http://www.rfc-editor.org/rfc/rfc1613.txt RFC1613] ''Cisco Systems X.25 over TCP (XOT)''

ROSE

2015-06-15T22:39:28Z

DL5RB: /* See also */ Remove stray `]' bracket.

Node

2015-06-03T13:38:24Z

DL5RB: A few words about the node program.

The [[node]] package for [[AX.25]], [[NET/ROM]], [[ROSE]] and TCP/IP provides a node shell modelled after hose of the [[TheNet]] or [[G8BPQ]] nodes.
Early versions did ship as part of [[ax25-utils]]. Starting version 0.3.0-ALPHA-1 node published as an independent package after ax25-utils was split in several packages. The latest version is still 0.3.2 which was published in [[1999]].

Ax25-utils

2015-06-03T13:30:29Z

DL5RB: Created page with "The '''ax25-utils''' package was the original AX.25 support for Linux 2.0 and 2.1. The package was split in about 1997 into four separate packages libax25, ax25-too..."

The '''ax25-utils''' package was the original AX.25 support for Linux 2.0 and 2.1. The package was split in about [[1997]] into four separate packages [[libax25]], [[ax25-tools]], [[ax25-apps]] and [[node]]. Today ax25-utils is obsolete.

Starting packet radio on bootup

2015-05-19T13:26:14Z

DL5RB: Explain startup of AX.25 services in particular in the new fangled world of systemd.

All released version of [ax25-tools] and [ax25-apps] do not include the necessary scripts or configuration data to automate startup on bootup.

== System V Init ==
Neither ax25-tools and ax25-tools nor any known distribution is shipping init scripts to start the desired daemons on bootup. Due to this startup at boot time is typically scripted by the system adminstrator in ''rc.local'' which depending on your distribution and its vintage lives somewhere in ''etc''.

== Systemd ==
Systemd is a still relatively new, very powerful and complicated replacement for the venerable System V init. It does not use the traditional init scripts in /etc but relies on configuration files written in a simple syntax to declare in what order to start which services at boot time. As AX.25 requires configuration by default all related services are disabled. This section describes the available unit files.

Please note that everything described in in the systemd section is work in progress and currently unpublished.

=== ax25d.service ===
To enable this service, use ''systemctl enable ax25d.service''. If you also enable ''packet-radio.service'' (see below), [[ax25d]] will be started when the system is booting multiuser. You should review ax25d's configuration before starting this service.

=== mheardd.service ===
To enable this service, use ''systemctl enable mheardd.service''. If you also enable ''packet-radio.service'' (see below), [[mheard]] will be started when the system is booting multiuser.

=== netromd.service ===
To enable this service, use ''systemctl enable netromd.service''. If you also enable ''packet-radio.service'' (see below), [[netromd]] will be started when the system is booting multiuser.

=== packet-radio.target ===
Starting this target with ''systemctl start packet-radio.target'' will start those of ax25d.service, mheardd.service and netromd.service which have been enabled. If enabled with ''systemctl enable packet-radio.target'' this will automatically happen when the system is booting multiuser.

There is no support for daemons other than those listed currently, that is those will still need to be started manually by the sysadmin as explained in the System V Init section above.

== Upstart and others ==
There is no specific support for upstart and other inits. However they do suport some ''rc.local'' script like System V Init so can be treated just like that.

Main Page

2015-05-01T11:44:25Z

DL5RB:

__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]] – [[GIT]]

<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 ==
{| border="0" cellpadding="4" cellspacing="0" valign="top" style="margin: 1em 1em 1em 0; background: #ffe0c0; border-collapse: collapse;"
|-valign="top"
| 2015-04-30
| linux-ax25.org is undergoing massive updates of its slightly dated infrastructure. As the result there will outages of services or the entire system over several days.
|-valign="top"
| 2011-11-04
| All SSL certificates for linux-ax25.org have been refreshed. As a reminder, linux-ax25.org uses [http://www.cacert.org CAcert] certificates and the root certificate for CAcert.org (available [http://www.cacert.org/index.php?id=3 here] is not included with all operating systems and browsers yet so you may have to manually install it if you want to use linux-ax25.org's services encryptedly.
|-valign="top"
| 2011-09-07
| The recent [http://lwn.net/Articles/457142/ compromise] of a kernel.org servers has resulted in some of kernel.org's servers providing DNS service to linux-ax25.org becoming unavailable. A temporary solution is now in place.
|-valign="top"
| 2011-08-18
| A fix for [http://www.cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2011-2910 CVE-2011-2910] ([https://www.redhat.com/security/data/cve/CVE-2011-2910.html Red Hat CVE database], [https://bugzilla.redhat.com/show_bug.cgi?id=730783 Red Hat Bug 730783], [https://bugzilla.redhat.com/show_bug.cgi?id=730784 Red Hat Bug 830784], [http://security-tracker.debian.org/tracker/CVE-2011-2910 Debian security tracker], [http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=638198 Debian Bug 638198]) has been checked into [[CVS]]. The impact of this issue is low as the circumstances that trigger the issue should not normally encountered on a correctly configured system. See also related [http://www.openwall.com/lists/oss-security/2011/08/ discussion] on the oss-security mailing list under the subject "CVE request (and disclosure): ax25d missing setuid return code check".
|-valign="top"
| 2010-06-10
| Linux-ax25.org now is SSL-enabled.
|-valign="top"
| 2010-03-29
| Due to hardware defects the site was running from an outdated copy for a while. The problem has been rectified now. Sorry for the inconvenience.
|-valign="top"
| 2009-12-15
| Since about two weeks linux-ax25.org is suffering from occasional ISP outages. We apologise.
|-valign="top"
| 2009-12-08
| On Friday, 2009-12-11 between 12:00 and 18:00 UTC there is a likely outage for exchange of a broken electricity meter.
|-valign="top"
| 2009-11-20
| linux-ax25.org's software will be upgraded during the next days resulting in downtime of a few hours.
|-valign="top"
| 2009-07-13
| The ISP of linux-ax25.org has announced some scheduled downtime for 2009-08-12. The exact time might change at short notice.
|-valign="top"
| 2009-05-31
| Linux-ax25.org now has an ftp site [ftp://ftp.linux-ax25.org ftp.linux-ax25.org] which hosts historic and current versions of [[ax25-apps]], [[ax25-tools]] and [[libax25]].
|-valign="top"
| 2009-05-29
| The site has moved to a new temporary server system.
|-valign="top"
| 2006-04-19
| Start German version of the site.
|-valign="top"
| 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 ==
[http://www.linux-ax25.org/pub/ax25-apps/ax25-apps-{{Latest-stable-ax25-apps-version}}.tar.gz AX.25 Apps {{Latest-stable-ax25-apps-version}}]<br>
[http://www.linux-ax25.org/pub/ax25-tools/ax25-tools-{{Latest-stable-ax25-tools-version}}.tar.gz AX.25 Tools {{Latest-stable-ax25-tools-version}}]<br>
[http://www.linux-ax25.org/pub/libax25/libax25-{{Latest-stable-libax25-version}}.tar.gz AX.25 Library {{Latest-stable-libax25-version}}]<br>
</div>

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

CVS

2015-05-01T11:36:27Z

DL5RB: Remove mention of git-cvsserver; we never had it officially supported anyway.

LinuxAX25 History

2015-05-01T07:59:46Z

DL5RB: Less talk about CVS, more on GIT.

In Oct 2005 Craig Small passed on maintainership to us, DL9SAU and DL5RB. We immediately updated the contact details on the Sourceforge website.

We started to add the pending software fixes which were discussed at the linux-hams mailinglist. And we revised and added all the patches from the ax25.sf.net bugtracker, which sat there for quite a long time.

Because there were problems with sourceforge.net (a [[CVS]] checkin (In simple words, CVS is a system to maintain the history of all changes to a software project) to a software project]took more than three months until the internal system has shown it up in the public part of the CVS) we decided to give the linux AX.25 collection a new home at linux-ax25.org. Being root, it gives us all the opportunities we may need.

Starting with our Server linux-ax25.org, we first imported the complete CVS tree. Special care was taken that the CVS commit messages (who has when changed what, when and why) of the whole development history were kept: We had to import the whole history by hand/automatic scripts, which was a real pain, because sourceforge provided no simple way to get this data in realtime, and due to their massive technical problems we did not want to wait 3 further months. This traceability is an important thing in Software development, and it was also a major goal at our work.

We also discussed if we should switch over to SVN or GIT instead of CVS, and ended in the opinion that everyone who develops knows how CVS works, and the features the CVS system offers are good enough. This view changed in 2014 by which time CVS was looking even more technically inferior to GIT than it always has been and beginning to fade away into obscurity, so linux-ax25.org migrated over to GIT. The old CVS repositories still exist for the beneift of those who still have active CVS checkouts but there will be no future checkins. The best way to follow Linux/AX2.25 history online is now http://git.linux-ax25.org/cgit/ rsp. https://git.linux-ax25.org/cgit/.

The Wiki documents details on how to download and compile:
URL: http://www.linux-ax25.org/wiki/GIT

We left the download links to the latest relases on the ax25.sourceforge.net site untouched. From todays point of view this may be was a mistake, because people may consider the project being dead. The reasons which lead to this decision were:
* Nobody knew how many linux discributions automatically build packages from this download link and what damage the removal could cause
* We needed time for development. If i.E. people have problems (bug, compatibility, etc..) with software at an arbitrary point during this phase, or if there's a security problem, it's not easy to track the error.
* Users mostly do not compile their own software. They just use the "know how" of their favourite linux distribution.
* Developers knew about the new home, or just sent us an E-Mail or chated with us on our wconvers channel.

Time went on, the software became more and more stable, but we needed some more steps for a "release". Some times, GNU automake changed, sometimes the new gcc compiler began to complain things (where their ancestors just did their work) and sometimes we had an issue with new include files or the behaviour of a new glibc.

On the other hand longer the time took, the more the truth for all software became perceptible: there never will be an end. It's an ongoing process. This is the main reason why there (still) is no new version numbered release like ax25-apps-0.0.6, ax25-tools-0.0.8 or libax25-0.0.11 which are the latest official released tar balls and stem from the sourceforge era.

Since we always tested our code before checkin to the CVS there was nothing to worry about at when point of time someone checked out the sources. Most people had the CVS extracted at home and from time to time did an CVS update.

Keeping this in mind, we encouraged maintainers of linux distributions (who contacted us) to periodicaly check the changes on the cvs. This is apparently not a new idea. You may look at your favourite linux distribution and their experiences over the years:
Either they said "we need to get solid as a rock". They froze their applications, needed 2 to 3 years for their release, and when it came out it was so antiquated that no one liked to use it (either because it did not had all the whistles one expects from modern systems, or because it's so old that important features were not available); never mind, the freaks always used the development system, and thus the old release was not a problem for them.<br />
Other distributions went another way round: they have release cycles of half a year and an easy upgrade mechanism. With this kind evolutionary process nobody cares of libax25-version-f00-bar.

Link to the archived ax25.sourceforge.net Homepage:
[[LinuxAX25_Historic_Homepage]]

== Famous last words ==
We always encouraged to submit error reports and patches or help us for the goal of a release. There was feedback, but not enough.

As of Jan 2009 there was a strange discussion going on the linux-hams mailinglist. We've to point out that
* The project is not dead.
* DL5RB and DL9SAU are the maintainers. They usually answer in less than 24 hours.
* Patches and fixes have to be sent to us. We could only incorporate things we have cognition about.
* Nobody could clame the stability of the software, nor the modernity, nor the good quality of the code.
* Nobody who ever asked has gone without a satisfactory answer for his request or problem.
* It's in fact not possible to read the list the whole time. Posting something to a list is like pinning a bugfix on a beer mat in a disco in Timbuktu.
* Discussion is important. But the claim that "the community is on the mailinglist" (where tons of other problems were discussed) has to be declined. That's the way open software goes? - Indeed, it's one way, unfortunately, and often enough. But it's not the correct way. If you have a problem, go to the maintainer. If you want to play with, ask to join. Want to help (package building, website, bringing the software to the next millenium): talk with us and not beyond us.<p>We really wonder why over the years nobody came to the idea to say "Hey dear maintainers, i'm in an important discussion on the mailinglist xyz, you're requested to join in". This is not really that kind of "community" and "the way software development on linux goes", as someone pointed out.
* Software development needs continuity, project leaders, volunteers, fans. Not just a collection of pinboards.

Collaboration work means working together, not against each other.

CVS

2015-05-01T07:34:05Z

DL5RB: /* Browse the changes */ Move cvsweb to http[s]://cvs.linux-ax25.org/cvsweb which is a more logic place for it to be.

Morse Code

2015-04-30T07:59:45Z

DL5RB: /* Other */ CWirc has moved. Update home page URL.

== Morse Software ==
* [http://www.w1hkj.com/Fldigi.html Fldigi] Digital Modem

== Training ==
* [http://aldo.nongnu.org/ Aldo]
* [[GW4PTS Morse Trainer]]
* [[morse]] aka superiormorse
* [[SoundCard CW]]

== Other ==
* [http://myspace.voo.be/pcoupard/cwirc/ CWirc] is a plugin for the [http://www.xchat.org X-Chat] IRC client to transmit raw morse code over the internet using IRC servers as reflectors.

CVS

2015-04-26T18:44:46Z

DL5RB: Cleanup. CVS no longer tracks the bleedings edge. The trailing edge. At best.

Compilation

2015-04-26T18:26:28Z

DL5RB: Remove mention of CVS. CVS is not only dead but also this page is SCM tool agnostic.

This is how to build [[libax25]], [[ax25-tools]] or [[ax25-apps]] from source. See also below for the special steps required to build from a fresh [[GIT]] checkout.

=== Build dependencies ===
Install autoconf automake1.9 libtool libncurses-dev. Parts of the ax25-tools package will also fltk and fltk development packages.

Automake1.4 on debian sarge and etch is known to be incompatible in preconfigureing the hdlcutil FL-Widgets tree.

=== Bootstrap (autoreconf, make) ===

<pre>
for dir in libax25 ax25-apps ax25-tools; do
cd $dir && autoreconf --install --force && \
./configure --prefix=/usr --sysconfdir=/etc --localstatedir=/var --mandir=/usr/share/man && \
make && make install && cd ..
done
</pre>

On a new fresh installation, you should do "make installconf" in the libax25 ax25-apps ax25-tools directories, too.
But be aware, that make installconf overwrites existing configuration files in /etc/ax25/.

Note: earlier versions had a bootstrap script (with aclocal, autoconf and an appropriate ./configure line) but these days <em>autoreconf</em> should be used.

=== Ax25-apps naming conflicts ===
<tt>ax25-apps</tt> installs two program named <tt>call</tt> and <tt>listen</tt>. Despite <tt>ax25-apps</tt> using these names for longer than other packages various Linux distributions including [http://www.debian.org/ Debian] and [http://www.fedoraproject.org Fedora] have elected to rename these binaries. When building <tt>ax25-apps</tt> you want to make sure there are no such conflicts. Standard GNU autoconf which is being used by <tt>ax25-apps</tt> for configuration supports such renaming through the powerful but obscure <tt>--program-transform-name</tt> option like this:

<pre>
./configure --program-transform-name='s@^call@axcall@;s@^listen@axlisten@' --prefix=/usr --sysconfdir=/etc --localstatedir=/var --mandir=/usr/share/man
</pre>

This will install the <tt>call</tt> program and its man page as <tt>axcall</tt> and <tt>listen</tt> as <tt>axlisten</tt>. The argument of --program-transform-name is a <tt>sed(1)</tt> program; adjust as need for your installation. Because this is a standard feature of <tt>GNU autoconf</tt>, all versions of <tt>ax25-apps</tt> and also <tt>ax25-tools</tt> support this.

Versions of ax25-apps from 2011-12-11 or newer also honour the <tt>--program-transform-name</tt>, <tt>--program-prefix</tt> and <tt>--program-suffix</tt> options for the content and cross references of the man pages.

Git

2015-04-26T18:22:40Z

DL5RB: Redirect so GIT and Git capitalizations will both work.

#redirect [[GIT]]

GIT

2015-04-26T18:19:09Z

DL5RB: /* Status of CVS to GIT conversion */

<h4 style="background-color:#efefff;border-bottom: 0px;border: 1px solid #1e90ff;text-align:left;padding-top:4px;margin-top:5px; ">
::We will hereby start scouring the net for people who say git is hard to
::understand and use, and just kill them. They clearly are just polluting
::the gene pool.
:
::::Linus
</h4>
<div style="padding-left:2em;padding-right:2em;">

All right, we're not quite that bad. Yet. These days the Linux world has largely switched to '''GIT''' as its SCM. Git is a fairly low-level thing, more the backing store of an SCM - or ''plumbing'' in Linus's words - than a full-blown SCM but it's growing up very quickly. Linux-ax25.org has used [[CVS]] since [[2001]] and so naturally is a little more conservative in switching to a new tools as we don't want to drop all the history that's hidden in these trees.

== Accessing GIT repositories ==
The GIT repositories can be accessed by <tt>git://git.linux-ax25.org/pub/scm</tt>. The http and rsync protocols are also supported but not recommended. Here are two example commands using the <tt>libax25.git</tt> repository; you can substitute the name of another repository (see further below) for <tt>libax25.git</tt> in the examples.

=== Cloning a repository ===

git clone git://git.linux-ax25.org/pub/scm/libax25

This will create a new directory under the current working directory called linux.
To use a different name specify it on the command line as an additional argument and it will become the target.
Here is an alternate form of the command which creates a local directory called libax25.git instead of libax25.

git clone git://git.linux-ax25.org/pub/scm/libax25 linux.git

=== Updating a repository ===
When the repository was cloned the upstream URL was saved into the file <tt>.git/remotes/origin</tt>.
This is the default location for git to pull updates.
If you wish to modify the default URL you may edit that file directly.

From the top directory of your local repository (that is, the directory which contains the <tt>.git</tt> subdirectory) run the following command:

git pull

This will pull updates from the repository and merge them into your local repository.

It is also possible to specify an alternate URL by specifying it on the command line.

git pull git://git.linux-ax25.org/pub/scm/libax25

Typing in URLs can be tedious. You may create shortcuts to repeatedly used URLs by saving them in a remotes file.
Alternate URLs may be saved in the <tt>.git/remotes/REMOTENAME</tt> file where the <tt>REMOTENAME</tt> string is the name that you wish to call that source location. Let's say that that you wanted to clone this long URL
<tt>git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git</tt> but find that a lot to type repeatedly.
If that is specified in a remotes file <tt>linus</tt> then the following command would pull from it. <tt>git pull linus</tt>

=== Which git protocol to use ===
Generally these days the git protocol (the <tt>git://</tt>) URLs) is the prefered protocol.
* git Git's own protocol which tries to heavily optimize the amount of bandwidth used and thus is generally very efficient for updates. An issue with the git protocol is its use of TCP port 9418 which [[Wikipedia:Paranoia|paranoid]] firewall admins may have blocked.
* http Rather inefficient usage of bandwith and CPU but since http is generally enabled in firewalls it exists for those poor souls suffering from [[Wikipedia:Fascist|fascist]] firewall admins.
* https More secure than http but otherwise pretty much the same thing. linux-ax25.org uses SSL certificates from cacert.org and CACERT's root certificate is not included with most operating systems. A notable exception is Debian however. So if attempts to access a linux-ax25.org repository via https fail with an error message about an invalid SSL certificate, you can:
** use one of the other protocols listed in this section
** disable the verification of the SSL certificate. On a UNIX or Linux type of system you do this by setting the GIT_SSL_NO_VERIFY variable, for example: <code>GIT_SSL_NO_VERIFY=yes git clone https://git.linux-ax25.org/pub/scm/libax25.git</code>. Note that this disables the verification of the certificate thus leaving you vulnerable to the same attacks as plain http.
** manually import the root certificate. The preferable but also most complicated approach.
* rsync The oldest git protocol, deprecated and supposed to eventually go away. Suffers from a low probability race condition. Its advantage is the lowest CPU usage on the server side. Also some firewalls that don't allow git git protocol will allow rsync. Not recommended for pulling or fetching. Heck, it really should be considered the last alternative. Rsync is not what in git parlance is called an intelligent transport which means that all new pack files on the server side will be transfered to the client even if only a single object from the pack would need to be transfered.

== Status of CVS to GIT conversion ==

All development has been moved to git. For the time being the CVS Server is still running to maintain the history and help users with existing CVS checkouts however there will be ''no'' more CVS checkins.

It has been attempted to convert the entire history of CVS with some of the details that CVS doesn't record manually restructed and the tarball history which predates the CVS history. Various generated files, even some binaries were checked into the CVS history and often these files were deleted or regenerated for the distributed archives, so there is no 100% equivalence between the tagged versions and corresponding tarballs.

== Checking out a tagged release with git ==
This is how to list the available tags:

<pre>
[ralf@dea linux-git]$ git tag -l
$ git tag -l
libax25-0.0.10
libax25-0.0.11
libax25-0.0.12-rc1
libax25-0.0.12-rc2
libax25-0.0.12-rc3
...
</pre>

The actual list of tags is longer. Okay, so let's assume we want to checkout the <tt>libax25-0.0.11</tt> release:

<pre>
[ralf@dea linux-git]$ git checkout -b my-0.0.11 libax25-0.0.11
</pre>

What this exactly does is creating a ''new'' branch named <tt>my-0.0.11</tt> at <tt>linux-0.0.11</tt> and checking out it's HEAD.

== Gitweb ==
Gitweb allows simple browsing of git repositories in a web browser. Git web is available at http://git.linux-ax25.org.

== See also ==
* [[Compilation]] How to build <tt>libax25</tt>, <tt>ax25-tools</tt> or <tt>ax25-apps</tt> from source.
* [http://kernel.org/pub/software/scm/git/docs/tutorial.html A short git tutorial] at [http://www.kernel.org kernel.org]
* [http://git.or.cz The GIT homepage]
* http://www-128.ibm.com/developerworks/linux/library/l-vercon/index.html A nice article by IBM giving an overview what SCM is and several popular SCM systems.

[[Category:git]]

AX.25

2015-04-26T18:15:08Z

DL5RB: Kill another reference to CVS. Though this link should probably have a differnt destination ...

* [[The Packet Radio Protocols and Linux]]
* [[GIT|Linux AX25-APPS/-TOOLS]]
* [[The AX.25/NET/ROM/ROSE software components]]
* [[Installing the AX.25/NET/ROM/ROSE software]]
* [[A note on callsigns, addresses and things before we start]]
** [[What are all those T1, T2, N2 and things ?]]
** [[Run time configurable parameters]]
* [[Configuring an AX.25 port]]
** [[Configuring_an_AX.25_port#Creating_the_AX.25_network_device|Creating the AX.25 network device]]
** [[Configuring_an_AX.25_port#Creating_the_.2Fetc.2Fax25.2Faxports_file|Creating the /etc/ax25/axports file]]
** [[Configuring_an_AX.25_port#Configuring_AX.25_routing|Configuring AX.25 routing]]
* [[Configuring an AX.25 interface for TCP/IP]]
* [[NET/ROM]] The NET/ROM protocol and it's configuration.
* [[Configuring a NET/ROM interface for TCP/IP]]
* [[ROSE]] More about ROSE and it's configuration.
* [[Making AX.25/NET/ROM/ROSE calls]]
* [[Configuring Linux to accept Packet connections]]
** [[Configuring_Linux_to_accept_Packet_connections#Creating_the_.2Fetc.2Fax25.2Fax25d.conf_file|Creating the /etc/ax25/ax25d.conf file]]
** [[Configuring_Linux_to_accept_Packet_connections#A_simple_example_ax25d.conf_file|A simple example ax25d.conf file]]
** [[Configuring_Linux_to_accept_Packet_connections#Starting_ax25d|Starting ax25d]]
* [[Configuring the node software]]
** [[Configuring_the_node_software#Creating_the_.2Fetc.2Fax25.2Fnode.conf_file|Creating the /etc/ax25/node.conf file]]
** [[Configuring_the_node_software#Creating_the_.2Fetc.2Fax25.2Fnode.perms_file|Creating the /etc/ax25/node.perms file]]
** [[Configuring_the_node_software#Configuring_node_to_run_from_ax25d|Configuring node to run from ax25d]]
** [[Configuring_the_node_software#Configuring_node_to_run_from_inetd|Configuring node to run from inetd]]
* [[Configuring axspawn]]
** [[Configuring axspawn# Creating the /etc/ax25/axspawn.conf file|Creating the /etc/ax25/axspawn.conf file]]
* [[Configuring the pms]]
* [[Configuring the user_call programs]]
* [[Configuring the ROSE Uplink and Downlink commands]]
* [[Associating AX.25 callsigns with Linux users]]
* [[Configuring APRS]]
* [[The /proc/ file system entries]]
* [[AX.25, NET/ROM, ROSE network programming]]
** [[AX.25%2C_NET/ROM%2C_ROSE_network_programming#The_address_families|The address families]]
** [[AX.25%2C_NET/ROM%2C_ROSE_network_programming#The_header_files|The header files]]
** [[AX.25%2C_NET/ROM%2C_ROSE_network_programming#Callsign_mangling_and_examples|Callsign mangling and examples]]
* [[Some sample configurations]]
** [[Some_sample_configurations#Small_Ethernet_LAN_with_Linux_as_a_router_to_Radio_LAN|Small Ethernet LAN with Linux as a router to Radio LAN]]
** [[Some_sample_configurations#IPIP_encapsulated_gateway_configuration|IPIP encapsulated gateway configuration]]
** [[Some_sample_configurations#AXIP_encapsulated_gateway_configuration|AXIP encapsulated gateway configuration]]
** [[Some_sample_configurations#Linking_NOS_and_Linux_using_a_pipe_device|Linking NOS and Linux using a pipe device]]
* [[Summary of AX.25-related Linux commands]]
* [[Where do I find more information about .... ?]]
** [[Other related documentation]]
** [[Where_do_I_find_more_information_about_...._%3F#Packet_Radio|Packet Radio]]
** [[Where_do_I_find_more_information_about_...._%3F#Protocol_Documentation|Protocol Documentation]]
** [[Where_do_I_find_more_information_about_...._%3F#Hardware_Documentation|Hardware Documentation]]
** [[Where_do_I_find_more_information_about_...._%3F#Linux_Ham_Radio_Software|Linux Ham Radio Software]]
* [[Discussion relating to Amateur Radio and Linux]]

== See also ==
* http://www.ax25.net/ The AX.25 Layer 2 SIG

CVS

2015-04-26T18:02:09Z

DL5RB: Capitalize Link name properly so it will actually work.

Template:Latest-stable-ax25-apps-version

2013-06-17T13:32:36Z

DL5RB: ax25-apps 0.0.8-rc4

0.0.8-rc4

Template:Latest-stable-ax25-tools-version

2013-06-17T13:32:16Z

DL5RB: ax25-tools 0.0.10-rc4

0.0.10-rc4

Template:Latest-stable-libax25-version

2013-06-17T13:31:57Z

DL5RB: libax25 0.0.12-rc4

0.0.12-rc4

GIT

2013-06-04T14:50:30Z

DL5RB: Link to compilation notes page.

<h4 style="background-color:#efefff;border-bottom: 0px;border: 1px solid #1e90ff;text-align:left;padding-top:4px;margin-top:5px; ">
::We will hereby start scouring the net for people who say git is hard to
::understand and use, and just kill them. They clearly are just polluting
::the gene pool.
:
::::Linus
</h4>
<div style="padding-left:2em;padding-right:2em;">

All right, we're not quite that bad. Yet. These days the Linux world has largely switched to '''GIT''' as its SCM. Git is a fairly low-level thing, more the backing store of an SCM - or ''plumbing'' in Linus's words - than a full-blown SCM but it's growing up very quickly. Linux-ax25.org has used [[CVS]] since [[2001]] and so naturally is a little more conservative in switching to a new tools as we don't want to drop all the history that's hidden in these trees.

== Accessing GIT repositories ==
The GIT repositories can be accessed by <tt>git://git.linux-ax25.org/pub/scm</tt>. The http and rsync protocols are also supported but not recommended. Here are two example commands using the <tt>libax25.git</tt> repository; you can substitute the name of another repository (see further below) for <tt>libax25.git</tt> in the examples.

=== Cloning a repository ===

git clone git://git.linux-ax25.org/pub/scm/libax25

This will create a new directory under the current working directory called linux.
To use a different name specify it on the command line as an additional argument and it will become the target.
Here is an alternate form of the command which creates a local directory called libax25.git instead of libax25.

git clone git://git.linux-ax25.org/pub/scm/libax25 linux.git

=== Updating a repository ===
When the repository was cloned the upstream URL was saved into the file <tt>.git/remotes/origin</tt>.
This is the default location for git to pull updates.
If you wish to modify the default URL you may edit that file directly.

From the top directory of your local repository (that is, the directory which contains the <tt>.git</tt> subdirectory) run the following command:

git pull

This will pull updates from the repository and merge them into your local repository.

It is also possible to specify an alternate URL by specifying it on the command line.

git pull git://git.linux-ax25.org/pub/scm/libax25

Typing in URLs can be tedious. You may create shortcuts to repeatedly used URLs by saving them in a remotes file.
Alternate URLs may be saved in the <tt>.git/remotes/REMOTENAME</tt> file where the <tt>REMOTENAME</tt> string is the name that you wish to call that source location. Let's say that that you wanted to clone this long URL
<tt>git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git</tt> but find that a lot to type repeatedly.
If that is specified in a remotes file <tt>linus</tt> then the following command would pull from it. <tt>git pull linus</tt>

=== Which git protocol to use ===
Generally these days the git protocol (the <tt>git://</tt>) URLs) is the prefered protocol.
* git Git's own protocol which tries to heavily optimize the amount of bandwidth used and thus is generally very efficient for updates. An issue with the git protocol is its use of TCP port 9418 which [[Wikipedia:Paranoia|paranoid]] firewall admins may have blocked.
* http Rather inefficient usage of bandwith and CPU but since http is generally enabled in firewalls it exists for those poor souls suffering from [[Wikipedia:Fascist|fascist]] firewall admins.
* https More secure than http but otherwise pretty much the same thing. linux-ax25.org uses SSL certificates from cacert.org and CACERT's root certificate is not included with most operating systems. A notable exception is Debian however. So if attempts to access a linux-ax25.org repository via https fail with an error message about an invalid SSL certificate, you can:
** use one of the other protocols listed in this section
** disable the verification of the SSL certificate. On a UNIX or Linux type of system you do this by setting the GIT_SSL_NO_VERIFY variable, for example: <code>GIT_SSL_NO_VERIFY=yes git clone https://git.linux-ax25.org/pub/scm/libax25.git</code>. Note that this disables the verification of the certificate thus leaving you vulnerable to the same attacks as plain http.
** manually import the root certificate. The preferable but also most complicated approach.
* rsync The oldest git protocol, deprecated and supposed to eventually go away. Suffers from a low probability race condition. Its advantage is the lowest CPU usage on the server side. Also some firewalls that don't allow git git protocol will allow rsync. Not recommended for pulling or fetching. Heck, it really should be considered the last alternative. Rsync is not what in git parlance is called an intelligent transport which means that all new pack files on the server side will be transfered to the client even if only a single object from the pack would need to be transfered.

== Status of CVS to GIT conversion ==

All development has been moved to git. It has been attempted to convert the entire history of CVS with some of the details that CVS doesn't record manually restructed and the tarball history which predates the CVS history. Various generated files, even some binaries were checked into the CVS history and often these files were deleted or regenerated for the distributed archives, so there is no 100% equivalence between the tagged versions and corresponding tarballs.

== Checking out a tagged release with git ==
This is how to list the available tags:

<pre>
[ralf@dea linux-git]$ git tag -l
$ git tag -l
libax25-0.0.10
libax25-0.0.11
libax25-0.0.12-rc1
libax25-0.0.12-rc2
libax25-0.0.12-rc3
...
</pre>

The actual list of tags is longer. Okay, so let's assume we want to checkout the <tt>libax25-0.0.11</tt> release:

<pre>
[ralf@dea linux-git]$ git checkout -b my-0.0.11 libax25-0.0.11
</pre>

What this exactly does is creating a ''new'' branch named <tt>my-0.0.11</tt> at <tt>linux-0.0.11</tt> and checking out it's HEAD.

== Gitweb ==
Gitweb allows simple browsing of git repositories in a web browser. Git web is available at http://git.linux-ax25.org.

== See also ==
* [[Compilation]] How to build <tt>libax25</tt>, <tt>ax25-tools</tt> or <tt>ax25-apps</tt> from source.
* [http://kernel.org/pub/software/scm/git/docs/tutorial.html A short git tutorial] at [http://www.kernel.org kernel.org]
* [http://git.or.cz The GIT homepage]
* http://www-128.ibm.com/developerworks/linux/library/l-vercon/index.html A nice article by IBM giving an overview what SCM is and several popular SCM systems.

[[Category:git]]

Compilation

2013-06-04T14:50:16Z

DL5RB: ... to here.

This is how to build [[libax25]], [[ax25-tools]] or [[ax25-apps]] from source. See also below for the special steps required to build from a fresh [[GIT]] or beware, [[CVS]] checkout.

=== Build dependencies ===
Install autoconf automake1.9 libtool libncurses-dev. Parts of the ax25-tools package will also fltk and fltk development packages.

Automake1.4 on debian sarge and etch is known to be incompatible in preconfigureing the hdlcutil FL-Widgets tree.

=== Bootstrap (autoreconf, make) ===

<pre>
for dir in libax25 ax25-apps ax25-tools; do
cd $dir && autoreconf --install --force && \
./configure --prefix=/usr --sysconfdir=/etc --localstatedir=/var --mandir=/usr/share/man && \
make && make install && cd ..
done
</pre>

On a new fresh installation, you should do "make installconf" in the libax25 ax25-apps ax25-tools directories, too.
But be aware, that make installconf overwrites existing configuration files in /etc/ax25/.

Note: earlier versions had a bootstrap script (with aclocal, autoconf and an appropriate ./configure line) but these days <em>autoreconf</em> should be used.

=== Ax25-apps naming conflicts ===
<tt>ax25-apps</tt> installs two program named <tt>call</tt> and <tt>listen</tt>. Despite <tt>ax25-apps</tt> using these names for longer than other packages various Linux distributions including [http://www.debian.org/ Debian] and [http://www.fedoraproject.org Fedora] have elected to rename these binaries. When building <tt>ax25-apps</tt> you want to make sure there are no such conflicts. Standard GNU autoconf which is being used by <tt>ax25-apps</tt> for configuration supports such renaming through the powerful but obscure <tt>--program-transform-name</tt> option like this:

<pre>
./configure --program-transform-name='s@^call@axcall@;s@^listen@axlisten@' --prefix=/usr --sysconfdir=/etc --localstatedir=/var --mandir=/usr/share/man
</pre>

This will install the <tt>call</tt> program and its man page as <tt>axcall</tt> and <tt>listen</tt> as <tt>axlisten</tt>. The argument of --program-transform-name is a <tt>sed(1)</tt> program; adjust as need for your installation. Because this is a standard feature of <tt>GNU autoconf</tt>, all versions of <tt>ax25-apps</tt> and also <tt>ax25-tools</tt> support this.

Versions of ax25-apps from 2011-12-11 or newer also honour the <tt>--program-transform-name</tt>, <tt>--program-prefix</tt> and <tt>--program-suffix</tt> options for the content and cross references of the man pages.

CVS

2013-06-04T14:49:17Z

DL5RB: Move compilation notes from here ...

GIT

2013-06-04T14:38:54Z

DL5RB: A git primer for linux-ax25.org users.

<h4 style="background-color:#efefff;border-bottom: 0px;border: 1px solid #1e90ff;text-align:left;padding-top:4px;margin-top:5px; ">
::We will hereby start scouring the net for people who say git is hard to
::understand and use, and just kill them. They clearly are just polluting
::the gene pool.
:
::::Linus
</h4>
<div style="padding-left:2em;padding-right:2em;">

All right, we're not quite that bad. Yet. These days the Linux world has largely switched to '''GIT''' as its SCM. Git is a fairly low-level thing, more the backing store of an SCM - or ''plumbing'' in Linus's words - than a full-blown SCM but it's growing up very quickly. Linux-ax25.org has used [[CVS]] since [[2001]] and so naturally is a little more conservative in switching to a new tools as we don't want to drop all the history that's hidden in these trees.

== Accessing GIT repositories ==
The GIT repositories can be accessed by <tt>git://git.linux-ax25.org/pub/scm</tt>. The http and rsync protocols are also supported but not recommended. Here are two example commands using the <tt>libax25.git</tt> repository; you can substitute the name of another repository (see further below) for <tt>libax25.git</tt> in the examples.

=== Cloning a repository ===

git clone git://git.linux-ax25.org/pub/scm/libax25

This will create a new directory under the current working directory called linux.
To use a different name specify it on the command line as an additional argument and it will become the target.
Here is an alternate form of the command which creates a local directory called libax25.git instead of libax25.

git clone git://git.linux-ax25.org/pub/scm/libax25 linux.git

=== Updating a repository ===
When the repository was cloned the upstream URL was saved into the file <tt>.git/remotes/origin</tt>.
This is the default location for git to pull updates.
If you wish to modify the default URL you may edit that file directly.

From the top directory of your local repository (that is, the directory which contains the <tt>.git</tt> subdirectory) run the following command:

git pull

This will pull updates from the repository and merge them into your local repository.

It is also possible to specify an alternate URL by specifying it on the command line.

git pull git://git.linux-ax25.org/pub/scm/libax25

Typing in URLs can be tedious. You may create shortcuts to repeatedly used URLs by saving them in a remotes file.
Alternate URLs may be saved in the <tt>.git/remotes/REMOTENAME</tt> file where the <tt>REMOTENAME</tt> string is the name that you wish to call that source location. Let's say that that you wanted to clone this long URL
<tt>git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git</tt> but find that a lot to type repeatedly.
If that is specified in a remotes file <tt>linus</tt> then the following command would pull from it. <tt>git pull linus</tt>

=== Which git protocol to use ===
Generally these days the git protocol (the <tt>git://</tt>) URLs) is the prefered protocol.
* git Git's own protocol which tries to heavily optimize the amount of bandwidth used and thus is generally very efficient for updates. An issue with the git protocol is its use of TCP port 9418 which [[Wikipedia:Paranoia|paranoid]] firewall admins may have blocked.
* http Rather inefficient usage of bandwith and CPU but since http is generally enabled in firewalls it exists for those poor souls suffering from [[Wikipedia:Fascist|fascist]] firewall admins.
* https More secure than http but otherwise pretty much the same thing. linux-ax25.org uses SSL certificates from cacert.org and CACERT's root certificate is not included with most operating systems. A notable exception is Debian however. So if attempts to access a linux-ax25.org repository via https fail with an error message about an invalid SSL certificate, you can:
** use one of the other protocols listed in this section
** disable the verification of the SSL certificate. On a UNIX or Linux type of system you do this by setting the GIT_SSL_NO_VERIFY variable, for example: <code>GIT_SSL_NO_VERIFY=yes git clone https://git.linux-ax25.org/pub/scm/libax25.git</code>. Note that this disables the verification of the certificate thus leaving you vulnerable to the same attacks as plain http.
** manually import the root certificate. The preferable but also most complicated approach.
* rsync The oldest git protocol, deprecated and supposed to eventually go away. Suffers from a low probability race condition. Its advantage is the lowest CPU usage on the server side. Also some firewalls that don't allow git git protocol will allow rsync. Not recommended for pulling or fetching. Heck, it really should be considered the last alternative. Rsync is not what in git parlance is called an intelligent transport which means that all new pack files on the server side will be transfered to the client even if only a single object from the pack would need to be transfered.

== Status of CVS to GIT conversion ==

All development has been moved to git. It has been attempted to convert the entire history of CVS with some of the details that CVS doesn't record manually restructed and the tarball history which predates the CVS history. Various generated files, even some binaries were checked into the CVS history and often these files were deleted or regenerated for the distributed archives, so there is no 100% equivalence between the tagged versions and corresponding tarballs.

== Checking out a tagged release with git ==
This is how to list the available tags:

<pre>
[ralf@dea linux-git]$ git tag -l
$ git tag -l
libax25-0.0.10
libax25-0.0.11
libax25-0.0.12-rc1
libax25-0.0.12-rc2
libax25-0.0.12-rc3
...
</pre>

The actual list of tags is longer. Okay, so let's assume we want to checkout the <tt>libax25-0.0.11</tt> release:

<pre>
[ralf@dea linux-git]$ git checkout -b my-0.0.11 libax25-0.0.11
</pre>

What this exactly does is creating a ''new'' branch named <tt>my-0.0.11</tt> at <tt>linux-0.0.11</tt> and checking out it's HEAD.

== Gitweb ==
Gitweb allows simple browsing of git repositories in a web browser. Git web is available at http://git.linux-ax25.org.

== See also ==
* [http://kernel.org/pub/software/scm/git/docs/tutorial.html A short git tutorial] at [http://www.kernel.org kernel.org]
* [http://git.or.cz The GIT homepage]
* http://www-128.ibm.com/developerworks/linux/library/l-vercon/index.html A nice article by IBM giving an overview what SCM is and several popular SCM systems.

[[Category:git]]

Main Page

2013-06-04T14:13:20Z

DL5RB: Change CVS link to git.

__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]] – [[GIT]]

<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 ==
{| border="0" cellpadding="4" cellspacing="0" valign="top" style="margin: 1em 1em 1em 0; background: #ffe0c0; border-collapse: collapse;"
|-valign="top"
| 2011-11-04
| All SSL certificates for linux-ax25.org have been refreshed. As a reminder, linux-ax25.org uses [http://www.cacert.org CAcert] certificates and the root certificate for CAcert.org (available [http://www.cacert.org/index.php?id=3 here] is not included with all operating systems and browsers yet so you may have to manually install it if you want to use linux-ax25.org's services encryptedly.
|-valign="top"
| 2011-09-07
| The recent [http://lwn.net/Articles/457142/ compromise] of a kernel.org servers has resulted in some of kernel.org's servers providing DNS service to linux-ax25.org becoming unavailable. A temporary solution is now in place.
|-valign="top"
| 2011-08-18
| A fix for [http://www.cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2011-2910 CVE-2011-2910] ([https://www.redhat.com/security/data/cve/CVE-2011-2910.html Red Hat CVE database], [https://bugzilla.redhat.com/show_bug.cgi?id=730783 Red Hat Bug 730783], [https://bugzilla.redhat.com/show_bug.cgi?id=730784 Red Hat Bug 830784], [http://security-tracker.debian.org/tracker/CVE-2011-2910 Debian security tracker], [http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=638198 Debian Bug 638198]) has been checked into [[CVS]]. The impact of this issue is low as the circumstances that trigger the issue should not normally encountered on a correctly configured system. See also related [http://www.openwall.com/lists/oss-security/2011/08/ discussion] on the oss-security mailing list under the subject "CVE request (and disclosure): ax25d missing setuid return code check".
|-valign="top"
| 2010-06-10
| Linux-ax25.org now is SSL-enabled.
|-valign="top"
| 2010-03-29
| Due to hardware defects the site was running from an outdated copy for a while. The problem has been rectified now. Sorry for the inconvenience.
|-valign="top"
| 2009-12-15
| Since about two weeks linux-ax25.org is suffering from occasional ISP outages. We apologise.
|-valign="top"
| 2009-12-08
| On Friday, 2009-12-11 between 12:00 and 18:00 UTC there is a likely outage for exchange of a broken electricity meter.
|-valign="top"
| 2009-11-20
| linux-ax25.org's software will be upgraded during the next days resulting in downtime of a few hours.
|-valign="top"
| 2009-07-13
| The ISP of linux-ax25.org has announced some scheduled downtime for 2009-08-12. The exact time might change at short notice.
|-valign="top"
| 2009-05-31
| Linux-ax25.org now has an ftp site [ftp://ftp.linux-ax25.org ftp.linux-ax25.org] which hosts historic and current versions of [[ax25-apps]], [[ax25-tools]] and [[libax25]].
|-valign="top"
| 2009-05-29
| The site has moved to a new temporary server system.
|-valign="top"
| 2006-04-19
| Start German version of the site.
|-valign="top"
| 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 ==
[http://www.linux-ax25.org/pub/ax25-apps/ax25-apps-{{Latest-stable-ax25-apps-version}}.tar.gz AX.25 Apps {{Latest-stable-ax25-apps-version}}]<br>
[http://www.linux-ax25.org/pub/ax25-tools/ax25-tools-{{Latest-stable-ax25-tools-version}}.tar.gz AX.25 Tools {{Latest-stable-ax25-tools-version}}]<br>
[http://www.linux-ax25.org/pub/libax25/libax25-{{Latest-stable-libax25-version}}.tar.gz AX.25 Library {{Latest-stable-libax25-version}}]<br>
</div>

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

CVS

2013-06-04T14:11:47Z

DL5RB: linux-ax25.org is switching to git.

''CVS'' has been retired at linux-ax25.org. The anonymous CVS server will stay running so people can continue to do cvs diff and other operations but the content of the archive has been frozen on 2013-06-04. Similarly the cvsweb service will continue to run so links to it will stay valid but of course it won't pick up any further deelopment. All further development will happen on in [[git]]. The remainder of this page is mostly for historical purposes or for those few who have an actual need for it.

== Anonymous CVS ==

For those who always want to stay on the bleeding edge, and want to avoid having to download patch files or full tarballs, we also have an anonymous CVS server. There are currently three amateur radio relevant modules in CVS archive, ''[[libax25]]'', ''[[ax25-apps]]'' and ''[[ax25-tools]]''.

<pre>
cvs -d :pserver:cvs@cvs.linux-ax25.org:/home/ax25-cvs login
(Only needed the first time you use anonymous CVS, the password is "cvs")
cvs -d :pserver:cvs@cvs.linux-ax25.org:/home/ax25-cvs co <module>
</pre>

== The Git CVS server ==

Git now has aquired the ability to deliver it's content over the venerable CVS protocol. Inferior in endless ways, hated with passion and believed to be not very high in demand linux-ax25.org does not provide a git-cvs service.

== Web CVS ==

=== Browse the changes ===
Via [//www.linux-ax25.org/cvsweb cvsweb], you have direct access to the new [[AX.25]] sources. The intuitive interface allows you to follow the development at the click of your mouse.

=== Download as tar archive ===
Automatically generated on the fly as you download these tarballs are always the very latest - with all the risk and benefits of living on the bleeding edge. Building requires recent versions of automake and autoconf.

[//www.linux-ax25.org/cvsweb/libax25/libax25.tar.gz?tarball=1 libax25]
[//www.linux-ax25.org/cvsweb/ax25-apps/ax25-apps.tar.gz?tarball=1 ax25-apps]
[//www.linux-ax25.org/cvsweb/ax25-tools/ax25-tools.tar.gz?tarball=1 ax25-tools]

=== Latest releases ===
The best choice for the OM who just wants to keep his system going along happily. Unlike the raw CVS snapshots above these tarballs don't require any messing with GNU autoconf and automake.

[//www.linux-ax25.org/pub/ax25-apps/ax25-apps-{{Latest-stable-ax25-apps-version}}.tar.gz ax25-apps-{{Latest-stable-ax25-apps-version}}.tar.gz]
[//www.linux-ax25.org/pub/ax25-tools/ax25-tools-{{Latest-stable-ax25-tools-version}}.tar.gz ax25-tools-{{Latest-stable-ax25-tools-version}}.tar.gz]
[//www.linux-ax25.org/pub/libax25/libax25-{{Latest-stable-libax25-version}}.tar.gz libax25-{{Latest-stable-libax25-version}}.tar.gz]

== CVS copy via Rsync ==

The CVS repository can also be fetched using rsync like this:
<pre>
rsync -avz --progress --stats rsync://cvs.linux-ax25.org/cvs/<module> /local/directory
rsync -avz --progress --stats rsync://cvs.linux-ax25.org/cvs/CVSROOT /local/directory
</pre>

You can then check it out using:
<pre>
cvs -d/local/directory co <module>
</pre>

== Quarterly snapshots ==

We plan to automaticaly generate snapshots quarterly, downloadable as tar archives.

== Compilation notes ==

=== Build dependencies ===
install autoconf automake1.9 libtool libncurses-dev

Automake1.4 on debian sarge and etch is known to be incompatible in preconfigureing the hdlcutil FL-Widgets tree.

=== Bootstrap (autoreconf, make) ===

<pre>
for dir in libax25 ax25-apps ax25-tools; do
cd $dir && autoreconf --install --force && \
./configure --prefix=/usr --sysconfdir=/etc --localstatedir=/var --mandir=/usr/share/man && \
make && make install && cd ..
done
</pre>

On a new fresh installation, you should do "make installconf" in the libax25 ax25-apps ax25-tools directories, too.
But be aware, that make installconf overwrites existing configuration files in /etc/ax25/.

Note: earlier versions had a bootstrap script (with aclocal, autoconf and an appropriate ./configure line) but these days <em>autoreconf</em> should be used.

=== Ax25-apps naming conflicts ===
<tt>ax25-apps</tt> installs two program named <tt>call</tt> and <tt>listen</tt>. Despite <tt>ax25-apps</tt> using these names for longer than other packages various Linux distributions including [http://www.debian.org/ Debian] and [http://www.fedoraproject.org Fedora] have elected to rename these binaries. When building <tt>ax25-apps</tt> you want to make sure there are no such conflicts. Standard GNU autoconf which is being used by <tt>ax25-apps</tt> for configuration supports such renaming through the powerful but obscure <tt>--program-transform-name</tt> option like this:

<pre>
./configure --program-transform-name='s@^call@axcall@;s@^listen@axlisten@' --prefix=/usr --sysconfdir=/etc --localstatedir=/var --mandir=/usr/share/man
</pre>

This will install the <tt>call</tt> program and its man page as <tt>axcall</tt> and <tt>listen</tt> as <tt>axlisten</tt>. The argument of --program-transform-name is a <tt>sed(1)</tt> program; adjust as need for your installation. Because this is a standard feature of <tt>GNU autoconf</tt>, all versions of <tt>ax25-apps</tt> and also <tt>ax25-tools</tt> support this.

Versions of ax25-apps from 2011-12-11 or newer also honour the <tt>--program-transform-name</tt>, <tt>--program-prefix</tt> and <tt>--program-suffix</tt> options for the content and cross references of the man pages.

=== 64-bit systems ===
Most 64-bit systems are setup such that libs go to <tt>/lib64</tt> <tt>/usr/lib64</tt>, <tt>/usr/local/lib64</tt>. Autoconf won't notice this; it will default libdir to <prefix>/lib. This means installation will overwrite whatever is there possibly damaging 32-bit compat versions of the libraries installed there. To get autoconf to do the right thing in this case you must pass --libdir=<prefix>/lib64 when configuring.

== Maintainers ==

Maintainers for ax25-apps, ax25-tools and libax25 are

* [mailto:Ralf%20Baechle%20%3cralf@linux-mips.org%3e Ralf Baechle DL5RB <ralf@linux-mips.org>]
* [mailto:Thomas%20Osterried%20%3cax25@x-berg.in-berlin.de%3e Thomas Osterried DL9SAU <ax25@x-berg.in-berlin.de>]

Please feel free to contact us in case of problems, bugs or fixes, patches, enhancements, feature requests, or just for your personal success story.

[[de:CVS]]

Template:Latest-stable-ax25-apps-version

2013-06-04T13:47:17Z

DL5RB: 0.0.8-rc3

0.0.8-rc3

Template:Latest-stable-ax25-tools-version

2013-06-04T13:46:45Z

DL5RB: ax25-tools 0.0.10-rc3

0.0.10-rc3

Template:Latest-stable-libax25-version

2013-06-04T13:45:50Z

DL5RB: libax25 0.0.12-rc3

0.0.12-rc3

Main Page

2013-04-02T07:29:30Z

DL5RB: Fix more cut'n'paste type errors in domain errors as noticed by [User:VK4MSL]

__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 ==
{| border="0" cellpadding="4" cellspacing="0" valign="top" style="margin: 1em 1em 1em 0; background: #ffe0c0; border-collapse: collapse;"
|-valign="top"
| 2011-11-04
| All SSL certificates for linux-ax25.org have been refreshed. As a reminder, linux-ax25.org uses [http://www.cacert.org CAcert] certificates and the root certificate for CAcert.org (available [http://www.cacert.org/index.php?id=3 here] is not included with all operating systems and browsers yet so you may have to manually install it if you want to use linux-ax25.org's services encryptedly.
|-valign="top"
| 2011-09-07
| The recent [http://lwn.net/Articles/457142/ compromise] of a kernel.org servers has resulted in some of kernel.org's servers providing DNS service to linux-ax25.org becoming unavailable. A temporary solution is now in place.
|-valign="top"
| 2011-08-18
| A fix for [http://www.cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2011-2910 CVE-2011-2910] ([https://www.redhat.com/security/data/cve/CVE-2011-2910.html Red Hat CVE database], [https://bugzilla.redhat.com/show_bug.cgi?id=730783 Red Hat Bug 730783], [https://bugzilla.redhat.com/show_bug.cgi?id=730784 Red Hat Bug 830784], [http://security-tracker.debian.org/tracker/CVE-2011-2910 Debian security tracker], [http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=638198 Debian Bug 638198]) has been checked into [[CVS]]. The impact of this issue is low as the circumstances that trigger the issue should not normally encountered on a correctly configured system. See also related [http://www.openwall.com/lists/oss-security/2011/08/ discussion] on the oss-security mailing list under the subject "CVE request (and disclosure): ax25d missing setuid return code check".
|-valign="top"
| 2010-06-10
| Linux-ax25.org now is SSL-enabled.
|-valign="top"
| 2010-03-29
| Due to hardware defects the site was running from an outdated copy for a while. The problem has been rectified now. Sorry for the inconvenience.
|-valign="top"
| 2009-12-15
| Since about two weeks linux-ax25.org is suffering from occasional ISP outages. We apologise.
|-valign="top"
| 2009-12-08
| On Friday, 2009-12-11 between 12:00 and 18:00 UTC there is a likely outage for exchange of a broken electricity meter.
|-valign="top"
| 2009-11-20
| linux-ax25.org's software will be upgraded during the next days resulting in downtime of a few hours.
|-valign="top"
| 2009-07-13
| The ISP of linux-ax25.org has announced some scheduled downtime for 2009-08-12. The exact time might change at short notice.
|-valign="top"
| 2009-05-31
| Linux-ax25.org now has an ftp site [ftp://ftp.linux-ax25.org ftp.linux-ax25.org] which hosts historic and current versions of [[ax25-apps]], [[ax25-tools]] and [[libax25]].
|-valign="top"
| 2009-05-29
| The site has moved to a new temporary server system.
|-valign="top"
| 2006-04-19
| Start German version of the site.
|-valign="top"
| 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 ==
[http://www.linux-ax25.org/pub/ax25-apps/ax25-apps-{{Latest-stable-ax25-apps-version}}.tar.gz AX.25 Apps {{Latest-stable-ax25-apps-version}}]<br>
[http://www.linux-ax25.org/pub/ax25-tools/ax25-tools-{{Latest-stable-ax25-tools-version}}.tar.gz AX.25 Tools {{Latest-stable-ax25-tools-version}}]<br>
[http://www.linux-ax25.org/pub/libax25/libax25-{{Latest-stable-libax25-version}}.tar.gz AX.25 Library {{Latest-stable-libax25-version}}]<br>
</div>

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

Main Page

2012-06-21T16:18:59Z

DL5RB: /* News */ Fix cut and paste error in domain name.

__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 ==
{| border="0" cellpadding="4" cellspacing="0" valign="top" style="margin: 1em 1em 1em 0; background: #ffe0c0; border-collapse: collapse;"
|-valign="top"
| 2011-11-04
| All SSL certificates for linux-ax25.org have been refreshed. As a reminder, linux-ax25.org uses [http://www.cacert.org CAcert] certificates and the root certificate for CAcert.org (available [http://www.cacert.org/index.php?id=3 here] is not included with all operating systems and browsers yet so you may have to manually install it if you want to use linux-mips.org's services encryptedly.
|-valign="top"
| 2011-09-07
| The recent [http://lwn.net/Articles/457142/ compromise] of a kernel.org servers has resulted in some of kernel.org's servers providing DNS service to linux-mips.org becoming unavailable. A temporary solution is now in place.
|-valign="top"
| 2011-08-18
| A fix for [http://www.cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2011-2910 CVE-2011-2910] ([https://www.redhat.com/security/data/cve/CVE-2011-2910.html Red Hat CVE database], [https://bugzilla.redhat.com/show_bug.cgi?id=730783 Red Hat Bug 730783], [https://bugzilla.redhat.com/show_bug.cgi?id=730784 Red Hat Bug 830784], [http://security-tracker.debian.org/tracker/CVE-2011-2910 Debian security tracker], [http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=638198 Debian Bug 638198]) has been checked into [[CVS]]. The impact of this issue is low as the circumstances that trigger the issue should not normally encountered on a correctly configured system. See also related [http://www.openwall.com/lists/oss-security/2011/08/ discussion] on the oss-security mailing list under the subject "CVE request (and disclosure): ax25d missing setuid return code check".
|-valign="top"
| 2010-06-10
| Linux-ax25.org now is SSL-enabled.
|-valign="top"
| 2010-03-29
| Due to hardware defects the site was running from an outdated copy for a while. The problem has been rectified now. Sorry for the inconvenience.
|-valign="top"
| 2009-12-15
| Since about two weeks linux-ax25.org is suffering from occasional ISP outages. We apologise.
|-valign="top"
| 2009-12-08
| On Friday, 2009-12-11 between 12:00 and 18:00 UTC there is a likely outage for exchange of a broken electricity meter.
|-valign="top"
| 2009-11-20
| linux-ax25.org's software will be upgraded during the next days resulting in downtime of a few hours.
|-valign="top"
| 2009-07-13
| The ISP of linux-ax25.org has announced some scheduled downtime for 2009-08-12. The exact time might change at short notice.
|-valign="top"
| 2009-05-31
| Linux-ax25.org now has an ftp site [ftp://ftp.linux-ax25.org ftp.linux-ax25.org] which hosts historic and current versions of [[ax25-apps]], [[ax25-tools]] and [[libax25]].
|-valign="top"
| 2009-05-29
| The site has moved to a new temporary server system.
|-valign="top"
| 2006-04-19
| Start German version of the site.
|-valign="top"
| 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 ==
[http://www.linux-ax25.org/pub/ax25-apps/ax25-apps-{{Latest-stable-ax25-apps-version}}.tar.gz AX.25 Apps {{Latest-stable-ax25-apps-version}}]<br>
[http://www.linux-ax25.org/pub/ax25-tools/ax25-tools-{{Latest-stable-ax25-tools-version}}.tar.gz AX.25 Tools {{Latest-stable-ax25-tools-version}}]<br>
[http://www.linux-ax25.org/pub/libax25/libax25-{{Latest-stable-libax25-version}}.tar.gz AX.25 Library {{Latest-stable-libax25-version}}]<br>
</div>

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

CVS

2011-12-11T23:18:33Z

DL5RB: /* Ax25-apps naming conflicts */ Update to the latest status.

== Anonymous CVS ==

For those who always want to stay on the bleeding edge, and want to avoid having to download patch files or full tarballs, we also have an anonymous CVS server. There are currently three amateur radio relevant modules in CVS archive, ''[[libax25]]'', ''[[ax25-apps]]'' and ''[[ax25-tools]]''.

<pre>
cvs -d :pserver:cvs@cvs.linux-ax25.org:/home/ax25-cvs login
(Only needed the first time you use anonymous CVS, the password is "cvs")
cvs -d :pserver:cvs@cvs.linux-ax25.org:/home/ax25-cvs co <module>
</pre>

== Web CVS ==

=== Browse the changes ===
Via [//www.linux-ax25.org/cvsweb cvsweb], you have direct access to the new [[AX.25]] sources. The intuitive interface allows you to follow the development at the click of your mouse.

=== Download as tar archive ===
Automatically generated on the fly as you download these tarballs are always the very latest - with all the risk and benefits of living on the bleeding edge. Building requires recent versions of automake and autoconf.

[//www.linux-ax25.org/cvsweb/libax25/libax25.tar.gz?tarball=1 libax25]
[//www.linux-ax25.org/cvsweb/ax25-apps/ax25-apps.tar.gz?tarball=1 ax25-apps]
[//www.linux-ax25.org/cvsweb/ax25-tools/ax25-tools.tar.gz?tarball=1 ax25-tools]

=== Latest releases ===
The best choice for the OM who just wants to keep his system going along happily. Unlike the raw CVS snapshots above these tarballs don't require any messing with GNU autoconf and automake.

[//www.linux-ax25.org/pub/ax25-apps/ax25-apps-{{Latest-stable-ax25-apps-version}}.tar.gz ax25-apps-{{Latest-stable-ax25-apps-version}}.tar.gz]
[//www.linux-ax25.org/pub/ax25-tools/ax25-tools-{{Latest-stable-ax25-tools-version}}.tar.gz ax25-tools-{{Latest-stable-ax25-tools-version}}.tar.gz]
[//www.linux-ax25.org/pub/libax25/libax25-{{Latest-stable-libax25-version}}.tar.gz libax25-{{Latest-stable-libax25-version}}.tar.gz]

== CVS copy via Rsync ==

The CVS repository can also be fetched using rsync like this:
<pre>
rsync -avz --progress --stats rsync://cvs.linux-ax25.org/cvs/<module> /local/directory
rsync -avz --progress --stats rsync://cvs.linux-ax25.org/cvs/CVSROOT /local/directory
</pre>

You can then check it out using:
<pre>
cvs -d/local/directory co <module>
</pre>

== Quarterly snapshots ==

We plan to automaticaly generate snapshots quarterly, downloadable as tar archives.

== Compilation notes ==

=== Build dependencies ===
install autoconf automake1.9 libtool libncurses-dev

Automake1.4 on debian sarge and etch is known to be incompatible in preconfigureing the hdlcutil FL-Widgets tree.

=== Bootstrap (autoreconf, make) ===

<pre>
for dir in libax25 ax25-apps ax25-tools; do
cd $dir && autoreconf --install --force && \
./configure --prefix=/usr --sysconfdir=/etc --localstatedir=/var --mandir=/usr/share/man && \
make && make install && cd ..
done
</pre>

On a new fresh installation, you should do "make installconf" in the libax25 ax25-apps ax25-tools directories, too.
But be aware, that make installconf overwrites existing configuration files in /etc/ax25/.

Note: earlier versions had a bootstrap script (with aclocal, autoconf and an appropriate ./configure line) but these days <em>autoreconf</em> should be used.

=== Ax25-apps naming conflicts ===
<tt>ax25-apps</tt> installs two program named <tt>call</tt> and <tt>listen</tt>. Despite <tt>ax25-apps</tt> using these names for longer than other packages various Linux distributions including [http://www.debian.org/ Debian] and [http://www.fedoraproject.org Fedora] have elected to rename these binaries. When building <tt>ax25-apps</tt> you want to make sure there are no such conflicts. Standard GNU autoconf which is being used by <tt>ax25-apps</tt> for configuration supports such renaming through the powerful but obscure <tt>--program-transform-name</tt> option like this:

<pre>
./configure --program-transform-name='s@^call@axcall@;s@^listen@axlisten@' --prefix=/usr --sysconfdir=/etc --localstatedir=/var --mandir=/usr/share/man
</pre>

This will install the <tt>call</tt> program and its man page as <tt>axcall</tt> and <tt>listen</tt> as <tt>axlisten</tt>. The argument of --program-transform-name is a <tt>sed(1)</tt> program; adjust as need for your installation. Because this is a standard feature of <tt>GNU autoconf</tt>, all versions of <tt>ax25-apps</tt> and also <tt>ax25-tools</tt> support this.

Versions of ax25-apps from 2011-12-11 or newer also honour the <tt>--program-transform-name</tt>, <tt>--program-prefix</tt> and <tt>--program-suffix</tt> options for the content and cross references of the man pages.

=== 64-bit systems ===
Most 64-bit systems are setup such that libs go to <tt>/lib64</tt> <tt>/usr/lib64</tt>, <tt>/usr/local/lib64</tt>. Autoconf won't notice this; it will default libdir to <prefix>/lib. This means installation will overwrite whatever is there possibly damaging 32-bit compat versions of the libraries installed there. To get autoconf to do the right thing in this case you must pass --libdir=<prefix>/lib64 when configuring.

== Maintainers ==

Maintainers for ax25-apps, ax25-tools and libax25 are

* [mailto:Ralf%20Baechle%20%3cralf@linux-mips.org%3e Ralf Baechle DL5RB <ralf@linux-mips.org>]
* [mailto:Thomas%20Osterried%20%3cax25@x-berg.in-berlin.de%3e Thomas Osterried DL9SAU <ax25@x-berg.in-berlin.de>]

Please feel free to contact us in case of problems, bugs or fixes, patches, enhancements, feature requests, or just for your personal success story.

[[de:CVS]]

CVS

2011-12-11T17:58:39Z

DL5RB: /* Naming conflicts */

== Anonymous CVS ==

For those who always want to stay on the bleeding edge, and want to avoid having to download patch files or full tarballs, we also have an anonymous CVS server. There are currently three amateur radio relevant modules in CVS archive, ''[[libax25]]'', ''[[ax25-apps]]'' and ''[[ax25-tools]]''.

<pre>
cvs -d :pserver:cvs@cvs.linux-ax25.org:/home/ax25-cvs login
(Only needed the first time you use anonymous CVS, the password is "cvs")
cvs -d :pserver:cvs@cvs.linux-ax25.org:/home/ax25-cvs co <module>
</pre>

== Web CVS ==

=== Browse the changes ===
Via [//www.linux-ax25.org/cvsweb cvsweb], you have direct access to the new [[AX.25]] sources. The intuitive interface allows you to follow the development at the click of your mouse.

=== Download as tar archive ===
Automatically generated on the fly as you download these tarballs are always the very latest - with all the risk and benefits of living on the bleeding edge. Building requires recent versions of automake and autoconf.

[//www.linux-ax25.org/cvsweb/libax25/libax25.tar.gz?tarball=1 libax25]
[//www.linux-ax25.org/cvsweb/ax25-apps/ax25-apps.tar.gz?tarball=1 ax25-apps]
[//www.linux-ax25.org/cvsweb/ax25-tools/ax25-tools.tar.gz?tarball=1 ax25-tools]

=== Latest releases ===
The best choice for the OM who just wants to keep his system going along happily. Unlike the raw CVS snapshots above these tarballs don't require any messing with GNU autoconf and automake.

[//www.linux-ax25.org/pub/ax25-apps/ax25-apps-{{Latest-stable-ax25-apps-version}}.tar.gz ax25-apps-{{Latest-stable-ax25-apps-version}}.tar.gz]
[//www.linux-ax25.org/pub/ax25-tools/ax25-tools-{{Latest-stable-ax25-tools-version}}.tar.gz ax25-tools-{{Latest-stable-ax25-tools-version}}.tar.gz]
[//www.linux-ax25.org/pub/libax25/libax25-{{Latest-stable-libax25-version}}.tar.gz libax25-{{Latest-stable-libax25-version}}.tar.gz]

== CVS copy via Rsync ==

The CVS repository can also be fetched using rsync like this:
<pre>
rsync -avz --progress --stats rsync://cvs.linux-ax25.org/cvs/<module> /local/directory
rsync -avz --progress --stats rsync://cvs.linux-ax25.org/cvs/CVSROOT /local/directory
</pre>

You can then check it out using:
<pre>
cvs -d/local/directory co <module>
</pre>

== Quarterly snapshots ==

We plan to automaticaly generate snapshots quarterly, downloadable as tar archives.

== Compilation notes ==

=== Build dependencies ===
install autoconf automake1.9 libtool libncurses-dev

Automake1.4 on debian sarge and etch is known to be incompatible in preconfigureing the hdlcutil FL-Widgets tree.

=== Bootstrap (autoreconf, make) ===

<pre>
for dir in libax25 ax25-apps ax25-tools; do
cd $dir && autoreconf --install --force && \
./configure --prefix=/usr --sysconfdir=/etc --localstatedir=/var --mandir=/usr/share/man && \
make && make install && cd ..
done
</pre>

On a new fresh installation, you should do "make installconf" in the libax25 ax25-apps ax25-tools directories, too.
But be aware, that make installconf overwrites existing configuration files in /etc/ax25/.

Note: earlier versions had a bootstrap script (with aclocal, autoconf and an appropriate ./configure line) but these days <em>autoreconf</em> should be used.

=== Ax25-apps naming conflicts ===
<tt>ax25-apps</tt> installs two program named <tt>call</tt> and <tt>listen</tt>. Despite <tt>ax25-apps</tt> using these names for longer than other packages various Linux distributions including [http://www.debian.org/ Debian] and [http://www.fedoraproject.org Fedora] have elected to rename these binaries. When building <tt>ax25-apps</tt> you want to make sure there are no such conflicts. Standard GNU autoconf which is being used by <tt>ax25-apps</tt> for configuration supports such renaming through the powerful but obscure <tt>--program-transform-name</tt> option like this:

<pre>
./configure --program-transform-name='s@^call@axcall@;s@^listen@axlisten@' --prefix=/usr --sysconfdir=/etc --localstatedir=/var --mandir=/usr/share/man
</pre>

This will install the <tt>call</tt> program and its man page as <tt>axcall</tt> and <tt>listen</tt> as <tt>axlisten</tt>. The argument of --program-transform-name is a <tt>sed(1)</tt> program; adjust as need for your installation. Because this is a standard feature of <tt>GNU autoconf</tt>, all versions of <tt>ax25-apps</tt> and also <tt>ax25-tools</tt> support this.

CVS versions from 2011-12-11 or newer also honour the <tt>--program-transform-name</tt>, <tt>--program-prefix</tt> and <tt>--program-suffix</tt> options for the content and cross references of the <tt>call(1)</tt> and <tt>listen(1)</tt> man pages.

=== 64-bit systems ===
Most 64-bit systems are setup such that libs go to <tt>/lib64</tt> <tt>/usr/lib64</tt>, <tt>/usr/local/lib64</tt>. Autoconf won't notice this; it will default libdir to <prefix>/lib. This means installation will overwrite whatever is there possibly damaging 32-bit compat versions of the libraries installed there. To get autoconf to do the right thing in this case you must pass --libdir=<prefix>/lib64 when configuring.

== Maintainers ==

Maintainers for ax25-apps, ax25-tools and libax25 are

* [mailto:Ralf%20Baechle%20%3cralf@linux-mips.org%3e Ralf Baechle DL5RB <ralf@linux-mips.org>]
* [mailto:Thomas%20Osterried%20%3cax25@x-berg.in-berlin.de%3e Thomas Osterried DL9SAU <ax25@x-berg.in-berlin.de>]

Please feel free to contact us in case of problems, bugs or fixes, patches, enhancements, feature requests, or just for your personal success story.

[[de:CVS]]

CVS

2011-12-10T10:48:34Z

DL5RB: /* Naming conflicts */

== Anonymous CVS ==

For those who always want to stay on the bleeding edge, and want to avoid having to download patch files or full tarballs, we also have an anonymous CVS server. There are currently three amateur radio relevant modules in CVS archive, ''[[libax25]]'', ''[[ax25-apps]]'' and ''[[ax25-tools]]''.

<pre>
cvs -d :pserver:cvs@cvs.linux-ax25.org:/home/ax25-cvs login
(Only needed the first time you use anonymous CVS, the password is "cvs")
cvs -d :pserver:cvs@cvs.linux-ax25.org:/home/ax25-cvs co <module>
</pre>

== Web CVS ==

=== Browse the changes ===
Via [//www.linux-ax25.org/cvsweb cvsweb], you have direct access to the new [[AX.25]] sources. The intuitive interface allows you to follow the development at the click of your mouse.

=== Download as tar archive ===
Automatically generated on the fly as you download these tarballs are always the very latest - with all the risk and benefits of living on the bleeding edge. Building requires recent versions of automake and autoconf.

[//www.linux-ax25.org/cvsweb/libax25/libax25.tar.gz?tarball=1 libax25]
[//www.linux-ax25.org/cvsweb/ax25-apps/ax25-apps.tar.gz?tarball=1 ax25-apps]
[//www.linux-ax25.org/cvsweb/ax25-tools/ax25-tools.tar.gz?tarball=1 ax25-tools]

=== Latest releases ===
The best choice for the OM who just wants to keep his system going along happily. Unlike the raw CVS snapshots above these tarballs don't require any messing with GNU autoconf and automake.

[//www.linux-ax25.org/pub/ax25-apps/ax25-apps-{{Latest-stable-ax25-apps-version}}.tar.gz ax25-apps-{{Latest-stable-ax25-apps-version}}.tar.gz]
[//www.linux-ax25.org/pub/ax25-tools/ax25-tools-{{Latest-stable-ax25-tools-version}}.tar.gz ax25-tools-{{Latest-stable-ax25-tools-version}}.tar.gz]
[//www.linux-ax25.org/pub/libax25/libax25-{{Latest-stable-libax25-version}}.tar.gz libax25-{{Latest-stable-libax25-version}}.tar.gz]

== CVS copy via Rsync ==

The CVS repository can also be fetched using rsync like this:
<pre>
rsync -avz --progress --stats rsync://cvs.linux-ax25.org/cvs/<module> /local/directory
rsync -avz --progress --stats rsync://cvs.linux-ax25.org/cvs/CVSROOT /local/directory
</pre>

You can then check it out using:
<pre>
cvs -d/local/directory co <module>
</pre>

== Quarterly snapshots ==

We plan to automaticaly generate snapshots quarterly, downloadable as tar archives.

== Compilation notes ==

=== Build dependencies ===
install autoconf automake1.9 libtool libncurses-dev

Automake1.4 on debian sarge and etch is known to be incompatible in preconfigureing the hdlcutil FL-Widgets tree.

=== Bootstrap (autoreconf, make) ===

<pre>
for dir in libax25 ax25-apps ax25-tools; do
cd $dir && autoreconf --install --force && \
./configure --prefix=/usr --sysconfdir=/etc --localstatedir=/var --mandir=/usr/share/man && \
make && make install && cd ..
done
</pre>

On a new fresh installation, you should do "make installconf" in the libax25 ax25-apps ax25-tools directories, too.
But be aware, that make installconf overwrites existing configuration files in /etc/ax25/.

Note: earlier versions had a bootstrap script (with aclocal, autoconf and an appropriate ./configure line) but these days <em>autoreconf</em> should be used.

=== Naming conflicts ===
<tt>ax25-apps</tt> installs two program named <tt>call</tt> and <tt>listen</tt>. Despite <tt>ax25-apps</tt> using these names for longer than other packages various Linux distributions including [http://www.debian.org/ Debian] and [http://www.fedoraproject.org Fedora] have elected to rename these binaries. When building <tt>ax25-apps</tt> you want to make sure there are no such conflicts. Standard GNU autoconf which is being used by <tt>ax25-apps</tt> for configuration supports such renaming through the powerful but obscure <tt>--program-transform-name</tt> option like this:

<pre>
./configure --program-transform-name='s@^call@axcall@;s@^listen@axlisten@' --prefix=/usr --sysconfdir=/etc --localstatedir=/var --mandir=/usr/share/man
</pre>

This will install the <tt>call</tt> program and its man page as <tt>axcall</tt> and <tt>listen</tt> as <tt>axlisten</tt>. The argument of --program-transform-name is a <tt>sed(1)</tt> program; adjust as need for your installation. Because this is a standard feature of <tt>GNU autoconf</tt>, all versions of <tt>ax25-apps</tt> and also <tt>ax25-tools</tt> support this.

=== 64-bit systems ===
Most 64-bit systems are setup such that libs go to <tt>/lib64</tt> <tt>/usr/lib64</tt>, <tt>/usr/local/lib64</tt>. Autoconf won't notice this; it will default libdir to <prefix>/lib. This means installation will overwrite whatever is there possibly damaging 32-bit compat versions of the libraries installed there. To get autoconf to do the right thing in this case you must pass --libdir=<prefix>/lib64 when configuring.

== Maintainers ==

Maintainers for ax25-apps, ax25-tools and libax25 are

* [mailto:Ralf%20Baechle%20%3cralf@linux-mips.org%3e Ralf Baechle DL5RB <ralf@linux-mips.org>]
* [mailto:Thomas%20Osterried%20%3cax25@x-berg.in-berlin.de%3e Thomas Osterried DL9SAU <ax25@x-berg.in-berlin.de>]

Please feel free to contact us in case of problems, bugs or fixes, patches, enhancements, feature requests, or just for your personal success story.

[[de:CVS]]

CVS

2011-12-10T09:29:21Z

DL5RB: /* Naming conflicts */

== Anonymous CVS ==

For those who always want to stay on the bleeding edge, and want to avoid having to download patch files or full tarballs, we also have an anonymous CVS server. There are currently three amateur radio relevant modules in CVS archive, ''[[libax25]]'', ''[[ax25-apps]]'' and ''[[ax25-tools]]''.

<pre>
cvs -d :pserver:cvs@cvs.linux-ax25.org:/home/ax25-cvs login
(Only needed the first time you use anonymous CVS, the password is "cvs")
cvs -d :pserver:cvs@cvs.linux-ax25.org:/home/ax25-cvs co <module>
</pre>

== Web CVS ==

=== Browse the changes ===
Via [//www.linux-ax25.org/cvsweb cvsweb], you have direct access to the new [[AX.25]] sources. The intuitive interface allows you to follow the development at the click of your mouse.

=== Download as tar archive ===
Automatically generated on the fly as you download these tarballs are always the very latest - with all the risk and benefits of living on the bleeding edge. Building requires recent versions of automake and autoconf.

[//www.linux-ax25.org/cvsweb/libax25/libax25.tar.gz?tarball=1 libax25]
[//www.linux-ax25.org/cvsweb/ax25-apps/ax25-apps.tar.gz?tarball=1 ax25-apps]
[//www.linux-ax25.org/cvsweb/ax25-tools/ax25-tools.tar.gz?tarball=1 ax25-tools]

=== Latest releases ===
The best choice for the OM who just wants to keep his system going along happily. Unlike the raw CVS snapshots above these tarballs don't require any messing with GNU autoconf and automake.

[//www.linux-ax25.org/pub/ax25-apps/ax25-apps-{{Latest-stable-ax25-apps-version}}.tar.gz ax25-apps-{{Latest-stable-ax25-apps-version}}.tar.gz]
[//www.linux-ax25.org/pub/ax25-tools/ax25-tools-{{Latest-stable-ax25-tools-version}}.tar.gz ax25-tools-{{Latest-stable-ax25-tools-version}}.tar.gz]
[//www.linux-ax25.org/pub/libax25/libax25-{{Latest-stable-libax25-version}}.tar.gz libax25-{{Latest-stable-libax25-version}}.tar.gz]

== CVS copy via Rsync ==

The CVS repository can also be fetched using rsync like this:
<pre>
rsync -avz --progress --stats rsync://cvs.linux-ax25.org/cvs/<module> /local/directory
rsync -avz --progress --stats rsync://cvs.linux-ax25.org/cvs/CVSROOT /local/directory
</pre>

You can then check it out using:
<pre>
cvs -d/local/directory co <module>
</pre>

== Quarterly snapshots ==

We plan to automaticaly generate snapshots quarterly, downloadable as tar archives.

== Compilation notes ==

=== Build dependencies ===
install autoconf automake1.9 libtool libncurses-dev

Automake1.4 on debian sarge and etch is known to be incompatible in preconfigureing the hdlcutil FL-Widgets tree.

=== Bootstrap (autoreconf, make) ===

<pre>
for dir in libax25 ax25-apps ax25-tools; do
cd $dir && autoreconf --install --force && \
./configure --prefix=/usr --sysconfdir=/etc --localstatedir=/var --mandir=/usr/share/man && \
make && make install && cd ..
done
</pre>

On a new fresh installation, you should do "make installconf" in the libax25 ax25-apps ax25-tools directories, too.
But be aware, that make installconf overwrites existing configuration files in /etc/ax25/.

Note: earlier versions had a bootstrap script (with aclocal, autoconf and an appropriate ./configure line) but these days <em>autoreconf</em> should be used.

=== Naming conflicts ===
<tt>ax25-apps</tt> installs two program named <tt>call</tt> and <tt>listen</tt>. Despite <tt>ax25-apps</tt> using these names for longer than other packages various Linux distributions including [http://www.debian.org/ Debian] and [http://www.fedoraproject.org Fedora] have elected to rename these binaries. When building <tt>ax25-apps</tt> you want to make sure there are no such conflicts. Standard GNU autoconf which is being used by <tt>ax25-apps</tt> for configuration supports such renaming through the powerful but obscure <tt>--program-transform-name</tt> option like this:

<pre>
./configure --program-transform-name='s@call@axcall@;s@listen@axlisten@' --prefix=/usr --sysconfdir=/etc --localstatedir=/var --mandir=/usr/share/man
</pre>

This will install the <tt>call</tt> program and its man page as <tt>axcall</tt> and <tt>listen</tt> as <tt>axlisten</tt>. The argument of --program-transform-name is a <tt>sed(1)</tt> program; adjust as need for your installation. Because this is a standard feature of <tt>GNU autoconf</tt>, all versions of <tt>ax25-apps</tt> and also <tt>ax25-tools</tt> support this.

=== 64-bit systems ===
Most 64-bit systems are setup such that libs go to <tt>/lib64</tt> <tt>/usr/lib64</tt>, <tt>/usr/local/lib64</tt>. Autoconf won't notice this; it will default libdir to <prefix>/lib. This means installation will overwrite whatever is there possibly damaging 32-bit compat versions of the libraries installed there. To get autoconf to do the right thing in this case you must pass --libdir=<prefix>/lib64 when configuring.

== Maintainers ==

Maintainers for ax25-apps, ax25-tools and libax25 are

* [mailto:Ralf%20Baechle%20%3cralf@linux-mips.org%3e Ralf Baechle DL5RB <ralf@linux-mips.org>]
* [mailto:Thomas%20Osterried%20%3cax25@x-berg.in-berlin.de%3e Thomas Osterried DL9SAU <ax25@x-berg.in-berlin.de>]

Please feel free to contact us in case of problems, bugs or fixes, patches, enhancements, feature requests, or just for your personal success story.

[[de:CVS]]

CVS

2011-12-06T16:14:55Z

DL5RB: /* Maintainers */ Include full name in mailto addresses.

== Anonymous CVS ==

For those who always want to stay on the bleeding edge, and want to avoid having to download patch files or full tarballs, we also have an anonymous CVS server. There are currently three amateur radio relevant modules in CVS archive, ''[[libax25]]'', ''[[ax25-apps]]'' and ''[[ax25-tools]]''.

<pre>
cvs -d :pserver:cvs@cvs.linux-ax25.org:/home/ax25-cvs login
(Only needed the first time you use anonymous CVS, the password is "cvs")
cvs -d :pserver:cvs@cvs.linux-ax25.org:/home/ax25-cvs co <module>
</pre>

== Web CVS ==

=== Browse the changes ===
Via [//www.linux-ax25.org/cvsweb cvsweb], you have direct access to the new [[AX.25]] sources. The intuitive interface allows you to follow the development at the click of your mouse.

=== Download as tar archive ===
Automatically generated on the fly as you download these tarballs are always the very latest - with all the risk and benefits of living on the bleeding edge. Building requires recent versions of automake and autoconf.

[//www.linux-ax25.org/cvsweb/libax25/libax25.tar.gz?tarball=1 libax25]
[//www.linux-ax25.org/cvsweb/ax25-apps/ax25-apps.tar.gz?tarball=1 ax25-apps]
[//www.linux-ax25.org/cvsweb/ax25-tools/ax25-tools.tar.gz?tarball=1 ax25-tools]

=== Latest releases ===
The best choice for the OM who just wants to keep his system going along happily. Unlike the raw CVS snapshots above these tarballs don't require any messing with GNU autoconf and automake.

[//www.linux-ax25.org/pub/ax25-apps/ax25-apps-{{Latest-stable-ax25-apps-version}}.tar.gz ax25-apps-{{Latest-stable-ax25-apps-version}}.tar.gz]
[//www.linux-ax25.org/pub/ax25-tools/ax25-tools-{{Latest-stable-ax25-tools-version}}.tar.gz ax25-tools-{{Latest-stable-ax25-tools-version}}.tar.gz]
[//www.linux-ax25.org/pub/libax25/libax25-{{Latest-stable-libax25-version}}.tar.gz libax25-{{Latest-stable-libax25-version}}.tar.gz]

== CVS copy via Rsync ==

The CVS repository can also be fetched using rsync like this:
<pre>
rsync -avz --progress --stats rsync://cvs.linux-ax25.org/cvs/<module> /local/directory
rsync -avz --progress --stats rsync://cvs.linux-ax25.org/cvs/CVSROOT /local/directory
</pre>

You can then check it out using:
<pre>
cvs -d/local/directory co <module>
</pre>

== Quarterly snapshots ==

We plan to automaticaly generate snapshots quarterly, downloadable as tar archives.

== Compilation notes ==

=== Build dependencies ===
install autoconf automake1.9 libtool libncurses-dev

Automake1.4 on debian sarge and etch is known to be incompatible in preconfigureing the hdlcutil FL-Widgets tree.

=== Bootstrap (autoreconf, make) ===

<pre>
for dir in libax25 ax25-apps ax25-tools; do
cd $dir && autoreconf --install --force && \
./configure --prefix=/usr --sysconfdir=/etc --localstatedir=/var --mandir=/usr/share/man && \
make && make install && cd ..
done
</pre>

On a new fresh installation, you should do "make installconf" in the libax25 ax25-apps ax25-tools directories, too.
But be aware, that make installconf overwrites existing configuration files in /etc/ax25/.

Note: earlier versions had a bootstrap script (with aclocal, autoconf and an appropriate ./configure line) but these days <em>autoreconf</em> should be used.

=== Naming conflicts ===
<tt>ax25-apps</tt> installs two program named <tt>call</tt> and <tt>listen</tt>. Despite <tt>ax25-apps</tt> using these names for longer than other packages various Linux distributions including [http://www.debian.org/ Debian] and [http://www.fedoraproject.org Fedora] have elected to rename these binaries. When building <tt>ax25-apps</tt> you want to make sure there are no such conflicts. Standard GNU autoconf which is being used by <tt>ax25-apps</tt> for configuration supports such renaming through the powerful but obscure <tt>--program-transform-name</tt> option like this:

<pre>
./configure --program-transform-name='s@call@axscall@;s@listen@axlisten@' --prefix=/usr --sysconfdir=/etc --localstatedir=/var --mandir=/usr/share/man
</pre>

This will install the <tt>call</tt> program and its man page as <tt>axcall</tt> and <tt>listen</tt> as <tt>axlisten</tt>. The argument of --program-transform-name is a <tt>sed(1)</tt> program; adjust as need for your installation. Because this is a standard feature of <tt>GNU autoconf</tt>, all versions of <tt>ax25-apps</tt> and also <tt>ax25-tools</tt> support this.

=== 64-bit systems ===
Most 64-bit systems are setup such that libs go to <tt>/lib64</tt> <tt>/usr/lib64</tt>, <tt>/usr/local/lib64</tt>. Autoconf won't notice this; it will default libdir to <prefix>/lib. This means installation will overwrite whatever is there possibly damaging 32-bit compat versions of the libraries installed there. To get autoconf to do the right thing in this case you must pass --libdir=<prefix>/lib64 when configuring.

== Maintainers ==

Maintainers for ax25-apps, ax25-tools and libax25 are

* [mailto:Ralf%20Baechle%20%3cralf@linux-mips.org%3e Ralf Baechle DL5RB <ralf@linux-mips.org>]
* [mailto:Thomas%20Osterried%20%3cax25@x-berg.in-berlin.de%3e Thomas Osterried DL9SAU <ax25@x-berg.in-berlin.de>]

Please feel free to contact us in case of problems, bugs or fixes, patches, enhancements, feature requests, or just for your personal success story.

[[de:CVS]]