9. - AX.25 Packet programs - Bringing up the other useful packet applications and daemons
As part of the ax25-apps package, there are several basic programs to make
connections. Let's talk about two of them in particular:
- ax25_call :: a simple connection tool similar to TELNET that
can connect to remote AX.25, NetROM, ROSE, etc.
hosts from the ax25-tools RPM
- this tools has aliases to be netrom_call, rose_call
and even tcp_call
- call :: a better AX25 conenction tool similar to TELNET for
TCP/IP. Supports a basic interface as well as a
'talk' style split screen. Comes from the ax25-apps
RPM. Works well though Linpac is even nicer
Say you're in Silicon Valley trying to connect to K6SNY-1. To do so, you you
would enter:
ax25_call sm0 K6SNY-1
- axcall is the program
- sm0 is the AX.25 device
- in my examples, sm0 would be for a Soundmodem-based device or
d710 for a Kenwood D710 based HW-TNC
- K6SNY-1 is the remote destination
Other examples:
- To connect to a directly reachable AX.25 machine, I would do:
call d710 woody
- To connect to a indirectly reachable AX.25 machine via a digipeater,
(not recommended for over 3 hops away), I would do:
call d710 berry via woody
- To connect to a indirectly reachable AX.25 machine via a node,
I would do:
call d710 woody
#wait for the connection to establish
#Using the Kantronics "c" command, connect to the remote host "berry"
c berry
- To connect to a remote machine via NetROM, I would do:
# This assume your have a) Netrom configured on your system
# (covered below) and b) the remote destination is loaded
# in the Netrom route table. Shown with "route -A netrom"
#
call netrom berry
A GOOD connection to K6SNY-1 according to axlisten would show:
#This is a connection request
fm KI6ZHD-8 to K6SNY-1 ctl SABM+
#This is a completed connection
fm K6SNY-1 to KI6ZHD-8 ctl UA-
#This is a transmit of the "?" character (the trailing . is a terminator)
fm KI6ZHD-8 to K6SNY-1 ctl I00^ pid=F0(Text) len 2 0000 ?.
#This is a connection keepalive
fm KI6ZHD-8 to K6SNY-1 ctl RR0+
#This is a disconnect request
fm KI6ZHD-8 to K6SNY-1 ctl DISC+
#This is a disconnect confirmation
fm K6SNY-1 to KI6ZHD-8 ctl DM-
A BAD connection according to axlisten would show:
[root@hampacket sbin]# axlisten
axconfig: port APRS not active
sm[29369]: snd_pcm_start in iotxstart: Broken pipesm0: fm KI6ZHD-8 to W6XSC-2
ctl DISC+
Broken pipes like this one for sm0 reflect OLD versions of soundmodem
and you need to upgrade it
As you've seen, you can make basic, outgoing connections but Linux AX.25 can do SO much
more using tools from the ax25-suite as well as 3rd party tools. For example:
#ax25d daemon - similar to inetd which will start services based on incoming requests
/usr/sbin/ax25d
#You should see:
#
# axconfig: port APRS not active
# nrconfig: unable to open nrports file /etc/ax25/nrports (No such file or directory)
# rsconfig: unable to open rsports file /etc/ax25/rsports (No such file or directory)
#Log and track users you system hears
/usr/bin/mheardd
#beacon - Announce your presence on a given frequency
beacon -d BEACON -t 10 sm0 "Welcome the new HAM to AX.25.. still working on it"
To monitor all of the received packets as well as ones you sent,
there are two KEY programs you should be aware of:
listen :: listens to ALL packets sent and received
This is already running in the packetrig.sh script
and you can just tail the log file
------------------------------------------------------------
/usr/bin/listen -8artp
Make sure it DOESN'T say "axconfig: port sm0 not active"
mheard :: shows last heard stations with optional things like
via what digipeater, etc. "man mheard"
Doesn't show the frequency but it's very similar
to the "last" command in Unix
------------------------------------------------------------
mheard
---------------
AX.25 Messaging
---------------
9a. - ax25mail-utils - AX.25 messaging tools for used with Linpac
One thing I've been missing on my system is a simple way for users to leave messages
and for me to reply to them. Below I describe what I've found and the integration
of axmail-utils with Linpac gets close but ultimately, Linpac wants to forward those
messages on to a remote FBB BBS. I don't want that.. I want it all local and
without using a Mail Transfer Agent (MTA) which won't let me reply to the user's
message without them having a Unix account on my box! Gahhh!!
Read on to see what I've found so far..
axmail-utils:
-------------
This suite is used by say Linpac to transfer messages to/from a FBB
BBS. Most of the versions on the internet are stale and cannot compile
due to it looking for the pre-2.4 head files such as netax25/kernel_ax25.h
and netax25/kernel_rose.h. Fortunately, Debian has an updated patch set
that gets things working ok:
cd /usr/src/redhat/SOURCES
#no, the debian sourced one is no different
wget http://sourceforge.net/settings/mirror_choices?projectname=ax25mail&filename=ax25mail-utils/0.11/ax25mail-utils-0.11.tar.gz
#get the debian patches
wget http://ftp.sv.debian.org/ubuntu/ubuntu/pool/universe/a/ax25mail-utils/ax25mail-utils_0.11-6.1.diff.gz
#Optionally, you can find them on my site as well:
# wget -r -l1 --no-parent -nd -A ax25mail* www.trinityos.com/HAM/CentosDigitalModes/usr/src/redhat/SOURCES/
gunzip ax25mail-utils_0.11-6.1.diff.gz
#Next, download my patch and ax25mail-apps.spec file from:
cd /usr/src/redhat/SOURCES
wget http://www.trinityos.com/HAM/CentosDigitalModes/usr/src/redhat/SOURCES/ax25mail-utils_0.11-ulistd.diff
cd /usr/src/redhat/SPECS
wget http://www.trinityos.com/HAM/CentosDigitalModes/usr/src/redhat/SPECS/ax25mail-utils.spec
#Ok, time to build it:
#for 64bit systems
rpmbuild -bb --target=x86_64 ax25mail-utils.spec
rpm -ivh /usr/src/redhat/RPMS/x86_64/ax25mail-utils-0.11-7.1.el6.x86_64.rpm
#for 32bit systems
rpmbuild -bb --target=i686 ax25mail-utils.spec
rpm -ivh /usr/src/redhat/RPMS/i686/ax25mail-utils-0.11-7.1.el6.i686.rpm
Once you install the RPM, you'll need to manually create the following
directory (I couldn't get the %dir macro to work properly in the .spec file):
mkdir /var/ax25/ulistd
---
If you are manually doing things without the .spec file
-------------------------------------------------------
cd /usr/src/redhat/BUILD
tar xzvf ../SOURCES/ax25mail-utils_0.11.orig.tar.gz
cd ax25mail-utils-0.11.orig/
vi ulistd/ulistd.c and delete the two lines:
#include >netax25/kernel_ax25.h< // new for libax25
#include >netax25/kernel_rose.h< // required by axlib.h
patch -p0 < ../SOURCES/ax25mail-utils_0.11-6.1.diff
./configure
make
make install
Incomplete - To do:
-------------------
Once installed, the ax25mail-utils prgram needs the following configuration
files to be configured to relay mail to/from Linpac:
/etc/ax25/axgetlist.conf
/etc/ax25/axgetmail.conf
/etc/ax25/bulletins.OK0PAB
/etc/ax25/logins
/etc/ax25/ulistd.conf
Out of the box, this program can forward/relay messages from FBB, JNOS, and
a few other BBSes and it seems extensible to support other BBSes as well.
NOTE: I have tried configuring these files but regardless of what
I do (I've tried all kinds of callsign permutations, etc), when
I run ulistd, I always get:
no BBS specified in configuration file /etc/ax25/ulistd.conf
If you know the solution to this error, I'd love to hear from you
on what I'm doing wrong!
---------------------------------------------------------------------------
PMS:
---
There is an old program called "pms" which was apart of the deprecated
ax25-utils package. This program only receives messages and it forwards
the resulting message to email via Sendmail (no simple / local PBBS mail)
and it also doesn't support sending messages to other hams using your PBBS
as their mailbox. This program also does not support reading any messages.
This program was abandoned a long time ago when the ax25-utils package was
broken into the ax25-apps and ax25-tools packages.
Axmail:
-------
I found this Axmail program (0.0.5) at http://benghi.wz.cz/vyvoj.html but
this program also uses Sendmail to send/receive emails and it also uses the
axspawn mechanism to dynically create Unix accounts to support new users
on demand.
Inbox
-----
A HAM has posted his Perl version of what is similar functionality to
what the PMS program does. Unfortunately for me, it still uses a local
MTA to deliver messages and doesn't provide any way for me to respond
to the user's message like one could on a classic TNC PBBS.
http://www.kingsqueak.org/2011/10/a-linux-packet-radio-personal-message-inbox/
Still researching this for a viable PBBS canidate on Linux as of 08/03/12
10. - Advanced AX.25 configuration, Netrom, Node services, and Troubleshooting
10a. - ax25spyd - Next generation packet monitoring daemon
Ax25spyd is very much like the "listen" program that comes with ax25-apps where it
acts like a sniffer on your AX.25 interfaces but it has two key differences:
- It's broken into two pieces:
ax25spyd - Runs as root and provides network socket connections to
other clients. This allows other programs that required
being run as ROOT to now run as individual users (more
secure)
- It also can detect transit packet messages and send them
to a SMTP host.
- Can capture all traffic on a per-callsign basis and
put it in /var/lib/ax25/ax25spyd/call1->call
ax25spy - A client to ax25spyd that can
- display the decoded AX.25 packets much like "listen" can
- Can display packets similar to a DX-cluster display
- Just show I, UI, IP, show unique QSOs,
Debian has a patched for the ax25spyd code that's more modern than
the official version ( http://linkt.de/ax25spyd/ ) and it works with modern
Linux kernels and libraries!
cd /usr/src/redhat/SOURCES
wget http://linkt.de/ax25spyd/ax25spyd-0.23.tar.gz
#Get the patch files from the Debian sources
wget http://ftp.de.debian.org/debian/pool/main/a/ax25spyd/ax25spyd_0.23-8.diff.gz
#Alternatively, you can find the patches from my site too
# wget -r -l1 --no-parent -nd -A ax25spy* www.trinityos.com/HAM/CentosDigitalModes/usr/src/redhat/SOURCES/
#Next, download my ax25spyd.spec file from:
cd /usr/src/redhat/SPECS
wget http://www.trinityos.com/HAM/CentosDigitalModes/usr/src/redhat/SPECS/ax25spyd.spec
#Ok, time to build it:
#for 64bit systems
rpmbuild -bb --target=x86_64 ax25spyd.spec
NOTE:
-----
I have seen a strange transient error where the build will FAIL with:
--
cd . && automake --gnu Makefile
configure.in:4: your implementation of AM_INIT_AUTOMAKE comes from an
configure.in:4: old Automake version. You should recreate aclocal.m4
configure.in:4: with aclocal and run automake again.
make: *** [Makefile.in] Error 63
error: Bad exit status from /var/tmp/rpm-tmp.sbVtCD (%build)
--
* If you try building the RPM several times back to back, it will eventually
* succeed. Dunno why and it's still happening as of 10/16/12! Maybe an
* issue with Automake??
# Now go ahead and install it
rpm -ivh /usr/src/redhat/RPMS/x86_64/ax25spyd-0.23-8.1.el6.x86_64.rpm
#for 32bit systems
rpmbuild -bb --target=i686 ax25spyd.spec
rpm -ivh /usr/src/redhat/RPMS/i686/ax25spyd-0.23-8.1.el6.i686.rpm
If you aren't going to build things via the SPEC file, follow this:
-------------------------------------------------------------------
cd /usr/usr/redhat/BUILD
tar xzvf ../SOURCES/ax25spyd_0.23.orig.tar.gz
gunzip ../SOURCES/ax25spyd_0.23-8.diff.gz
patch -p0 < ax25spyd_0.23-8.diff
./configure
make
NOTE: I've seen strange transient build error (shown above)):
--
To work around this, I ran "aclocal" which didn't give any output,
I then deleted the ax25spyd sources in /usr/src/redhat/BUILD,
re-untared the archive, and patched them and then re-did the
comfigure and make and things worked fine
Ok, now with things installed, just run src/ax25spyd as root for now:
NOTE: You can invoke "ax25spyd -s" which will create unique files in
/var/lib/ax25/ax25spyd\ for per-callsign detail
Please note that the KDE-based LinKT terminal program has a packet monitoring
program called MonKT that uses the ax25spyd daemon
10b. - AX.25 NetROM Routing and connections
Netrom - Netrom is a protocol that rides over AX.25 and has two main puposes
1. advertize known local neighbors with an associated link quality
in periodic "netrom" route updates
2. connect to remote stations found in the netrom route table without
requiring the user to know each of the hops to get to that
final destination
To configure Netrom on Linux, first you need to configure the /etc/ax25/nrports
file. In this example, the sole line configures SSID -5 which will announce
the "SCLARA" node alias which will resolve back to KI6ZHD-5.
The first configured item in that file is the netrom DEVICE which nothing can
connect (this is similar to the "ax0" interface that's configured but never
directly used. The next parameter is the callsign that is used when both
advertising netrom routes (both locally generated and optionally re-advertised
routes) and is the source callsign used when making Netrom connections. In this
example, I'm using an SSID of -5 for my outbound connections which is common for
Northern California Netrom nodes.
NOTE: The man pages speak of putting a # in front of the netRom alias of "SCLARA"
to mean it won't ever be announced by the NetRom system. I'm not sure if
the # trick is working as I still see SCLARA / KI6ZHD-5 getting announced
NOTE2: All of these "aliases" listed here must be UNIQUE to the netrom
table in your area. Please make sure you MONITOR your chosen
frequencies and netrom systems before choosing these names. Here in
Norcal, the general recommendation is to have a netrom alias that
calls out your general location.
NOTE3: blank lines in this file are NOT legal!!
--
# /etc/ax25/nrports
#
# The format of this file is:
#
# name callsign alias paclen description
#
netrom KI6ZHD-5 SCLARA 235 node
--
Finally, we need to edit the /etc/ax25/nrbroadcast file. This file controls
which AX.25 ports we will send NetROM broadcasts over and how it learns
routes.
NOTE: Please consider setting the VERBOSE setting to 0 unless your system
offers high level coverage!! If you have a low level machine like
most of us, the routes you'll be advertising are probably going to be
inferior to those other high level routes. You'll also be sending
these poorer routes all the time, polluting the airwaves!
For me, I use the following:
- d710 - matches up with the radio port definition in /etc/ax25/axports
- min_obs - minimum obsolescence count - when learning remote routes, a
heard route must have a OBS value HIGHER than this value to be
considered valid and entered into the local table and possibly
be re-advertized
- def_qual - this "default quality" is the initial value we first set to the
route
- worst_qual - minimum quality of a received route to be added to the local
netrom table
- verbose - A setting of verbose=0 will NOT advertise learned routes and
only advertise locally generated routes (ourself). A setting
of "0" is a GOOD default until you a) have a good handle on
NetROM routing and b) you're machine has good reachability to
other nodes and your system can handle the potential transit
traffic
--
# /etc/ax25/nrbroadcast
#
# The format of this file is:
#
# ax25_name min_obs def_qual worst_qual verbose
d710 5 190 100 0
--
Next, bring up the netrom interfaces by issuing:
/sbin/modprobe netrom
/usr/sbin/nrattach -i 44.4.10.40 netrom
--------------------
VERY IMPORTANT NOTE:
--------------------
After running each one of those nrattach lines (if you have multiple), you
should get a new "nr" device like nr0, nr1, nr2. If you don't a unique
device and instead each line reuses nr0, you're running a buggy version of
the ax25-tools package! The solution to this is to either add a patch
(disscused in the section where this document covered the installation of
the ax25-tools package OR (probably the more recommended way if you're
starting from scratch), use newer versions of the AX tools (be it the
CVS version "official AXTools" (last updated June 2011), the FPAC / F6BVP
version, or the VE7FET version posted on Github.
--
Finally, to get the netrom service running, issue the commands where:
-i : will send a netrom route update immeadiately
-l : turns on logging for both programs
-t 30 : send updates every 60 minutes
/usr/sbin/ax25d -l
/usr/sbin/netromd -i -l -t 60
# NOTE: These commands are fully integrated into the master packetrig.sh script
Make Netrom connections locally:
-------------------------------
As part of the ax25-apps package, the "call" program can make direct Netrom
connections. The man page eludes to this but what if fails to mention that
for the "port", you need to use the netrom device as defined in
/etc/ax25/nrports! As an example, if I make a regular AX.25 connection
with:
call d710 woody
I would make a netrom call by doing the following:
call netrom wbay
I bet you might be able to create Netrom connections via Linpac but
you need to be able to change the port from say "d710" to "netrom".
You might be able to do this on a per-F-key basis but I haven't looked.
Two other useful programs:
- nrparms :: manually create NetROM routes
- nodesave :: Store (and optionally reload) learned netrom routes
--
If you have a machine running a long time on a frequency
and it's stored up a long list of NetROM routes, you can
SAVE them from the /proc/net/nr_routes file with this
tool which creates a shell script that you can simply
run to restore these routes if you had to reboot, etc.
Do be careful about this and try not to use very old
saved tables as nodes come and go all the time!
For example, I use:
/usr/sbin/nodesave /var/ax25/nr-routes-145050.sh
Important note:
---------------
To help make all of this easy and reliable, ALL of these configurations are
already present in my TrinityOS packetrig.sh master shell script!
10c. - AX.25 Node Services - locally ACKed connections
A node program allows remote users to connect to your machine and then
initiate connections from your machine on to other machines. This is
superior to digipeating as each hop can do per-link retries vs. with
digipeating, the souce has to do retries all the way through the path.
This specific issue is very error-prone.
There are at least five Node programs out there for Linux that I know of:
- FPAC - Part node, part ROSE protocol, part packet switch. I haven't
used this program yet but I plan on it in the future!
http://www.f6fbb.org/fpac/fpac.html
- Actively maintained!
- Unode - Recommended : A renamed fork of the last available version of
the UroNode software available at:
https://github.com/kd1zd/Unode/tarball/master
- Not actively maintained
- UroNode - Abandoned : A heavily modified version of Anznode that has
additional features such as Flexd for FlexROM routing code beyond
all the features available in Linuxnode. Unfortunately, the
author seemingly dropped off the net (all web pages are broken,
etc.) as well as a copy of the software source code is
unavailable
- Anznode - A fork of the original Linuxnode that added several major
features but was abandoned. See below for supported commands.
- Linuxnode - (called Node) which is the original node version which works
but previously had KNOWN security issues. Unknown if those
security issues were resolved.
You can read about other nodes, what made them unique, their prompts, etc.
here:
http://www.proaxis.com/~wagnerj/ka7ehk/map/noderef.html
Unode
-----
The Unode software offers not only a NODE like interface for remote users
to hop packets off your system but also offers many other features. For
example, here is the main prompt given to a remote user:
--
?, Bye, Connect, Desti, Escape, Finger, Help, HOst, Info, INTerfaces
Links, MHeard, MSg, Nodes, Ping, Quit, Quit, Routes, SEssions, Status
Telnet, Users, Version, Who, WInlink
--
Unode is also extensible and you can add additional node commands by
calling other local commands. For example, I've also seen machines
setup to allow for the following:
--
?, Bye, CAllbook, CLuster, Connect, CONVers, Escape, Finger, Help, HOst
Info, Links, Mheard, NLinks, Nodes, PIng, Ports, Routes, Status, TAlk
Telnet, Users, ZConnect, ZTelnet
--
--
LinuxNode - Comes as part of ax25-tools (for historical comparison)
-------------------------------------------------------------------
Supported commands are:
?, Bye, Connect, Escape, Finger, Help, HOst, Info, Links, Mheard
NLinks, Nodes, PIng, Ports, Routes, Status, TAlk, Telnet, Users, ZConnect
ZTelnet
Anznode (for historical comparison)
----------------------------------
Supported commands are:
!, ?, Bye, Connect, Dest, Escape, Finger, Help, HOst, Info
Links, MHeard, MSessions, Nodes, PIng, Ports, Routes, Send, TAlk, Telnet
Users
Anyway, for this document, we're going to setup Unode. To get the software,
get it direct from Github but then it needs to be cleaned up a bit:
cd /usr/src/redhat/SOURCES
wget https://github.com/kd1zd/Unode/tarball/master
#Next, lets rename it and update it to reflect a new version
mv master kd1zd-Unode-f685a9a.tar.gz #This is v1.0.0-1
cd /usr/src/redhat/BUILD
tar xzvf ../SOURCES/kd1zd-Unode-f685a9a.tar.gz
mv kd1zd-Unode-f685a9a Unode-1.0.1
tar czvf ../SOURCES/Unode-1.0.1.tgz Unode-1.0.1/*
NOTE: The "configure" script in the Unode package is:
a) a Shell script and not the normal configure script
that you would expect. It's interactive and thus
can't be automated
b) If run, will call everything UroNode where as the
pre-configured Makefile will call everything
"Unode".
c) It seems this package includes a previously compiled
version of axdigi from the original FlexNode package
but I have no idea if this will run. I would recommend
to later DELETE this file and compile up your own
from this "Flexnode" package
NOTE#2: To fix many of those issues (and several others), I've posted
several patch files at the followowing URL and they are REQUIRED
if your going to use my spec file shown below:
cd /usr/src/redhat/SOURCES
wget http://www.trinityos.com/HAM/CentosDigitalModes/usr/src/redhat/SOURCES/Unode*
#Get the spec file from my directory
#
cd /usr/src/redhat/SPECS
wget -o unode.spec http://www.trinityos.com/HAM/CentosDigitalModes/usr/src/redhat/SPECS/Unode.spec
#Get all the patches too..
cd /usr/src/redhat/SOURCES
wget -r -l1 --no-parent -nd -A Unode* www.trinityos.com/HAM/CentosDigitalModes/usr/src/redhat/SOURCES/
#Ok, time to build it:
#for 64bit systems
rpmbuild -bb --target=x86_64 Unode.spec
rpm -Uvh /usr/src/redhat/RPMS/x86_64/Unode-1.0.0-1.x86_64.rpm
#for 32bit systems
rpmbuild -bb --target=x86_64 Unode.specc
rpm -ivh /usr/src/redhat/RPMS/i686/Unode-1.0.0-1.i686.rpm
Once installed, the RPM installs several files in /etc/ax25:
- Make sure the nrports and nrbroadcast files are configured as
mentioned in the previous section
Configuring Unode
-----------------
unode.conf - the main configuration file
- In this file, you need to change the following:
- IdleTimeout : leave this value at 900 (15min)
- ConnTimeout : leave this value at 600 (10min)
- HostName : to reflect your callsign - Ideally, you have already
requested an AMPR IP address through your local AMPR
coordinator. If you don't know how, email me and I'll
help you out with this very simple process
- ReConnect : This is optional but I personally like to set this to ON.
With this, when the user disconnects from a remote
station, they will drop back to your node
- LocalNet : If you have an AMPR address, put it in here with the
right subnet mask. if not, give it a unique IP that is
in the RFC1918 range with a /32 mask
- NodeId : replace OH2BNS-10 to your callsign. For me, I set it
to the following where the first paramater is an
ALIAS to this node (if you set one in
/etc/ax25/nrports and the next one is your
callsigni+SSID for the node. For me:
SCLARA:KI6ZHD-5
- Alias : I recommend you DISABLE any pre-defined Aliases with a #
until you a) know what commands you want b) have an
operational AMPR connection (for some of these examples)
and c) and understand the security
implications. Any aliases added here will show up in
the "node" interface when people are connected to it
- ExtCmd : I recommend to disable any pre-defined Aliases with a #
until you know what you want and understand the security
implications. Any aliases added here will show up in
the "node" interface when people are connected to it
- NrPort : Outgoing interface name used for NetROM connections.
The default is "netrom" but if not defined here,
it will either use the FIRST entry in /etc/ax25/nrports
or you can make it match somthing ELSE in the
/etc/ax25/nrports. I'm using my configured alisa of:
SCLARA
- LogLevel : once your comfortable with the setup, you should drop
the logging level to say 2
- NodePrompt : DEPRECATED - not sure if this is honored anymore
I recommend to # out the top \n example and re-enable the
bottom one for now with the full string but change the
callsign to reflect your own:
"\nSCLARA:KI6ZHD-5> "
If you have specific questions, do a "man node.conf" and "man node"
unode.motd - the message displayed when users connect to it
- There isn't much to change in this one
unode.perms - permissions
- When a user connects to Unode, it presents the user with a slew of options
as shown at the beginning of this section. I recommend to # out all lines
for any pre-defined users and CHANGE the default permission items to the
following.
# user type port passwd perms
* ax25 * * 7
* netrom * * 7
* rose * * 7
* local * * 7
* ampr * * 7
* inet * * 7
* host * * 7
You can have PER callsign permissions if you want but for now, my defaults
are the following as callsigns are easily spoofed. See unode.perms for
details but the following "perms" values is for:
- permits logging in even if no other permissions are given
- permits outgoing AX.25 / Flexnet connects
- permits outgoing NET/ROM connects
- permits outgoing ROSE connects.
- DOES NOT permit telneting to hosts in the "local" network as
defined in node.conf(5).
- permits telneting to hosts in amprnet (only enable
if you have a working AMPR.ORG connection running)
- DOES NOT permit telneting to hosts neither in the "local"
network nor in amprnet (aka, hosts on the Internet, etc)
- DOES NOT permit using hidden ports in outgoing AX.25 connections
- Escape mechanism for this user is still enabled
- No ANSI colors - who knows what the remote users are using.
Linpac can deal with it but can Outpost, ipserial, UISS, etc?
The defaults are the following (which I think are WAY too open)
---------------------------------------------------------------
# user type port passwd perms
* ax25 * * 31
* netrom * * 31
* local * * 31
* ampr * * 31
* inet * * 0
* host * * 31
node.info - details on your station
- Edit this file to give some info on your station
ax25d.conf
----------
The final file we need to configure is the /etc/ax25/ax25d.conf file. This file
is very similar to the /etc/inetd.conf file but for AX25/Netrom/Rose/Flex RF links.
When a given RF connection packet comes in with the correct destination callsign
and SSID, this file will match the CALL+SSID to the configured program and start
it up.
For my specific configuration, I want the node to be associated with KI6ZHD-5
to my "d710" AX.25 connection (see the packetrig.sh script for full details).
To support running the Linuxnode software, the second stanza is required:
ax25d.conf
--
#To allow connections to KI6ZHD-5 from a AX.25 connection
[KI6ZHD-5 VIA d710]
NOCALL * * * * * * L
default * * * * * * - root /usr/sbin/node node
#To allow connections to SCLARA from a AX.25 connection
[SCLARA VIA d710]
NOCALL * * * * * * L
default * * * * * * - root /usr/sbin/node node
#To allow connections to SCLARA from a Netrom connection
<netrom>
parameters 1 10 * * * * *
NOCALL * * * * * * L
default * * * * * * - root /usr/sbin/unode unode
--
That's it!
NOTE: If you had configured Linpac (previous section) to use the -5 SSID,
you should unconfigure that to avoid any conflicts in the
~/Linpac/macro/init.mac file
NOTE#2 When you eventually start up ax25d and it complains about the rsports
file for the Rose protocol, simply run "touch /etc/ax25/rsports" and
that will no
longer be a blocking error
------
09/09/11 - New issue with Unode
If I netrom OUT of my machine to WBAY, come back into it via SCLARA, and then
try to netrom BACK out to another machine, I get:
c WSTGAT
ERROR: connect_to: bind: Cannot assign requested address
------
------
Previous Issue with Unode (resolved in an above patch and the packetrig.sh script:
------
- If you try to run /usr/sbin/unode locally on the machine and you get:
$ /usr/sbin/unode
Segmentation fault (core dumped)
This means two things. One, you didn't apply the Unode-local-execution-coredump-fix.diff
patch from Steven, K6SPI. Alternatively, you can work around this issue
with putting the following command in your packet startup script. For
this setup, I put the following in the packetrig.sh script for my callsign
to username coorilation:
axparms -assoc KI6ZHD dranch
- The symptoms:
I have determined thast if you run Unode from localhost, the program
will coredump but it works *fine* via external RF links. I'm researching
this but it's not a fatal issue as ax25d will dynamically spawn new
connections as needed.
Here is my ongoing troubleshooting for this issue and this will be
removed once I resolve the issue:
--
1. I had to modify the spec files for unode and libax25 to add the
following line to be line #1:
%define debug_packages %{nil}
and then recompile those RPMs and install them. Additionally,
install the following debug RPMS:
yum --nogpgcheck --enablerepo=debug install glibc-debuginfo
yum --nogpgcheck --enablerepo=debug install zlib-debuginfo
[root@hampacket2 ~]# unode
Segmentation fault (core dumped)
[root@hampacket2 ~]# gdb unode core.10482
GNU gdb (GDB) Red Hat Enterprise Linux (7.2-50.el6)
Copyright (C) 2010 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law. Type "show copying"
and "show warranty" for details.
This GDB was configured as "x86_64-redhat-linux-gnu".
For bug reporting instructions, please see:
10d. - AX.25 Tunneling over the Internet via AXIP or AXUDP
This is a placeholder to get me started but it has NOT been integrated
into the packetrig.sh script as of yet.
NOTE: Depending on your selection of the ax25-apps that you installed,
you might need to apply a patch or you will get fatal tunneling
errors. This is dicussed above in the AX.25 installation section
1. Update /etc/ax25/axports and define the ipct port
This is currently another filename as /etc/ax25/axports-udp
2. /usr/sbin/kissnetd -p2 &
- Please record the FIRST port and SECOND port out of that list
for follow-on commands
3. /usr/sbin/kissattach -l /dev/pts/7 ipct 44.4.10.40
- In this example, /dev/pts/7 camesfrom the output of the kissnetd
command above. 44.4.10.40 is my AMPR IP address and you need
to put in your OWN IP address that you can get free from your
local AMPR IP coordinator.
NOTE: Your kernel MUST have legacy /dev/pty support for this
work
4. From the output of command in step 2, take the SECOND port given (not the
first port) and put that into /etc/ax25/ax25ipd.conf for the "device" line
NOTE: socket ip - means proto 93
socked udp - mean UDP defaulting on port 10093
5. run /usr/sbin/ax25ipd
6. Per db0fhn security, you MUST log into Echolink via the same egress IP
address (easily done via NAT) as this AXUDP connection.
7. Connect to the remote station:
call ipct db0fhn
Scripting the PTY values:
1. See the JNOS section of the packetrig.sh script
2. http://wiki.complete.org/LinuxPacketRadio#ax25ipd-1
3. Other HAMs have used the "socat" program to script this PTY setup
10e. - AX.25 Packet traffic monitoring
Like any amateur radio transmission, all signals are broadcasted for all to hear
and it's sometimes useful to monitor the packet traffic on a given frequency.
In my packetrig.sh script discussed elsewhere in this document, it starts a
promiscuous "listen" process in the background that decodes all heard packets
and logs them to a file named /var/log/listen->date<.log. At any time,
you can view, tail, etc. this file to see what's been going on.
Pretty useful!
The issue with monitoring this traffic is is that there is a LOT of redundant
traffic on a channel with beacons, NETROM route updates, etc. With all that
"noise", viewing logs can get very tedious. My solution is the
filter-packet-listen-logs.sh that can be found at:
http://www.trinityos.com/HAM/CentosDigitalModes/usr/local/bin/filter-packet-listen-logs.sh
This script needs to be modified by the reader to match your specific local
stations but it does greatly reduces the amount of repetive text that you
probably don't want. It's structured to filter out individual beacons in one
section and netrom updates in another section but also supports command line
options to reverse this behavior as well.
FUTURE: The "listen" process has the ability to color the text to make things
far more readible but saving this color information into a log file
makes parsing the data very difficult. As such, the packetrig.sh
script disables this coloring.
I hope to update the filter-packet-listen-logs.sh script to include
the use of supercat to re-color the output to make the resulting
filtered text more readible.
http://supercat.nosredna.net/
10f. - AX.25 Packet troubleshooting
+---------------------------+
| To be updated for Centos6 |
+---------------------------+
CHOKE messages:
When a remote station tries to connect to your machine yet they "busy" messages
and the AX.25 packet decodes saying things like "CHOKE", this means your
/etc/ax25/ax25d.conf file doesn't know what to do with this request
for the specific PROTOCOL. To be clear, AX.25 connections use
the square brackets [], Netrom uses >< signs, and ROSE uses
{}. This problem was messing with me for the LONGEST time!
Connect/Disconnect:
When a remote station tries to connect to your machine yet the session
connects and then immeadiately disconnects, this most likely means
that the binary program (node, unode, etc.) as specified in the
/etc/ax25/ax25d.conf file is improperly configured or isn't there.
To confirm the network is listening, try the following commands:
/sbin/ifconfig :: Shows all interfaces (I've removed my internal
ethernet ones
----------------------------------------------------------------
ax0 Link encap:AMPR AX.25 HWaddr KI6ZHD
inet addr:44.4.10.40 Bcast:44.255.255.255 Mask:255.0.0.0
UP BROADCAST RUNNING MTU:128 Metric:1
RX packets:16 errors:0 dropped:0 overruns:0 frame:0
TX packets:5 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:10
RX bytes:1273 (1.2 KiB) TX bytes:246 (246.0 b)
nr0 Link encap:AMPR NET/ROM HWaddr KI6ZHD-14
inet addr:44.4.10.40 Mask:255.0.0.0
UP RUNNING NOARP MTU:235 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)
nr1 Link encap:AMPR NET/ROM HWaddr KI6ZHD-1
inet addr:44.4.10.40 Mask:255.0.0.0
UP RUNNING NOARP MTU:235 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)
nr2 Link encap:AMPR NET/ROM HWaddr KI6ZHD-5
inet addr:44.4.10.40 Mask:255.0.0.0
UP RUNNING NOARP MTU:235 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)
To confirm that everything in /etc/ax25/axports is bound, the best I've been
able to find is:
ps aux | grep kissattach
NOTE: If anyone is aware of a way to find this via /proc or /sys, I'd
love to hear from you
Show all active AX.25 interfaces if everything is running including
Linpac:
netstat -A ax25 -an
---------------------------------------------------------------
Active AX.25 sockets
Dest Source Device State Vr/Vs Send-Q Recv-Q
* KI6ZHD-4 ax0 LISTENING 000/000 0 0
* KI6ZHD-3 ax0 LISTENING 000/000 0 0
* KI6ZHD-2 ax0 LISTENING 000/000 0 0
* KI6ZHD-1 ax0 LISTENING 000/000 0 0
* KI6ZHD-0 ax0 LISTENING 000/000 0 0
* ZHDNOD-0 ax0 LISTENING 000/000 0 0
* KI6ZHD-5 ax0 LISTENING 000/000 0 0
Show all active NetROM connections (if any):
netstat -A netrom -an :: Shows all active NetROM connections
------------------------------------------------------------
Active NET/ROM sockets
User Dest Source Device State Vr/Vs Send-Q Recv-Q
How to see the heard netrom table:
netstat -A netrom -rn
---------------------
Kernel NET/ROM routing table
Destination Mnemonic Quality Neighbour Iface
or
route -A netrom
-------------------
Kernel NET/ROM routing table
Destination Mnemonic Quality Neighbour Iface
WA7DG-4 ROSE 108 N6ZX-5 ax0
WA6YNG-1 RDG 108 N6ZX-5 ax0
KI6NCU-5 PONDER 107 N6ZX-5 ax0
KG6WOO-5 PLUMAS 134 N6ZX-5 ax0
WA6TOW-1 PAC 107 N6ZX-5 ax0
WW8L-3 OVALE 90 N6ZX-5 ax0
WB6YNM-11 MOC 143 N6ZX-5 ax0
KF6FPU-5 LIVER 143 N6ZX-5 ax0
KI6UDZ-7 FCITY 143 N6ZX-5 ax0
W6PJD-3 ELDOR 107 N6ZX-5 ax0
W6JEX-5 CORN 108 N6ZX-5 ax0
WG6D-6 CAM91 108 N6ZX-5 ax0
WG6D-8 CAM05 108 N6ZX-5 ax0
K7WWA-8 CAHTO 107 N6ZX-5 ax0
K6IXA-5 BULN 143 N6ZX-5 ax0
N6KRV-5 BRKNRG 107 N6ZX-5 ax0
K6JAC-4 BERRY 144 N6ZX-5 ax0
KF6DQU-9 BANNER 119 N6ZX-5 ax0
N6ZX-5 WBAY 190 N6ZX-5 ax0
Creating new netrom routes:
---------------------------
nrparms -routes
Creating remote IP routes via netrom:
------------------------------------
route add 44.2.14.100 nr0
To view the remotely learned NetROM routes, do:
-----------------------------------------------
cat /proc/net/nr :: Show all established netrom connections
-----------------------------------------------------------
user_addr dest_node src_node dev my your st vs vr va t1 t2 t4 idle n2 wnd Snd-Q Rcv-Q inode
show locally heard NetROM neighbors
cat /proc/net/nr_neigh
-----------------------------------------------------------
addr callsign dev qual lock count failed digipeaters
00003 WA6TOW-1 ax0 250 0 1 0
00002 N6ZX-5 ax0 250 0 26 0
00001 K6JAC-4 ax0 250 0 40 0
Shows all **learned**** NetROM routes from distant nodes:
netstat -A netrom an
or
cat /proc/net/nr_nodes
Quality >192 is exceptionally good. Good quality is 192. Poor quality is <120.
Zero quality means that the node can be heard but cannot be connected to reliably.
The obs number of additional nodes that can be connected from that destination node.
-------------------------------------------------------------------
callsign mnemonic w n qual obs neigh qual obs neigh qual obs neigh
WA7DG-4 ROSE 1 1 143 6 00002
WA6YNG-1 RDG 1 1 143 6 00002
KG6WOO-5 PLUMAS 1 1 176 6 00002
WD6EZC-5 PINOLE 1 1 188 6 00002
WA6TOW-1 PAC 1 2 250 6 00003 141 6 00002
K7URY-1 BLKMND 1 1 140 6 00001
K6LRC-2 ALM 1 1 132 6 00001
W6HMT-7 AUKUM 1 2 176 6 00002 176 6 00001
W7TA-4 RNO 1 1 141 6 00001
WX7RNO-2 NWSCHT 1 1 140 6 00001
W7DED-4 YRGTN 1 2 156 6 00001 118 6 00002
KE7CRZ-7 FERNLY 1 1 141 6 00001
N6ZX-5 WBAY 1 2 250 6 00002 188 6 00001
K6TUO-5 TUO 1 2 188 6 00002 188 6 00001
WX7RNO-3 NWSBBS 1 1 140 6 00001
KF6DQU-4 ROUGH 1 2 188 6 00002 188 6 00001
N6KRV-5 BRKNRG 1 2 142 6 00001 141 6 00002
WX7RNO-4 NWSRNO 1 1 141 6 00001
WB6YNM-11 MOC 1 2 188 6 00002 188 6 00001
KF6FPU-5 LIVER 1 2 188 6 00002 156 6 00001
K6LRC-1 LASSEN 1 1 141 6 00001
KJ6IX-10 IXRMS 1 1 140 6 00001
KJ6IX-2 IXCHT 1 1 140 6 00001
KJ6IX-3 IXBBS 1 1 140 6 00001
KJ6IX-4 KMEV 1 1 141 6 00001
KG6BAJ-2 GVCITY 1 2 188 6 00001 186 6 00002
N6SGR-1 FST 1 2 188 6 00001 143 6 00002
KE7CRZ-10 CRZRMS 1 1 140 6 00001
W6TUK-4 TUCK 1 2 143 6 00002 142 6 00001
W6PJD-3 ELDOR 1 2 142 6 00001 141 6 00002
W7DEM-10 DEMRMS 1 1 140 6 00001
W7DEM-2 DEMCHT 1 1 140 6 00001
W7DEM-3 DEMBBS 1 1 140 6 00001
W7DEM-4 CSN 1 1 141 6 00001
KE7CRZ-2 CRZCHA 1 1 140 6 00001
KE7CRZ-1 CRZBBS 1 1 140 6 00001
W6JEX-5 CORN 1 2 188 6 00001 143 6 00002
WG6D-6 CAM91 1 2 187 6 00001 142 6 00002
WG6D-8 CAM05 1 2 188 6 00001 143 6 00002
K7WWA-8 CAHTO 1 2 186 6 00001 141 6 00002
K6IXA-5 BULN 1 2 188 6 00002 188 6 00001
KF6DQU-9 BANNER 1 2 188 6 00001 156 6 00002
W6SV-6 WKRBSN 1 2 142 6 00001 141 6 00002
KI6UDZ-7 FCITY 1 2 188 6 00002 141 6 00001
K6JAC-4 BERRY 1 2 250 6 00001 189 6 00002
11. - Linpac - Advanced HF/VHF/UHF AX.25 packet terminal and PBBS
Linpac is a great packet termial program using TNCs in KISS mode. It seems to
emulate and surpass older premium programs like the KaGold program:
http://www.interflex.com/private/review1.htm
Though you can use the basic AX25 "call" program to connect to remote packet
nodes, etc...
- It gives you a keyboard to keyboard interface for MULTIPLE people
connecting to YOU
- allows for 8 simultaenous connections IN or OUT
- notifies you when people connect to you
- three views to show received, sent, and promiscuous decodes
- Supports a very easy to use UNPROTO mode
The main window where you can switch between SSIDs using the F-keys, see live decodes, etc:
Able to READ but not reply to messages (this will be fixed..):
+---------------------------------------------------------------------+
| There are TWO versions of Linpac available today: |
| |
| 0.17pre3 - an Ncurses based UI - old but simple and effective |
| |
| 1.0pre4 - a split client/server system with a Java-based client UI |
| Not covered in this document as of yet |
+---------------------------------------------------------------------+
The following instructions are for the Ncurses based Linpac 0.17pre3 for now
I've noticed that Linpac 0.16 stable will NOT compile cleanly
on Centos5 but version 0.17pre3 will. Because of this, you'll need
the newest version but let's steal the stable version's SPEC file:
Download the newest version of code:
cd /usr/src/redhat/SOURCES
wget -O LinPac-0.17pre3.tar.gz \
http://downloads.sourceforge.net/project/linpac/LinPac-unstable/0.17pre3/LinPac-0.17pre3.tar.gz
+-----------------------------------------------------------------------------+
| NOTE: Supporting local messaging |
| |
| Linpac can integrate with the axmail that can be found in the |
| axmail-utils package. Unfortunately, this program does NOT emulate |
| a classic PBBS like simple messaging system. This package is |
| designed to forward (proxy) messages to/from a FBB BBS and nothing |
| is local. |
| |
| See the "AX.25 Packet Programs" section for more mailing tool options |
+-----------------------------------------------------------------------------+
Next, download the SRPM at:
cd /usr/src/redhat/SRPMS
wget -O linpac-0.16-1.src.rpm \
http://downloads.sourceforge.net/project/linpac/LinPac/0.16/linpac-0.16-1.src.rpm
Now you need to get the various patches:
cd /usr/src/redhat/SOURCES
wget -r -l1 --no-parent -nd -A linpac* www.trinityos.com/HAM/CentosDigitalModes/usr/src/redhat/SOURCES/
Now go ahead and install the SRPM
rpm -ivh /usr/src/redhat/SRPMS/linpac-0.16-1.src.rpm
I now recommend to rename and edit the SPEC file
mv /usr/src/redhat/SPECS/linpac-0.16.spec /usr/src/redhat/SPECS/linpac.spec
These instructions assume Centos6
cd /usr/src/redhat/SPECS
vim linpac.spec
Find the following lines:
%define name linpac
%define version 0.16
Source: %{name}-%{version}.tar.bz2
tar xvjf $RPM_SOURCE_DIR/%{name}-%{version}.tar.bz2
and change and/or add the following lines:
%define name LinPac
%define version 0.17pre4
%define debug_package %{nil}
Source: %{name}-%{version}.tar.gz
#For Centos6 users, add:
Requires: compat-gcc-34-c++-3.4.6
#Under the %install section, add the following as the first line
#and change the configure line
export RPM_BUILD_ROOT="/usr/src/redhat/BUILD/%{name}-%{version}"
./configure --includedir=/usr/include/c++/3.4.6
(notice the version change.. and yes, pre4 is correct.. see below)
(notice the capital L and the P)
(notice that last line changes a "j" to a "z" too)
+-----------------------------------------------------------------+
| Work in progress.. I plan on updating the above SPEC file to do |
| this all for you but it hasn't been done quite yet. Until |
| then, read below how to patch the code manually. |
+-----------------------------------------------------------------+
Ok, now we have the SPEC file in place but we need to update the
code a bit:
cd /usr/src/redhat/BUILD
tar xzvf ../SOURCES/LinPac-0.17pre3.tar.gz
cd LinPac-0.17pre4
# Change #1
#
# The stock Linpac 0.17pre3 version has a limitation that it cannot use
# more than one digipeater for UNPROTO communications. Don't fret, make
# the following changes to the src/commands.cc file to allow 7 digipeaters
This is the 'diff -u' of the changes. To make the changes manually, just
file around line 644 and make the changes show with the "+". You can also
find this patch at:
http://www.trinityos.com/HAM/CentosDigitalModes/usr/src/patches/linpac-digi-length.patch
--
+++ commands.cc 2010-08-22 15:50:51.000000000 -0700
@@ -644,8 +644,9 @@
if (com_ok(chn, echn, cmd, "UNDest")) {
if (is_next())
{
+ strcpy(result, "ki6zhd digi patch enabled");
nextp(gps);
- normalize_call(gps);
+ //---- normalize_call(gps);
emit(chn, EV_UNPROTO_DEST, 0, gps);
}
else strcopy(result, sconfig(0, "cwit"), 256);
--
Next, Centos6's C++ compiler is far stricter that Centos5's compiler. So
we have to make some updates to the code to fix various minor issues:
vim src/applications/mailer/mail_call.cc
line 80: const char *p = strchr(addr, '@');
vim src/applications/mailer/mail_route.cc
#include <string.h>
vim src/applications/forward.cc
line 131: const char *p;
vim src/keyboard.cc
#include <string.h>
# Change #2
#
# The stock Linpac 0.17pre3 version has a limitation that it will always
# a OSS soundcard and can't be unconfigured. This patch makes it ALWAYS
# us the PC speaker
This is the 'diff -u' of the changes. To make the changes manually, just
file around line 644 and make the changes show with the "+". You can also
find this patch at this URL with 'patch -p0 < linpac-digi-length.patch':
http://www.trinityos.com/HAM/CentosDigitalModes/usr/src/patches/linpac-digi-length.patch
--- src/applications/bell.cc.orig 2011-11-27 19:25:04.000000000 -0800
+++ src/applications/bell.cc 2011-11-29 20:12:28.000000000 -0800
@@ -55,9 +55,10 @@
active = lp_start_appl();
lp_event_handling_off();
- if (active) lp_appl_result("Ringing...");
+ if (active) lp_appl_result("Ringing (PC speaker only)...");
- dsp = open("/dev/dsp", O_RDWR);
+ /*ki6zhd / dranch: disabled soundcard and using PC speaker only*/
+ /* dsp = open("/dev/dsp", O_RDWR);
if (dsp != -1) //soundcard present
{
i = AFMT_U8;
@@ -70,6 +71,7 @@
else //soundcard not present - use speaker
{
int i;
+ */
console = open("/dev/console", O_RDWR);
if (console == -1) printf("\a"); //nothing usable, try BEL char.
for (i=0; i < 10; i++)
@@ -78,7 +80,7 @@
sound(800); wait(20000);
}
nosound();
- }
+ /* } //disabling of the soundcard */
if (active) lp_end_appl();
return 0;
}
+----------------------------------------------------------------------+
| NOTE: |
| Centos6 comes with newer C++ libraries that poses problems for |
| old programs like Linpac (missing vector.cpp files, etc). |
| |
| Install the compat-gcc-34-c++-library with: |
| yum install compat-gcc-34-c++-3.4.6-19.el6.x86_64 |
| |
+----------------------------------------------------------------------+
+----------------------------------------------------------------------+
| NOTE #2: Issue with the ./configure script |
| |
| In the user's Linpac directory, the bin/ directory creates |
| possibly wrong symlinks to /usr/local/share/linpac/bin |
| You can fix this with the following command: |
| |
| ln -s /usr/local/share/linpac /usr/share/linpac |
+----------------------------------------------------------------------+
+----------------------------------------------------------------------+
| NOTE #3: Issue with the ./configure script |
| |
| It seems linpac is hardcoded to "listen" and not say |
| finding Debian/Ubuntu's broken naming of axlisten. You can |
| fix this in src/constants.h or create a symlink |
| pointing the listen binary to axlisten |
| |
+----------------------------------------------------------------------+
With all the changes, made, lets tar up the new archive:
mv LinPac-0.17pre3 LinPac-0.17pre4
tar czvf ../SOURCES/LinPac-0.17pre4.tar.gz LinPac-0.17pre4
Ok, now compile up the RPM
#for 64bit systems
rpmbuild -bb --target=x86_64 linpac.spec
#for 32bit systems
rpmbuild -bb --target=i686 linpac.spec
And now install it!
#for 64bit systems
rpm -ivh /usr/src/redhat/RPMS/x86_64/LinPac-0.17pre4-1.x86_64.rpm
A few more points:
#To properly suport local email, do the following as root (should be done
# via the RPM script:
mkdir /var/ax25/mail
chmod 777 /var/ax25/mail
#Future sections to expand on
#To support full FBB mail forwarding, install ax25mail-utils first
11a. - Linpac - Configuring the packet terminal program
Before running Linpac for the first time, there are a few things to consider:
Fixups before running
---------------------
- Fixme: Before starting Linpac as a normal user (not root), you need
to allow for users to create Lock files. To do this, run as root:
touch /var/lock/LinPac.500
chmod 666 /var/lock/LinPac.500
Site-Wide Configuration changes
-------------------------------
Menu Prompts
------------
- I recommend you edit the /usr/local/share/linpac/macro/info.mac
file as root and populate it with all the interesting info about
your specific packet setup.
- Linpac has the ability to do simple messaging but the default help
file doesn't clearly mention this! To make sure users can know about
this, edit the /usr/local/share/linpac/macro/help.mac as root and insert
the lines:
//SP [] - write a Private message to user [optional subject]
//SB [] - write a Bulletin message to everyone [optional subject]
Choosing what user to run Linpac as / Traffic Monitoring
--------------------------------------------------------
- Linpac has the ability to show all real-time traffic on a given
packet frequency in a section of the window. To show this real time
traffic, you either need to:
- Run the ax25spyd daemon as root as described in a previous
section. If ax25spyd is running when Linpac is started, all Linpac
configuration files are put into that user's home directory and this
non-root users can see the traffic data.
+---------------------------------------------------------------+
| NOTE: For general Linux security reasons, it's recommended to |
| use the ax25spyd method and NOT run Linpac as root |
+---------------------------------------------------------------+
- Alternatively, you can run Linpac as the "root" user which will
put all Linpac configuration files in the /root directory and
then spawn a "listen" process can monitor the traffic.
This process can then talk to the SOCK_PACKET socket to get the
traffic.
NOTE: If you don't have ax25spyd running as the root user OR you
start linpac NOT as root, you won't see real-time packet
traffic. Instead, you'll see the error:
socket: Operation not permitted
Starting up Linpac for the first time
-------------------------------------
- As above, you need to choose if you're going to run Linpac as a regular
user as root. Once decided, become that user and prepare to run Linpac
for the first time.
- When you first run Linpac on the local machine, it creates a directory in
the process owner (root or regular user's) home directory called
"LinPac". In this directory, Linpac copies over all kinds of default
files, etc. into their $HOME/Linpac directory.
- Now that the various skeleton files have all be copied over, issue
the command :sys to exit Linpac and return to the system. Now you
will need to edit the config files
Mail Forwarding
---------------
- Linpac has a mail forwarding system built into it where it can do bulk
uploads and downloads of messages from a different BBS. Once fetched,
you can read and reply to messages all offline while not connected to
any station. Once done, you and tell Linpac to send the messages and
get any new ones.
Please note this is NOT like a simple PBBS as found on TNC2/KPC3/etc
TNCs.
If you want to use this feature, you need to have followed the previous
section's instructions to get ax25mail and ulistd installed. Once
installed, need to do the following to get Linpac forwarding working.
NOTE: It's good to know about the purpose of the following dirs:
$HOME/LinPac/mail : where local messages are stored
/var/ax25/ulistd : where ?message lists? are stored
/var/ax25/mail : where message bulletins are stored
1. Choose a remote BBS that's on the same frequency as your packet
station. Today, it seems Linpac supports FBB and TNOS as valid
remote BBS types but there might be more. I hope to add simple
KPC3 PBBS forwarding support in the future.
2. Configure this station in the homeuser's Linpac/station.data file.
For example, I'm using the K6FB-1 BBS:
[K6FB-1]
NAME=K6FB PBBS
TYPE=FBB
- Linpac is configured by the $HOME/LinPac/macro/init.mac file. In this file,
you need to make several changes to fit your specific environment. You
need to put in your proper:
- AX.25 port name
- callsigns and SSID to F-key mapping
- unproto callsign and optional path
- optional BBS forwarding call and ssid
+--------------------------------------------------------------+
| NOTE: The Hampacket "packetrig.sh" script automatically |
| switches Linpac configs based upon how it's started |
| to select the right ax.25 device, etc. |
+--------------------------------------------------------------+
Master Configuration
--------------------
$HOME/LinPac/macro/init.mac
--
;;the default AX25 device name. For my packetrig.sh script with
;; VHF/UHF, it's named "d710"
port d710
;;Set the default terminal type to ANSI
term ansi
;;I prefer the following look
;; type-in window at type, what you send second, and a large
;; monitoring window at the bottom
statline 5
chnline 30
infoline 5
swapedit
redraw
;;With LinPac, each F-key in a Linux terminal can be a different
;; connection and each on can have their unique SSID if you'd like
;; To have unique SSIDs for say F1 through F8, try the following.
;; Note: F9 is a reserved screen where ALL traffic is UNPROTO:
mycall@1 KI6ZHD
mycall@2 KI6ZHD
mycall@3 KI6ZHD-1
mycall@4 KI6ZHD-1
;DO NOT use the **#***-5 SSID as that's used for the Netrom NODE
; SSID as described in the NetRom section
;;For unproto traffic, address it to the proper source and
;;destination -- Be sure to change this to your callsign
unsrc KI6ZHD
;;For basic one-hop UNPROTO communications, don't use any digipeated paths
;; undest INFO
;;For multi-hop UNPROTO communications, you need to use digipeated paths.
;;Assuming you enabled the digipeat patch from above AND you live in the
;; South BayArea, California, I use the following path:
;;
undest "David WOODY KBERR KTUO KMOC KBETH KLIVE KPAC"
;; Other settings - Allow the system to make a bell sound when remote users connect
cbell on
knax on
;; Required to be on or linpac won't accept any // commands from the remote user
remote on
infolevel 1
;; Default QRG - whatever is your primary packet frequency
set QRG@0 "145.050 MHz"
;; Default set of enabled remote commands
set DEF_RCMD@0 "AB D E VER L RP B MH N RT YPUT W R WB RB A CONV I H Q U CS SP SB"
;;Optional mail forwarding
;; Path to home BBS - the port name is REQUIRED
;;The syntax is:
;; The ax25 port name as shown above, the @0 reserved port number, the
;; BBS name and it's proper SSID, and additional digi callsigns required
;; to get to said BBS
set HOME_BBS@0 "d710:K6FB-2"
;; HOME_ADDR must be assigned or you won't be prompted for a subject
;; This example reflects using K6FB found in Northern California, CA, USA
set HOME_ADDR "K6FB.#NCA.CA.USA.NOAM"
--
Final Tweaks
------------
- By default, Linpac supports commands in upper or lower case but ONLY if
they are defined in the macro/commands file. If not defined but the
*.mac file exists in the macro/ directory, they will run but ONLY if the
command's "case" matches. Putting it another way, "sp.mac" would work
for "//sp" but wouldn't work for "//SP". Dear god this one pissed me
off for a while once. For a base system that you want to accept messages
on, I recommend to edit the following file and add these two lines to
accept "Send Private" and "Send Bulletin" in upper or lower case:
macro/commands
--
sb SB
sp SP
--
You can find another short Linpac setup doc here (very rare to find Linpac docs).
http://www.zs6mrk.org/pakket_met_linux.htm
If you know of any or if you're a Linpac user, please send me an email to tell me
as such!
12. - Fldigi - Fldigi - Compiling the program for HF digital modes
FLdigi is an HF Digital mode program that supports most of the digital
modes including BPSK31, RTTY, Olivia, CW, etc. It runs on Linux, Windows,
and Apple OSX.
Please understand that this is a BIG section and requires lots of dependencies
to get everything in place. Be patient, follow these steps and it will work!
This is the main window for making QSOs, seeing decodes of other signals, running macros, etc:
NOTE on Logging:
----------------
Though Fldigi supports exporting it's logs to say EQSL directly,
it doesn't directly support LOTW yet. Alternatively, you can use
external logging programs such as Xlog to automatically upload your
logs to LOTW, EQSL, etc.
If you want to use Xlog, you must be running Fldigi 3.20.21 or newer
Notes about Fldigi on centos5
-----------------------------
Performance
-----------
I have seen where fldigi running on slower machines (1.7Ghz Pentium-M)
can have the annoying problem where if Firefox or Chrome is open and
is specifically running a webpage loaded with JavaScript. A big offender
ironically seems to be QRZ.com:
a. Fldigi can get stuck when you try to transmit. The program becomes
very slow and it eventually asserts PTT but it won't start transmitting
any digital tones, etc. You can hit the ESC to abort the TX but it can
take 5-10 seconds to release PTT. The ONLY solution to solve this after
it starts happening is to first shutdown FF/Chrome and then completely
restart Fldigi. Fldigi 3.20.x does NOT fix this.
Contesting
----------
If you ever want to try contesting with Fldigi, make sure you have
Configure --> Contest --> Duplicate Check : ON
with at least the MODE box checked.
New Fldig compile time features
-------------------------------
New behind-the-scenes compile-time features are added into fldigi all
the time so I recommend you manually run it's configure script
via "./configure" and not just install the newest binaries to see what
new options have been added. If you want something that might be
disabled by default, you'll need to modify the SPEC file or manually
compile it to reflect the change.
Ok, let's get down to it!
+-----------------------------------------------------------------------+
| NOTE: |
| The following example assumes Fldigi 3.21.36 and Centos6 but Centos5 |
| is specifically called out as well |
+-----------------------------------------------------------------------+
Download the sources
--------------------
# NOTE:
# As of 3.21.35, Fldigi now supports more modern Fltk tool kits. I do
# NOT recommend you install older versions of the Fltk toolkits
cd /usr/src/redhat/SOURCES
#Getting the version 3.21.25 - change the version number to match the newest
# release version available
wget -O fldigi-3.21.35.tar.gz http://www.w1hkj.com/downloads/fldigi-3.21.35.tar.gz
It's recommended to download and use my TrinityOS SPEC file (which
enables the kitchen sink for Fldigi):
cd /usr/src/redhat/SPECS
wget -O fldigi.spec \
http://www.trinityos.com/HAM/CentosDigitalModes/usr/src/redhat/SPECS/fldigi.spec
+------------------------------------------------------------------------+
| If you choose use my SPEC file (recommended), you will *STILL NEED* to |
| follow all the below dependency steps to ensure your machine has the |
| additional required packages to both compile and install Fldigi. |
+------------------------------------------------------------------------+
Alternatively, you can follow the below steps to manually build your own
without doing the final compile/install via RPMs. You'll still need to fill
in the various requirements at "configure" time and compile, install, and
configure Fldigi itself at the end of this section.
------------------------------------------------
Building up your own SPEC file (not recommended)
------------------------------------------------
** This section is only useful to understand how I started to build my Fldigi
** SPEC file. There is little value in this section otherwise than maybe
** comparing what I'm doing to your build creation file (SPEC, deb, etc)
- The last fedora package I saw was using Fldigi 3.10 which very very old as
3.12.5 was current at that time. Grabbing the Fedora SPEC file still
helped a lot to start things off
- Using the Fedora fldigi.spec file has non-identified errors and will die
with errors like:
--
error: Installed (but unpackaged) file(s) found:
/usr/share/man/man1/fldigi.1.gz
to fix this, find the line
--
%{_datadir}/pixmaps/*
--
and add the following under it (flarq is new to 3.12.4)
--
%{_datadir}/applications/flarq.desktop
%{_mandir}/man1/fldigi.1.gz
%{_mandir}/man1/flarq.1.gz
--
to improve the build, replace the configure line with:
--
%configure --enable-optimizations=native
make %{?_smp_mflags} CFLAGS="$RPM_OPT_FLAGS"
--
NOTE:
Changes between my oldeer Fldigi 3.12.5 for Centos 5 and the and the
newer Fldigi 3.20.11 for Centos 6 notes:
1. In the 3.12.5 build notes, I used
%configure --enable-optimizations=native
which seems to throw warnins that the resulting code would
be using legacy i80387 FPU instructions. It turns out this
was an issue with the older Centos5 compilers and using "native"
is both recommended and enabled at the beginning of this document
and via the /etc/rpmrc file.
2. Starting in the 3.20.11 notes, I've added support
for the xmlrpc system which is used by the excellent Flrig rig
control program but Hamlib works as well.
3. LEGACY: The old Fldigi 3.20.11 now REQUIRES the obsolete
and deprecated fltk 1.1.9 toollike though the Fldigi
docs say it should work with 1.1.7. It's not true.
------------------------------------------------------------------------
NOTE: If you're upgrading from an older version of Fldigi, make sure
to :
1. make a copy of the old SPEC file, for me I do:
cp /usr/src/redhat/SPECS/fldigi.spec \
/usr/src/redhat/SPECS/Old/fldigi.spec
2. update the SPEC file to:
a. use the newer source tarball version
b. update the changelog section to reflect your changes
Next, regardless of using my SPEC file your you building your own, make sure
the version number reflects the current version of Fldigi
12a. - Fldigi - Depdendencies step #1
-------------------------------------------------------------
Fldigi Dependencies : All versions of Centos - 6 and 5
-------------------------------------------------------------
Regardless of building Fldigi via RPM spec files or doing everything
from source, the Fldigi build requires many other programs and libraries
(RPMs) to allow proper compiling and enabling all features installed:
#Installing libXt-devel is recommended and needed before building Fltk
yum install libXt-devel
# NOTE: Installing this may require 7+ other RPMs
#Installing libasound2 is recommended and needed before building Fltk
# I don't know why this isn't called libasound2 but this is NORMAL for Centos
yum install alsa-lib alsa-lib-devel
#A few others to make sure you have installed
yum install libX11-devel
yum install autoconf
yum install mesa-libGLU-devel
#fltk - Fast Light Toolkit
Fldigi (on Centos6 or Centos5) requires a *newer* version of fltk
than what EPEL and Rpmforge offers. To fix this, you have to
compile a new version yourself.
+--------------------------------------------------------------------+
| NOTE: things change over time so give Yum a try and maybe they now |
| offer fltk-1.3.0 or newer. If not, follow this next section. |
+--------------------------------------------------------------------+
Centos6 specific:
-----------------
#We'll use Fedora16 as a starting point
cd /usr/src/redhat/SRPMS
wget -O fltk-1.3.0-1.fc16.src.rpm \
http://download.fedoraproject.org/pub/fedora/linux/releases/16/Everything/source/SRPMS/fltk-1.3.0-1.fc16.src.rpm
#install the source SRPM
rpm -ivh fltk-1.3.0-1.fc16.src.rpm
#Next, we need to install build dependency RPMs:
yum install libjpeg-devel
#Ok... time to compile it
#
cd /usr/src/redhat/SPECS
rpmbuild -bb --target=x86_64 fltk.spec
#When you run the build above, make sure all the other required libs
#are seen. For example:
#
# Configuration Summary
# -------------------------------------------------------------------------
# Directories: prefix=/usr
# bindir=/usr/bin
# datadir=/usr/share
# datarootdir=${prefix}/share
# exec_prefix=/usr
# includedir=/usr/include
# libdir=/usr/lib64
# mandir=/usr/share/man
# Graphics: X11+Xft+Xdbe+Xinerama
# Image Libraries: JPEG=System
# PNG=System
# ZLIB=System
# Large Files: YES
# OpenGL: YES
# Threads: YES
#Install the compiled binaries
rpm -ivh /usr/src/redhat/RPMS/x86_64/fltk-1.3.0-1.el6.x86_64.rpm \
/usr/src/redhat/RPMS/x86_64/fltk-devel-1.3.0-1.el6.x86_64.rpm
Centos5 specific for older builds:
----------------------------------
yum install ftp://fr2.rpmfind.net/linux/epel/5/i386/fltk-1.1.9-4.el5.i386.rpm
yum install ftp://fr2.rpmfind.net/linux/epel/5/i386/fltk-devel-1.1.9-4.el5.i386.rpm
Both Centos6 and Centos5
------------------------
# libsndfile-devel
yum install libsndfile-devel
# libsamplerate-devel
yum install libsamplerate-devel
XMLRPC
------
# If you want the Fldigi's XMLRPC system for Flrig to work, you need
# to enable the xmlrpc code:
#
# Centos6:
# -------
yum install xmlrpc-c-c++ xmlrpc-c-client xmlrpc-c-client++ \
xmlrpc-c-devel xmlrpc-c xmlrpc-c-apps
# Centos 5
# -------
# Try installing from these pre-build versions:
yum install ftp://ftp.pbone.net/mirror/centos.karan.org/el5/extras/testing/i386/RPMS/xmlrpc-c-1.06.18-1.el5.kb.i386.rpm \
ftp://ftp.pbone.net/mirror/centos.karan.org/el5/extras/testing/i386/RPMS/xmlrpc-c-devel-1.06.18-1.el5.kb.i386.rpm \
ftp://ftp.pbone.net/mirror/centos.karan.org/el5/extras/testing/i386/RPMS/xmlrpc-c-apps-1.06.18-1.el5.kb.i386.rpm
# If the above RPMs won't work for some reason, you'll need to build the XMLRPC
# code from source:
# Not sure if cmake is required as we disable it later
yum install cmake
#Get the code
wget -O xmlrpc-c-1.06.18-1.el5.kb.src.rpm \
yum install http://centos.karan.org/el5/extras/testing/SRPMS/xmlrpc-c-1.06.18-1.el5.kb.src.rpm
#Install the code
rpm -ivh xmlrpc-c-1.06.18-1.el5.kb.src.rpm
# NOTE:
# 1 - this xmlrpc RPM uses cmake and not the usual configure system
# which seems to break the abyss-server subsystem:
#
# -- this following command should give a 0 but it doesn't
#
# xmlrpc-c-config c++2 abyss-server
# echo $?
#
# - to fix this, you have to redo the SPEC file a
# bit as shown below
# --
# 62,63c62,63
# < mkdir fedora
# < cd fedora
# ---
# > #mkdir fedora
# > #cd fedora
# 66,71c66,72
# < cmake .. \
# < -D_lib:STRING=%_lib \
# < -DMUST_BUILD_CURL_CLIENT:BOOL=ON \
# < -DMUST_BUILD_LIBWWW_CLIENT:BOOL=OFF \
# < -DCMAKE_INSTALL_PREFIX:PATH=%_prefix \
# < -DBUILD_SHARED_LIBS:BOOL=ON
# ---
# > #cmake .. \
# > # -D_lib:STRING=%_lib \
# > # -DMUST_BUILD_CURL_CLIENT:BOOL=ON \
# > # -DMUST_BUILD_LIBWWW_CLIENT:BOOL=OFF \
# > # -DCMAKE_INSTALL_PREFIX:PATH=%_prefix \
# > # -DBUILD_SHARED_LIBS:BOOL=ON
# > ./configure --prefix=%_prefix
# 77c78
# < cd fedora
# ---
# > #cd fedora
# 102d102
# < %_libdir/pkgconfig/*.pc
# 103a104,108
# > %_libdir/libxmlrpc++.a
# > %_libdir/libxmlrpc.a
# > %_libdir/libxmlrpc.la
# > %_libdir/libxmlrpc_*.*
# >
# 110d114
# < %_mandir/man1/*
# 113d116
# < %_bindir/xml-rpc-api2cpp
# 116a120,122
# > * Sat May 08 2010 DAvid Ranch - 1.06.18-2
# > - stopped using CMAKE, use ./configure to get xmlrpc-c-config C++2
# > abysss-server passing, added missing /usr/lib files into SPEC file
# Ok, time to build it
rpmbuild -bb --target i686 /usr/src/redhat/SPECS/xmlrpc-c.spec
#Time to install it
cd /usr/src/redhat/RPMS/i686
rpm -Uvh xmlrpc-c-1.06.18-1.i686.rpm xmlrpc-c-apps-1.06.18-1.i686.rpm \
xmlrpc-c-devel-1.06.18-1.i686.rpm
NOTE:
-----
- Using the above RPMs fails to work with Fldigi's configure system
-- the following test should give a result of "0" but it doesn't
xmlrpc-c-config c++2 abyss-server; echo $?
Back on track, lets move on for both Centos6 and Centos5
--
Perl-RPC-XML
-------------
# If the xml-rpc system is installed, the Fldigi system also needs the
# Perl RPC::XML CPAN module from RPMforge:
# NOTE: the old perl-XML-RPC package has been replaced by perl-RPC-XML
# package. Why they did this naming change boggles the mind
yum install perl-RPC-XML
# More packages to install
# ------------------------
#The following are required by HamLib which is required by Flwifi
yum install gd gd-devel tcl-devel libusb-devel doxygen libtool-ltdl-devel libXpm-devel
Ok, before we go much farther, we should get Hamlib running just in case you
don't want to use Flrig.
12b. - Hamlib for Fldigi (and other apps) - Rig control for your radio
Hamlib is a suite of programs and radio definitions to control a huge amount of
different radios. The amount of control depends on several factors suchs as:
- What does the radio offer for control (older radios are very simple,
new radios let you control almost every single thing about them)
- How mature is the Hamlib definition (some definitions are incomplete though
the radio supports additional rig control function)
Anyway, lets get going on building Hamlib:
# First, you need to install some build dependendies (if you don't
# already have them):
#
yum install libtool
# Next, we download the Fedora 16 SRPM to get the a baseline SPEC file, the
# patches for Hamlib to be compatible with Centos, and then later we'll
# download the newer Hamlib source code
#First, let's get the older SRPM and install it
cd /usr/src/redhat/SRPMS
wget -O hamlib-1.2.14-1.fc16.src.rpm http://download.fedoraproject.org/pub/fedora/linux/releases/16/Everything/source/SRPMS/hamlib-1.2.14-1.fc16.src.rpm
rpm -ivh hamlib-1.2.14-1.fc16.src.rpm
# Next, you can either use my SPEC file (recommended) or modify the Fedora
# one yourself your own:
#
# Getting and using my spec file:
#
cd /usr/src/redhat/SPECS
wget -O hamlib.spec http://www.trinityos.com/HAM/CentosDigitalModes/usr/src/redhat/SPECS/hamlib.spec
# Next, regardless of which SPEC file you use (my modified one or the stock
# Fedora one, it's recommend to download the NEWER production version of
# Hamlib sources. If there is even a newer version than 1.2.15, get that
# version instead and make the specific changes to allow for the newer
# version. You can browse the newest download URLs here:
#
# http://sourceforge.net/projects/hamlib/files/hamlib/
cd /usr/src/redhat/SOURCES/
wget -O hamlib-1.2.15.tar.gz \
http://downloads.sourceforge.net/project/hamlib/hamlib/1.2.15/hamlib-1.2.15.tar.gz?r=http%3A%2F%2Fsourceforge.net%2Fapps%2Fmediawiki%2Fhamlib%2Findex.php%3Ftitle%3DDownload&ts=1332655237&use_mirror=iweb
# Fixing your own SPEC file (not needed if you use my above spec file):
#
# The sources in hamlib 1.2.15 are newer and thus the Fedora16 RPM is
# a little out of date so we need to fix it and we should disable
# gnuradio and usrp while we're at it as they have HUGE dependencies
# that we don't use right now
# NOTE: there are some HAMlib options that you might want to enable
# such as USRP or Gnuradio but both of these options require
# SIGNIFICANTLY more work and packages to resolve. For example:
#
# --with-rigmatrix :: Generate rigmatrix tool (requires libgd)
# --without-winradio :: do not build winradio backend
# --with-gnuradio :: build gnuradio backend
# --with-usrp :: build USRP backend
# --without-rpc-backends :: do not build rpcrig and rpcrot backends
# NOTE2: Centos5
# with the 1.2.9n version and to get the perl and python
# options to work, you NEED to use the Fedora patch to set
# the proper destinations. The 1.2.8 patch applies cleanly
# on 1.2.9 but it does NOT apply to 1.2.13.1
cd /usr/src/redhat/SPECS
vim hamlib.spec
# In the top "BuildRequires:" lines, make the following changes:
# Update the version to reflect the new sources
Version: 1.2.15
# Remove "gnuradio-devel, usrp-devel"
#
# In the "%configure" section (don't forget that front "\"):
# remove "\
# --with-usrp"
# Find the following line and either DELETE it or comment it out with a pre-#
Patch2: hamlib-1.2.11-python2.7.configure.patch
# Find the following line and either DELETE it or comment it out with a pre-#
%patch2 -p1 -b .python-version
# Ok, let's compile hamlib and then install it:
#
# For Centos6:
rpmbuild -bb --target=x86_64 hamlib.spec
# For Centos5:
rpmbuild -bb --target i686 hamlib.spec
#Now that they're compiled, time to install them:
#For Centos6
#
cd /usr/src/redhat/RPMS/x86_64
rpm -Uvh hamlib-1.2.15-1.el6.x86_64.rpm hamlib-c++-1.2.15-1.el6.x86_64.rpm \
hamlib-c++-devel-1.2.15-1.el6.x86_64.rpm hamlib-debuginfo-1.2.15-1.el6.x86_64.rpm \
hamlib-devel-1.2.15-1.el6.x86_64.rpm hamlib-doc-1.2.15-1.el6.x86_64.rpm \
hamlib-perl-1.2.15-1.el6.x86_64.rpm hamlib-python-1.2.15-1.el6.x86_64.rpm \
hamlib-tcl-1.2.15-1.el6.x86_64.rpm
#For Centos5
cd /usr/src/redhat/RPMS/i686
rpm -Uvh hamlib*
?LEGACY - problably safe to ignore? -- confirm what Flwifi is
-------------------------------------------------------------
- Flwifi required hamlib-devel
- current available is 1.2.13.1
- last working version installed 1.2.9
- fedora repo is at 1.2.8
- not in rpmforge
12c. - Fldigi - Depdendencies step #2
Ok, back to more dependencies for Fldigi before we can compile it
ALSA & PortAudio specific
-----------------------------------
- As mentioned above in the ALSA section towards the top of this document,
both Centos6 and Centos5 ships with very old ALSA kernels and PortAudio
code. You need to upgrade BOTH for proper operation:
ElRepo ALSA (Centos6):
----------------------------
# NOTE: this will only upgrade the ALSA kernel soundcard drivers
# which remains compatible with the older ALSA libraries,
# tools, etc. This is very easy and works well
#
yum install http://elrepo.org/linux/elrepo/el6/x86_64/RPMS/kmod-alsa-1.0.24-1.el6.elrepo.x86_64.rpm
ElRepo ALSA (Centos5):
----------------------------
# NOTE: this will only upgrade the ALSA kernel soundcard drivers
# which remains compatible with the older ALSA libraries,
# tools, etc. This is very easy and works well
cd /usr/src/redhat/RPMS/i686
wget -O kmod-alsa-1.0.24-1.el5.elrepo.i686.rpm \
http://elrepo.org/linux/elrepo/el5/i686/RPMS/kmod-alsa-1.0.24-1.el5.elrepo.i686.rpm
rpm -ivh /usr/src/redhat/RPMS/i686/kmod-alsa-1.0.24-1.el5.elrepo.i686.rpm
PortAudio Snapshot:
-------------------
PortAudio is becoming legacy to Linux much like OSS was some time ago.
With that said, it's still good to have the support in the system
and other programs like WSJT still use it:
NOTE:
-----
* The EPEL portaudio-19-9.el6 for Centos6 and portaudio-19-8.el5 *
* for Centos5 is **NOT** new enough and you must use the newest *
* Tip-Of-Tree version *
cd /usr/src/redhat/SOURCES
wget -O pa_snapshot.tgz http://www.portaudio.com/archives/pa_snapshot.tgz
#Get dranch's portaudio-tot.spec file:
cd /usr/src/redhat/SPECS
wget -O portaudio-tot.spec \
http://www.trinityos.com/HAM/CentosDigitalModes/usr/src/redhat/SPECS/portaudio-tot.spec
#Look at the following page: http://www.portaudio.com/download.html
#
# Find the date specified for pa_snapshot.tgz
#Edit the portaudio-tot.spec file and change the date to reflect
# this newest TOT - for example:
#
# Version: 19
# Release: Release: 20120117%{?dist}
#Centos6 specific
rpmbuild -bb --target x86_64 portaudio-tot-el6.spec
rpm -ivh /usr/src/redhat/RPMS/x86_64/portaudio-19-20120117.el6.x86_64.rpm \
/usr/src/redhat/RPMS/x86_64/portaudio-devel-19-20120117.el6.x86_64.rpm
#Centos5 specific
rpmbuild -bb --target i686 portaudio-tot.spec
rpm -ivh /usr/src/redhat/RPMS/i686/portaudio-20100923.el5.i686.rpm
Additional Soundcard and Sound sub-system specific dependencies:
----------------------------------------------------------------
# Also install
yum install jack-audio-connection-kit-devel jack-audio-connection-kit
# This comes from ATrpms - needed for proper audio routing and levels
# from Pulse to Fldigi
yum install pavucontrol
12d. - Fldigi - Final Compiling
Finally, time to compile Fldigi..
------------------------------------
cd /usr/src/redhat/SPECS/
Centos6 on a x64 system:
------------------------
rpmbuild -bb --target x86_64 fldigi.spec
Centos5 on a i686 system:
-------------------------
rpmbuild -bb --target i686 fldigi.spec
Regardless of which Centos version you're building for, look back
in the RPM building process and make SURE it looks some thing like
the following. Make sure all the options are "yes", etc:
-------------------------------------
Version ..................... 3.21.35
Static linking .............. no
CPU optimizations ........... sse2
Debugging ................... no
fldigi ...................... yes
flarq ....................... yes
i18n ........................ yes
fldigi build options:
sndfile ..................... yes
oss ......................... yes
portaudio ................... yes
pulseaudio .................. yes
hamlib ...................... yes
xmlrpc ...................... yes
-------------------------------------
and now install it:
#Centos6 specific:
rpm -ivh /usr/src/redhat/RPMS/x86_64/fldigi-3.21.35-1.el6.x86_64.rpm
#Centos5 specific:
rpm -Uvh /usr/src/redhat/RPMS/i686/fldigi-3.20.21-1.i686.rpm
13. - Flrig - Rig control with or without Fldigi
Flrig is a rig control program that can either be stand-alone or a companion
program to Fldigi. Fldigi by itself can use Hamlib but it doesn't always
give all the desired information. Flrig gives you:
- It's completely independent of Hamlib and has it's own radio
definitions
- S-meter readouts as shown by the rig itself
- Full control of the rig's VFO-A, VFO-B, Split control
- Full control of the rig's speaker volume, RF power, IF shift, Notch
filter, MIC gain ATT, PreAmp1/2, NoiseBlanker, etc.
----------------------------------------------------------------------------
NOTE: this program is OPTIONAL to use with Fldigi but is highly recommended
----------------------------------------------------------------------------
This is the main window for controlling everything on the rig from RF power, using the tuner, etc:
Please note that Flrigit does NOT provide any QSO logging support what so
ever. If you want that, either use Fldigi's built-in logger, use Fllog,
or even use Xlog
Ok, let's get to it. Flrig is a very new program so you might want to try the Alpha
version if the posted version does't work for you. The primary version didn't for
me with my FT-950. It's new so we have to piece things together a bit:
cd /usr/src/redhat/SOURCES
#Getting the version 1.3.08 - change the version number to match the newest
# release version available
wget http://www.w1hkj.com/downloads/flrig/flrig-1.3.08.bin.tgz
Get the TrinityOS spec file (not recommended):
cd /usr/src/redhat/SPECS
wget -O flrig.spec \
http://www.trinityos.com/HAM/CentosDigitalModes/usr/src/redhat/SPECS/flrig.spec
# Update the spec file to reflect the current version of Flrig chosen
vim flrig.spec
Alternatively, you can create your own SPEC file
------------------------------------------------
#These notes reflect an older ALPHA build
cd /usr/src/redhat/SPECS
wget http://dp67.fedorapeople.org/pkgs/SPECS/flrig.spec
vim flrig.spec
--
* update the version to "1.1.3CY"
* Change the release string to "1%{?dist}"
* Change the source0 to "http://www.w1hkj.com/beta/flrig/%{name}-%{version}.tar.gz"
* Change the %prep0 to "%setup -q -n %{name}-%{version}"
* Change the %build section, make the "configure" and "make" lines read:
%configure --enable-optimizations=native
make %{?_smp_mflags} CFLAGS="$RPM_OPT_FLAGS"
* Change the %install line from:
desktop-file-install \
to
desktop-file-install --vendor="" \
also append the commend below the command to say:
# --vendor obsolete per new guidlines but leaving it in because
# this is an existing package with vendor previously installed
--
Next, regardless of using my SPEC file your you building your own, make sure
the version number reflects the current version of Flrig
Now let's build and install it:
cd /usr/src/redhat/SPECS/
NOTE: In the 3.12.5 build notes, I used to use
%configure --enable-optimizations=native
which seemed to throw warnings that the resulting code would
be using legacy i80387 FPU instructions. It turns out this
was an issue with the older Centos5 compilers and using "native"
is both RECOMMENDED and enabled
NOTE #2: at the beginning of this document, the "native" optimizations
was enabled via the /etc/rpmrc file but the Fldigi
configuration script does NOT honor those settings
#Centos6 specific
rpmbuild -bb --target=x86_64 flrig.spec
rpm -ivh /usr/src/redhat/RPMS/x86_64/flrig-1.2.6-1.el6.x86_64.rpm
#Centos5 specific
rpmbuild -bb --target=i686 flrig.spec
rpm -Uvh /usr/src/redhat/RPMS/i686/flrig-1.1.3CY-1.i686.rpm
