[Packet] Packet under Linux - port not active.
Doug Laidlaw
laidlaws at hotkey.net.au
Thu May 4 22:07:55 EDT 2006
I am running Mandriva 2006 with kernel 2.6.12 into a MFJ 1270B. When trying
to start packet, I got an error message:
kissattach: Error setting line discipline: TIOCSETD: No such device
On googling, I found a reply in Debian-hams to somebody using Ubuntu (also
kernel 2.6.12) advising him to upgrade to kernel 2.6.16, or at least 2.6.14.
I downloaded kernel2.6.16 and that seems to have dealt with that one.
Now, when I start packet, the port (COM2, /dev/ttyS1) is assigned to ax0 and
is promptly locked and made inaccessible. In a Linpac terminal and elsewhere,
there is a statement that my VHF port is not active and the computer port
cannot be accessed. T+Relevant config files are as follows:
axports:
# /etc/ax25/axports
#
# The format of this file is:
#
# name callsign speed paclen window description
#
vhf VK3KDI-1 1200 255 2 144.925 MHz (1200 bps)
ax25d.conf:
# ax25d.conf for VK3KDI - 04/05/06
# This configuration uses the AX.25 port defined earlier.
# <peer> Win T1 T2 T3 idl N2 <mode> <uid> <exec> <argv[0]>[<args....>]
[VK3KDI-1 via vhf]
parameters 1 10 * * * * *
NOCALL * * * * * * L
default 1 10 5 100 180 5 * root /usr/sbin/pms pms -a -o vk3kdi
--
startax25:
# MFJ-1270B to KISS mode
stty -F /dev/ttyS1 speed 9600
echo -en "KISS ON\015" > /dev/ttyS1
echo -en "RESTART\015" > /dev/ttyS1
echo "MFJ-1270B should be in KISS mode now"
modprobe mkiss
/usr/sbin/kissattach /dev/ttyS1 vhf 192.168.44.1
Another Ham said that he got Packet working by setting the IP address in the
Kissattach line to (as I understand his post) the address assigned to his
computer by DHCP. It is my understanding that it should be one of the groups
reserved for LANs but distinct from any existing LAN address.
Also, is there a precedent for starting packet from xinetd, please?
Doug VK3KDI.
Experience is simply the name we give our mistakes.
- Oscar Wilde
More information about the Packet
mailing list