Discussion:
multiple kiss ports
Stef Daniels VK5HSX
2007-02-14 13:33:06 UTC
Permalink
Greetings,

I am in the process of trying to get a BBS back operational. The
following is the setup:

P4 1.2Ghz Celeron
MSI Motherboard
512MB RAM
40GB ATA Drive
ttyS0 -> 9600bd -MFJ 1270b (1200bd TNC) axport '2'
ttyS1 -> 4800bd - AEA PK232 (4800bd TNC) axport '3'
Debian GNU\linux 3.1 (2.4.27 kernel)
using: libax25-0.0.11, ax25-apps-0.0.6, aax25-tools-0.0.8, node-0.3.2,
fbb7.04j

The problem is after we run our ax25 script to call up modules, tnc into
kiss and kissattach devices (which all work fine), upon connect using
port '2' the tnc "sta" LED comes on and tnc hangs.

We have tried the following:

Different- Computers, Cables, TNC's, O\S's, kernel's, hardrive, P\Supply
and Serial ports (PCI Serial Cards), to NO avail.

Any ideas, help, comments greatfully and most appreciatedly received!!
--
Regards,

Stef Daniels VK5HSX (OpenPGP:0xFDE007F6)
Amateur Radio Station
Adelaide, South Australia
E-mail: ***@wia.org.au
Member Wireless Inst. of Aust. (www.wia.org.au)
Proud Debian GNU\Linux User. (www.au.debian.org)
Ray Wells
2007-02-14 20:18:18 UTC
Permalink
Post by Stef Daniels VK5HSX
Greetings,
I am in the process of trying to get a BBS back operational. The
P4 1.2Ghz Celeron
MSI Motherboard
512MB RAM
40GB ATA Drive
ttyS0 -> 9600bd -MFJ 1270b (1200bd TNC) axport '2'
ttyS1 -> 4800bd - AEA PK232 (4800bd TNC) axport '3'
Debian GNU\linux 3.1 (2.4.27 kernel)
using: libax25-0.0.11, ax25-apps-0.0.6, aax25-tools-0.0.8, node-0.3.2,
fbb7.04j
The problem is after we run our ax25 script to call up modules, tnc into
kiss and kissattach devices (which all work fine), upon connect using
port '2' the tnc "sta" LED comes on and tnc hangs.
Different- Computers, Cables, TNC's, O\S's, kernel's, hardrive, P\Supply
and Serial ports (PCI Serial Cards), to NO avail.
Any ideas, help, comments greatfully and most appreciatedly received!!
Hi Stef,

You haven't really told us much, some configs would be nice, especially
your ax25 start-up file, axports, and port.sys for starters.

Does the problem occur using the call function or does it happen from
the bbs? You don't say if you're trying to use the bbs yet, only that
you want to get one running, and you don't say what the bbs is (or will
be). It's not safe to assume fbb.

Did you really try different O\S's, or was it just different Linux
distributions?

Although I'm using kernel 2.6.18-3 on the system here, I do have another
installation on a P166 with kernel 2.4.31 (from memory), and they both
work ok.

Both machines run Debian 3.1 (Sarge)

Ray vk2tv
Stef Daniels VK5HSX
2007-02-15 05:25:36 UTC
Permalink
Post by Ray Wells
Hi Stef,
You haven't really told us much, some configs would be nice, especially
your ax25 start-up file, axports, and port.sys for starters.
Okay.

#!/bin/sh
#
# This is /etc/init.d/ax25
#
# VK5TTY BBS AX25 Script
# by Stef Daniels VK5HSX and Geoff Madden VK5KMG.
# in January 2007.
#----------------------------------------------------
# Date and person making changes to script
#----------------------------------------------------
# Date Who Changes
#----------------------------------------------------
# 12/01/2007 SJD Created script
# 13/01/2007 SJD Added kissattach for ptyqa & b
#
#----------------------------------------------------
#
# Firmware-TNC's placed into kiss mode
echo "... MFJ 1270b TNC Placed into kiss mode"
#
stty 9600 < /dev/ttyS0
#
# MFJ 1270b in kiss with TF27 chip
echo -e "\r\***@K1\r" > /dev/ttyS0
#
# MFJ 1270b in kiss with TNC2 chip
#echo -e "kisson\rrestart\r" > /dev/ttyS0
#
sleep 3
#
# setting baud rate to 4800bd device (PK232).
setserial /dev/ttyS1 base_baud 4800
#
echo "Starting modules...."
# starting modules
/sbin/modprobe ax25
/sbin/modprobe mkiss
/sbin/modprobe netrom
/sbin/modprobe rose
#
echo "... configuring 'ax25' ports"
sleep 1
#
echo -n "port 2 '144.900 port'"
# com1 1200bd user port 144.900MHz
/usr/sbin/kissattach -m 255 /dev/ttyS0 2 44.136.176.220
/sbin/ifconfig 2 44.136.176.220 netmask 255.255.255.0 \
# broadcast 44.136.176.255 arp
#
echo -n "port 3 '434.050 port'"
# com2 4800bd backbone port 434.050MHz
/usr/sbin/kissattach -m 255 /dev/ttyS1 3 44.136.203.2
/sbin/ifconfig 3 44.136.203.1 netmask 255.255.255.0 \
# broadcast 44.136.203.255 arp
#
#echo -n "port4 '439.075 port'"
# com3 4800bd user port 439.075MHz
#/usr/sbin/kissattach -m 255 /dev/ttyS2 4 44.137.177.220
#/sbin/ifconfig 4 44.136.177.220 netmask 255.255.255.0 \
# broadcast 44.136.177.255 arp
#
# configuring loopback ports 'loop0' & 'loop1'"
/usr/sbin/kissnetd /dev/ptyq1 /dev/ptyq2 &
#
sleep 3
#
echo -n "loop0 loop1"
/usr/sbin/kissattach /dev/ttyq1 loop0 10.0.0.1
/usr/sbin/kissattach /dev/ttyq2 loop1 10.0.0.2
#
echo -n "... configuring 'netrom'"
#
/usr/sbin/nrattach -m 236 netrom
/usr/sbin/nrattach -m 236 nrbb
/usr/sbin/nrattach -m 235 nrdxc
#
#
echo -n "Starting ax25 & netrom daemons:"
#
echo "ax25 daemon"
/usr/sbin/ax25d
#
echo "netrom daemon"
/usr/sbin/netromd -i -t 45
#
echo "axip daemon"
/usr/sbin/axipd
#
# End

# /etc/ax25/axports for VK5TTY BBS
#
# The format of this file is:
#
# name callsign speed paclen window description
#
2 vk5tty-15 1200 256 2 Adelaide South LAN 144.900
3 vk5tty-14 4800 256 2 Adelaide Area Backbone 434.050
#4 vk5tty-13 1200 256 2 Adelaide South LAN 439.075
loop0 vk5aaa-1 38400 255 2 Loop #1
loop1 vk5aaa-2 38400 255 2 Loop #2
# End

#/etc/ax25/nrports
#
# The format of this file is:
#
# name callsign alias paclen description
#
netrom VK5TTY-2 ADLS2 235 VK5TTY Packet Radio Node-Adelaide South
nrbb VK5TTY-1 ADLSBB 235 VK5TTY Packet Radio BBS-Adelaide South
nrdxc VK5TTY-6 ADLSDX 235 VK5TTY Packet Radio DXCluster-Adelaide South
# End

#/etc/ax25/ax25d.conf
#
# ax25d Configuration File.
#
#----------------------------------------------------------------------
# Date Who Action
# 21/2/2005 KMG & HSX Compiled & Installed new ax25 system
#
#----------------------------------------------------------------------
# AX.25 Ports begin with a '['.
#
[VK5TTY-2 VIA 2]
NOCALL * * * * * * L
default * * * * * * - root /usr/sbin/node node
#
[VK5TTY-2 VIA 3]
NOCALL * * * * * * L
default * * * * * * - root /usr/sbin/node node
#
#[VK5TTY-2 VIA 4]
#NOCALL * * * * * * L
#default * * * * * * - root /usr/sbin/node node
#
[VK5TTY-12 VIA 3]
NOCALL * * * * * * L
default * * * * * * - root /usr/sbin/ax25_call ax25_call loop0 %s
vk5tty-0
#
#----------------------------------------------------------------------
# NET/ROM Ports begin with a '<'.
#
<netrom>
NOCALL * * * * * * L
default * * * * * * - root /usr/sbin/node node
#
#----------------------------------------------------------------------
# Rose X.25 Ports begin with a '{'
# Rose Local Services
#~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
{NODE-0 via rs2}
NOCALL * * * * * * L
default * * * * * * - root /usr/sbin/node node
#
{NODE-0 via rs3}
NOCALL * * * * * * L
default * * * * * * - root /usr/sbin/node node
#
{NODE-0 via rs4}
NOCALL * * * * * * L
default * * * * * * - root /usr/sbin/node node
#
{HEARD-0 via rsl1}
NOCALL * * * * * * L
default * * * * * * - root /usr/bin/mheard mheard
#
#{HEARD-0 via rsl2}
#NOCALL * * * * * * L
#default * * * * * * - root /usr/bin/mheard mheard
#
{USERS-0 via rsl1}
NOCALL * * * * * * L
default * * * * * * - root /usr/sbin/rusers.sh rsusers.sh
#
#{USERS-0 via rsl2}
#NOCALL * * * * * * L
#default * * * * * * - root /usr/sbin/rusers.sh rsusers.sh
#
#~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
# Rose Uplink/Downlink Configs
#~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
# Rose Downlink Connections
#
{* via rs2}
NOCALL * * * * * * L
default * * * * * * - root /usr/sbin/rsdwnlnk rsdwnlnk 2 vk5tty-3
#
{* via rs3}
NOCALL * * * * * * L
default * * * * * * - root /usr/sbin/rsdwnlnk rsdwnlnk 3 vk5tty-3
#
{* via rs4}
NOCALL * * * * * * L
default * * * * * * - root /usr/sbin/rsdwnlnk rsdwnlnk 4 vk5tty-3
#
{* via rsl1}
NOCALL * * * * * * L
default * * * * * * - root /usr/sbin/rsdwnlnk rsdwnlnk loop1 vk5tty-3
#
# Rose Uplink connections
#
[VK5TTY-3* via 2]
NOCALL * * * * * * L
default * * * * * * - root /usr/sbin/rsuplnk rsuplnk rs2
#
[VK5TTY-3* via 3]
NOCALL * * * * * * L
default * * * * * * - root /usr/sbin/rsuplnk rsuplnk rs3
#
#[VK5TTY-3* via 4]
#NOCALL * * * * * * L
#default * * * * * * - root /usr/sbin/rsuplnk rsuplnk rs4
#
[VK5TTY-3* via loop1]
NOCALL * * * * * * L
default * * * * * * - root /usr/sbin/rsuplnk rsuplnk rsl1
#
#
Post by Ray Wells
Does the problem occur using the call function or does it happen from
the bbs? You don't say if you're trying to use the bbs yet, only that
you want to get one running, and you don't say what the bbs is (or will
be). It's not safe to assume fbb.
Problem occurs when trying either a "call 2 vk5***" or fbb mail
forwarding. We have stopped FBB and tried manually kissattach and
calling with ports on console, with same results.
Post by Ray Wells
Did you really try different O\S's, or was it just different Linux
distributions?
Yes O\S include Slackware 10.1, 10.2 and Debian 3.0, 3.1 and 4.0. both
2.4 and 2.6 kernels.

With regards to Windows using TSTHwin, the system TNC works fine.
Post by Ray Wells
Although I'm using kernel 2.6.18-3 on the system here, I do have another
installation on a P166 with kernel 2.4.31 (from memory), and they both
work ok.
Both machines run Debian 3.1 (Sarge)
Ray vk2tv
Thanks for the help..
--
Regards,

Stef Daniels VK5HSX (OpenPGP:0xFDE007F6)
Amateur Radio Station
Adelaide, South Australia
E-mail: ***@wia.org.au
Member Wireless Inst. of Aust. (www.wia.org.au)
Proud Debian GNU\Linux User. (www.au.debian.org)
Ralf Baechle DL5RB
2007-02-14 20:14:00 UTC
Permalink
Post by Stef Daniels VK5HSX
P4 1.2Ghz Celeron
MSI Motherboard
512MB RAM
40GB ATA Drive
ttyS0 -> 9600bd -MFJ 1270b (1200bd TNC) axport '2'
ttyS1 -> 4800bd - AEA PK232 (4800bd TNC) axport '3'
Debian GNU\linux 3.1 (2.4.27 kernel)
using: libax25-0.0.11, ax25-apps-0.0.6, aax25-tools-0.0.8, node-0.3.2,
fbb7.04j
The problem is after we run our ax25 script to call up modules, tnc into
kiss and kissattach devices (which all work fine), upon connect using
port '2' the tnc "sta" LED comes on and tnc hangs.
Different- Computers, Cables, TNC's, O\S's, kernel's, hardrive, P\Supply
and Serial ports (PCI Serial Cards), to NO avail.
Any ideas, help, comments greatfully and most appreciatedly received!!
Did you try a 2.6 kernel also? The 2.4 mkiss driver usually works just
fine but it's a fairly suspect piece of code anyway, so I've turned the
KISS driver upside down for Linux 2.6.

A no-no at the current state of the code are SMP or preemptible kernels.

73 de DL5RB op Ralf

--
Loc. JN47BS / CQ 14 / ITU 28 / DOK A21
Packet: ***@DB0FHN.#BAY.DEU.EU
-
To unsubscribe from this list: send the line "unsubscribe linux-hams" in
the body of a message to ***@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Bernard Pidoux
2007-02-15 10:29:59 UTC
Permalink
Post by Stef Daniels VK5HSX
Greetings,
I am in the process of trying to get a BBS back operational. The
P4 1.2Ghz Celeron
MSI Motherboard
512MB RAM
40GB ATA Drive
ttyS0 -> 9600bd -MFJ 1270b (1200bd TNC) axport '2'
ttyS1 -> 4800bd - AEA PK232 (4800bd TNC) axport '3'
Debian GNU\linux 3.1 (2.4.27 kernel)
using: libax25-0.0.11, ax25-apps-0.0.6, aax25-tools-0.0.8, node-0.3.2,
fbb7.04j
The problem is after we run our ax25 script to call up modules, tnc into
kiss and kissattach devices (which all work fine), upon connect using
port '2' the tnc "sta" LED comes on and tnc hangs.
Different- Computers, Cables, TNC's, O\S's, kernel's, hardrive, P\Supply
and Serial ports (PCI Serial Cards), to NO avail.
Any ideas, help, comments greatfully and most appreciatedly received!!
Are you sure that your TNCs are set in KISS mode before using mkiss
driver for AX25 ?

You must put them into KISS mode manually while no mkiss driver is
loaded and using a terminal program
such as MINICOM.

I used minicom to adjust my KPC9612 dual port TNC serial baud rate and
calibrate the modulation
level of 1200 and 9600 baud radio ports.


73 de Bernard, f6bvp
--
To UNSUBSCRIBE, email to debian-hams-***@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact ***@lists.debian.org
Stef Daniels VK5HSX
2007-02-15 14:01:55 UTC
Permalink
Hi Bernard,
Post by Bernard Pidoux
Are you sure that your TNCs are set in KISS mode before using mkiss
driver for AX25 ?
Yep, using a script that includes:

# Firmware-TNC's placed into kiss mode
echo "... MFJ 1270b TNC Placed into kiss mode"
#
stty 9600 < /dev/ttyS0
#
# MFJ 1270b in kiss with TF27 chip
echo -e "\r\***@K1\r" > /dev/ttyS0 <---- this puts TF27 chip into KISS
#
# MFJ 1270b in kiss with TNC2 chip
#echo -e "kisson\rrestart\r" > /dev/ttyS0 <--- this puts TNC2 into KISS
#
Post by Bernard Pidoux
You must put them into KISS mode manually while no mkiss driver is
loaded and using a terminal program
such as MINICOM.
Have used minicom to test TNC is woring and does go into kiss. LED's
flash three (3) times..
Post by Bernard Pidoux
I used minicom to adjust my KPC9612 dual port TNC serial baud rate and
calibrate the modulation
level of 1200 and 9600 baud radio ports.
73 de Bernard, f6bvp
-
To unsubscribe from this list: send the line "unsubscribe linux-hams" in
More majordomo info at http://vger.kernel.org/majordomo-info.html
--
Regards,

Stef Daniels VK5HSX (OpenPGP:0xFDE007F6)
Amateur Radio Station
Adelaide, South Australia
E-mail: ***@wia.org.au
Member Wireless Inst. of Aust. (www.wia.org.au)
Proud Debian GNU\Linux User. (www.au.debian.org)
Loading...