Trying to get Ax25 running.

Trying to get Ax25 running.

[Chuck Hast]

Folks,
I am a bit new to this. I am running SuSE 9.1 I have installed the AX25
stuff, and when I set up the port I have a KISS TNC on I see the commands
being sent to it.
When I run call, and it appears that the connection is established the whole
thing locks up. Not just that screen, but X, Keyboard and all. At that point
I end up hitting the power button in order to get out of it.

I am going to try to get a second machine set up so I can try to get into
it remotely and see if I can kill it that way.

Any ideas of what I have screwed up?

-- 
Chuck Hast 
To paraphrase my flight instructor;
"the only dumb question is the one you DID NOT ask resulting in my going
out and having to identify your bits and pieces in the midst of torn
and twisted metal."

Re: Trying to get Ax25 running.

[Jeroen Vreeken]

Chuck Hast wrote:
> Folks,
> I am a bit new to this. I am running SuSE 9.1 I have installed the AX25
> stuff, and when I set up the port I have a KISS TNC on I see the commands
> being sent to it.
> When I run call, and it appears that the connection is established the whole
> thing locks up. Not just that screen, but X, Keyboard and all. At that point
> I end up hitting the power button in order to get out of it.

What kernel are you using? 2.4? if so try 2.6.
Try it without X, with any luck you will atleast catch an oops printed 
to the console that could help us further.

Jeroen

Re: Trying to get Ax25 running.

[Ron]

Chuck we need some basic background info about your
setup first.
1. What ax25 rpms have you installed?
2. What are your attach commands?
3. What are you trying to accomplish?..setup for
LinFBB?

FYI here is the first part of my startup script for
ax25 call fbb_start in /etc/ax25 along with other ax25
files:

/usr/sbin/kissattach /dev/ttyS0 vhf xxx.xxx.xxx.xxx

Where xxx=my ip address, with MFJ tnc in kiss mode on
com1. See also com port speed in axports.

 Check your ax25 device with 'ifconfig' and you should
see ax0.

Be sure to read ax25-how-to at:

http://www.tldp.org/HOWTO/AX25-HOWTO/


73, Ron

Chuck Hast wrote:
> Folks,
> I am a bit new to this. I am running SuSE 9.1 I have
installed the AX25
> stuff, and when I set up the port I have a KISS TNC
on I see the commands
> being sent to it.
> When I run call, and it appears that the connection
is established the whole
> thing locks up. Not just that screen, but X,
Keyboard and all. At that point
> I end up hitting the power button in order to get
out of it. 


		
__________________________________
Do you Yahoo!?
Read only the mail you want - Yahoo! Mail SpamGuard.
http://promotions.yahoo.com/new_mail 

Re: Trying to get Ax25 running.

[Chuck Hast]

Folks,
I updated my Linux install to 2.6.5.7-108default, and only got one lockup
and that was under X. At first I thought it may have been due to the fact
that all the ax25 stuff is under root, not sure if that is where it is supposed
to be. If I run  call from a consol screen under both root and my login, it
appears to be working now to the point where I can do ax25 calls. Next
step will be to start putting in the network stuff.

Once I get it all running then I will need to see how to build something
that I can stick on a CD in order to distribute to the other switch ops who
want to move to Linux. 

I assume that Call will not run in a X console. That appears to be where
things go off into the weeds, by way last time I locked it up I tried to
ssh in from another machine on my network, no joy. I could not even ping
the machine, so it appears that it was locking up solid. 

Now to start adding the ROSE and Node stuff to it so that we can start
testing the piece that we need for our network here, and also will be
adding the other network stuff so people can play with the whole nine
yards.



-- 
Chuck Hast 
To paraphrase my flight instructor;
"the only dumb question is the one you DID NOT ask resulting in my going
out and having to identify your bits and pieces in the midst of torn
and twisted metal."

Re: Trying to get Ax25 running.

[Chuck Hast]

Well, it appears that the locking up of the system happens when I attempt
to run CALL under X in a terminal screen. As long as I run it on a consol
it does not lock up. Is this normal or do I need to go in and change make
some changes some where so I can run it under a xterm? I can run listen
and mheard in xterm screens just fine, but so far call is avoiding it all.




-- 
Chuck Hast 
To paraphrase my flight instructor;
"the only dumb question is the one you DID NOT ask resulting in my going
out and having to identify your bits and pieces in the midst of torn
and twisted metal."

Re: Trying to get Ax25 running.

[Dennis Boone]

 > Well, it appears that the locking up of the system happens when I
 > attempt to run CALL under X in a terminal screen. As long as I run
 > it on a consol it does not lock up. Is this normal or do I need to
 > go in and change make some changes some where so I can run it under
 > a xterm? I can run listen and mheard in xterm screens just fine,
 > but so far call is avoiding it all.

Call should work fine in an xterm.  The fact that it locks up the
machine so badly that pings &c don't work would seem to imply that
there's either a hardware problem or a kernel problem, possibly in
the configuration of the AX25 wares.

Getting into the long-haired realm, if you have a second serial
port, you might try setting up a serial console, to see if you
can get an oops message while running X.  See e.g.

	http://www.tldp.org/HOWTO/Remote-Serial-Console-HOWTO/

for details.

Dennis Boone
KB8ZQZ

Re: Trying to get Ax25 running.

[Chuck Hast]

Folks,
I have used the AX25 config tool to configure this stuff. I am trying
to set up things to run
mkiss, but I can not quite figure out where to put the -c so that
mkiss will use the crc check.

ax25-config tool does not ask for it, so I assume that the author did
not get that far down the
road, but when I look in the files it creates I do not see the mkiss
line anywhere, I do see
where it does a modprobe for ax25,kiss and mkiss, the one that is
installed when I do a
lsmod is mkiss. So now if I can just figure out where the mkiss
configuration line is stuck I
should be able to set it up to use the crc check on the kiss frames.

On our DOS FPAC switches we are using BPQ KISS eproms with the CRC, so
in order to
not have to redo all of the eproms I am just trying to get the crc
check running, the man
page on mkiss says that the -c parm will cause it to do crc.

Re: Trying to get Ax25 running.

[Tomi Manninen]

On Fri, 2004-10-15 at 19:57, Chuck Hast wrote:

> I have used the AX25 config tool to configure this stuff. I am trying
> to set up things to run
> mkiss, but I can not quite figure out where to put the -c so that
> mkiss will use the crc check.

mkiss and mkiss are not the same... :)

The manual page you obviously have been reading, is for a user mode
tool that can be used to connect one or more kissattached kernel
interfaces to one serial port running one or more TNC's with
multidrop-kiss, crc-check etc. extended KISS modes.

The mkiss that you load with modprobe/insmod is a kernel module
that provides the kernel services that kissattach needs when you
make kernel KISS interfaces.

-- 
Tomi Manninen / OH2BNS / KP20ME04

Re: Trying to get Ax25 running.

[Dennis Boone]

 > I have used the AX25 config tool to configure this stuff. I am trying
 > to set up things to run mkiss, but I can not quite figure out where
 > to put the -c so that mkiss will use the crc check.
 > 
 > ax25-config tool does not ask for it, so I assume that the author
 > did not get that far down the road, but when I look in the files it
 > creates I do not see the mkiss line anywhere, I do see where it does
 > a modprobe for ax25,kiss and mkiss, the one that is installed when I
 > do a lsmod is mkiss. So now if I can just figure out where the mkiss
 > configuration line is stuck I should be able to set it up to use the
 > crc check on the kiss frames.

It might help if you posted your current config files, but from memory,
here are the commands in my startup script:

	mkiss -c -l -s 19200 /dev/ttyS0 /dev/ptyz0 /dev/ptyz1
	kissattach /dev/ptyz0 hfport 44.135.96.242
	kissattach /dev/ptyz0 vhfport 44.135.96.243

where:

	19200 is the baud rate (my hardware seems to keep up just fine
	with no handshaking at this speed, ymmv)

	/dev/ttyS0 is the serial port to which the TNC is connected

	/dev/ptyz0 ... are the pty devices created by mkiss to allow
	separate access to the TNC's different ports

	[v]hfport is the name of the port from the axports file

	44.135.96.24x are the IP addresses allocated to the ports (not
	actually mine, and while you need to have something here, if you're
	not doing IP, I think you can use anything that doesn't conflict)

You may also need the polling option of mkiss in your setup.

Then I go on to start up a node program, ax25d, convers and database
services, etc.

Here's my axports file:

	hfport KB8ZQZ-3 19200 255 7 HF Port
	vhfport KB8ZQZ-4 19200 255 7 VHF Port on 145.03

With this setup, I can then do:

	call vhfport wc8lan-15

to talk to the pbbs at the EOC.

Reading your comments about modules, I wonder if you have the ax25
and kiss modules built into your kernel?

Dennis Boone
KB8ZQZ

Re: Trying to get Ax25 running.

[Gérard / F6FGZ]

Dennis Boone a écrit :

>         mkiss -c -l -s 19200 /dev/ttyS0 /dev/ptyz0 /dev/ptyz1
>         kissattach /dev/ptyz0 hfport 44.135.96.242
>         kissattach /dev/ptyz0 vhfport 44.135.96.243

I correct your memory ;-)
kissattach /dev/ttyz0 hfport 44.135.96.242
kissattach /dev/ttyz1 vhfport 44.135.96.243

It is important to have ptyxx from one side corresponding to ttyxx on the other
side.
From /usr/src/linux/Documentation/devices.txt:
  2 char        Pseudo-TTY masters
                  0 = /dev/ptyp0        First PTY master
                  1 = /dev/ptyp1        Second PTY master
                    ...
                255 = /dev/ptyef        256th PTY master

                Pseudo-tty's are named as follows:
                * Masters are "pty", slaves are "tty";
                * the fourth letter is one of pqrstuvwxyzabcde indicating
                  the 1st through 16th series of 16 pseudo-ttys each, and
                * the fifth letter is one of 0123456789abcdef indicating
                  the position within the series.

Choose some pairs !


--
73 Gérard F6FGZ
-
To unsubscribe from this list: send the line "unsubscribe linux-hams" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Re: Trying to get Ax25 running.

[Dennis Boone]

 > I correct your memory ;-)
 > kissattach /dev/ttyz0 hfport 44.135.96.242
 > kissattach /dev/ttyz1 vhfport 44.135.96.243

Ooops.  Gérard is right, my actual config does say ttyz0 in the
kissattach statements.  So much for memory. :-)

De
-
To unsubscribe from this list: send the line "unsubscribe linux-hams" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Re: Trying to get Ax25 running.

[Tomi Manninen]

On Fri, 2004-10-15 at 20:59, Gérard / F6FGZ wrote:

> >         mkiss -c -l -s 19200 /dev/ttyS0 /dev/ptyz0 /dev/ptyz1
> >         kissattach /dev/ptyz0 hfport 44.135.96.242
> >         kissattach /dev/ptyz0 vhfport 44.135.96.243
> 
> I correct your memory ;-)
> kissattach /dev/ttyz0 hfport 44.135.96.242
> kissattach /dev/ttyz1 vhfport 44.135.96.243
> 
> It is important to have ptyxx from one side corresponding to ttyxx on the other
> side.

True. Additionally I would recommend kissattaching the master side
(ptyxx) and putting mkiss on the slave side (ttyxx). Then, as the
master side always needs to be opened first, you need to first do 
kissattach and mkiss after that.

-- 
Tomi Manninen / OH2BNS / KP20ME04

-
To unsubscribe from this list: send the line "unsubscribe linux-hams" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Re: Trying to get Ax25 running.

[Pontus Falk]

Hi!

> True. Additionally I would recommend kissattaching the master side
> (ptyxx) and putting mkiss on the slave side (ttyxx). Then, as the
> master side always needs to be opened first, you need to first do
> kissattach and mkiss after that.

Can you explain why you recommend to put kissattach in the master side and mkiss on
the slave side?

73's de Pontus/SMØRUX

-
To unsubscribe from this list: send the line "unsubscribe linux-hams" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Re: Trying to get Ax25 running.

[Tomi Manninen]

On Fri, 2004-10-15 at 21:33, Pontus Falk wrote:

> > True. Additionally I would recommend kissattaching the master side
> > (ptyxx) and putting mkiss on the slave side (ttyxx). Then, as the
> > master side always needs to be opened first, you need to first do
> > kissattach and mkiss after that.
> 
> Can you explain why you recommend to put kissattach in the master side and mkiss on
> the slave side?

It's because of the way pseudo-tty's work. If the process on the slave
side dies for any reason, the master side is unaffected. If the
process on the master side dies, the slave side dies too. So, you want 
to put the more stable process on the master side.

It's next to impossible for kissattach to die due to any error
(unless there is a problem with the kernel and then you are screwed 
anyway). So therefore I'd put it on the master side. Also if you think 
of maintenance work, it's more probable that you need to restart
the mkiss process if you do any rearranging of reconfiguring in
your system. Again, that is a reason to put mkiss on the slave side.

That said, this is not something that will impact the performance
of your system. It can make handling certain error and configuring
situations easier. On the other hand, if one uses the windows
method of system administartion, ie. reboot after any change, then
it doesn't make much difference one way or the other... :)

-- 
Tomi Manninen / OH2BNS / KP20ME04

Re: Trying to get Ax25 running.

[Curt, WE7U]

On Fri, 15 Oct 2004, Tomi Manninen wrote:

> It's because of the way pseudo-tty's work. If the process on the slave
> side dies for any reason, the master side is unaffected. If the
> process on the master side dies, the slave side dies too. So, you want
> to put the more stable process on the master side.
>
> It's next to impossible for kissattach to die due to any error
> (unless there is a problem with the kernel and then you are screwed
> anyway). So therefore I'd put it on the master side. Also if you think
> of maintenance work, it's more probable that you need to restart
> the mkiss process if you do any rearranging of reconfiguring in
> your system. Again, that is a reason to put mkiss on the slave side.
>
> That said, this is not something that will impact the performance
> of your system. It can make handling certain error and configuring
> situations easier. On the other hand, if one uses the windows
> method of system administartion, ie. reboot after any change, then
> it doesn't make much difference one way or the other... :)

You should get the above text put into the AX.25-HOWTO.  That's a
useful tidbit that I had never heard before.  I would imagine that
would be quite useful.

--
Curt, WE7U			         http://www.eskimo.com/~archer
"Lotto:    A tax on people who are bad at math." -- unknown
"Windows:  Microsoft's tax on computer illiterates." -- WE7U
"The world DOES revolve around me:  I picked the coordinate system!"

Re: Trying to get Ax25 running.

[Chuck Hast]

I am not interested in doing multiple TNC's all I want is the crc part,
Do I still have to use the master slave part? Looks like the AX25-
config program does not take into account such things.

Here is a listing from a lsmod on my system
kp4djt@rf-tool:~> lsmod
Module                  Size  Used by
mkiss                  10020  0
ax25                   58476  1 mkiss


This is the ax25-up script file that the ax25-config program created.

#!/bin/bash
# Startkiss0
# Firmware-TNCs in den KISS-Modus schalten
#stty 19200 < /dev/ttyS0
#echo -e "\r\033@K1\r" > /dev/ttyS0
#sleep 3
#
# KISS-Modul einbinden
modprobe ax25; modprobe kiss; modprobe mkiss
#
# KISS-Ger� an /dev/ttyS0 als Port kiss0 anbinden
/usr/sbin/kissattach -i 44.1.1.1 /dev/ttyS0 kiss0
# Parameter einstellen: P=128, W=10, TX-Delay=100
/usr/sbin/kissparms -p kiss0 -r 128 -s 10 -l 10 -t 100
# Endkiss0
# StartARNM
#
# Logins von au�n erm�lichen
/usr/sbin/ax25d &
echo $! > /var/run/ax25d.pid
#
# Start AX25 routing daemon
/usr/sbin/ax25rtd &
echo $! > /var/run/ax25rtd.pid
insmod netrom
nrattach -i 44.1.1.1 nr0
#
# Monitor auf Terminal 11 starten
/usr/bin/listen -artc > /dev/tty11 &
echo $! > /var/run/listen.pid
# EndARNM
-
To unsubscribe from this list: send the line "unsubscribe linux-hams" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Re: Trying to get Ax25 running.

[Chuck Hast]

> # Monitor auf Terminal 11 starten
> /usr/bin/listen -artc > /dev/tty11 &
> echo $! > /var/run/listen.pid
> # EndARNM
> 

This may be where I was having a issue, it is bringing up listen on tty 11.
(console 11) once I octothorped it I am even able run run call in a x session.

Now to go in and give the stuff the proper permissions so I do not have to
be root to run it.



-- 
Chuck Hast 
To paraphrase my flight instructor;
"the only dumb question is the one you DID NOT ask resulting in my going
out and having to identify your bits and pieces in the midst of torn
and twisted metal."

Re: Trying to get Ax25 running.

[Chuck Hast]

Here is what I ended up with when I commented out the listen console.
This appearst to have cleared up the locking up of the machine, I have
not had it lock up since.

Now if I can just get the BPQKISS part running (CRC kiss)


#!/bin/bash
# Startkiss0
# Firmware-TNCs in den KISS-Modus schalten
#stty 19200 < /dev/ttyUSB0
echo -e "\r\033@K1\r" > /dev/ttyUSB0
#sleep 3
#
# KISS-Modul einbinden
modprobe ax25; modprobe kiss; modprobe mkiss
#
# KISS-Ger344t an /dev/ttyUSB0 als Port kiss0 anbinden
/usr/sbin/kissattach -i 44.1.1.1 /dev/ttyUSB0 kiss0
# Parameter einstellen: P=254, W=10, TX-Delay=100
/usr/sbin/kissparms -p kiss0 -r 254 -s 1 -l 10 -t 100
# Endkiss0
# StartARNM
#
# Logins von au337en erm366glichen
#/usr/sbin/ax25d &
#echo $! > /var/run/ax25d.pid
#
# Start AX25 routing daemon
#/usr/sbin/ax25rtd &

#echo $! > /var/run/ax25rtd.pid
#insmod netrom
#nrattach -i 44.1.1.1 nr0
#
# Monitor auf Terminal 11 starten
#sleep 2
#/usr/bin/listen -artc > /dev/tty11 &
#echo $! > /var/run/listen.pid
# EndARNM

Re: Trying to get Ax25 running.

[Dennis Boone]

 > Now if I can just get the BPQKISS part running (CRC kiss)
 > 
 > echo -e "\r\033@K1\r" > /dev/ttyUSB0
 > modprobe ax25; modprobe kiss; modprobe mkiss
 > /usr/sbin/kissattach -i 44.1.1.1 /dev/ttyUSB0 kiss0
 > /usr/sbin/kissparms -p kiss0 -r 254 -s 1 -l 10 -t 100

If I understand correctly, only the mkiss utility speaks frame
check on kiss ports.  Even if you don't need multiple ports, you
need to run mkiss to get your checksums.  That would mean doing
the following with the above, following Tomi's suggestion from
earlier:

	echo -e "\r\033@K1\r" > /dev/ttyUSB0
	modprobe ax25; modprobe kiss; modprobe mkiss
	/usr/sbin/kissattach -i 44.1.1.1 /dev/ptyz0 kiss0
	/usr/sbin/kissparms -p kiss0 -r 254 -s 1 -l 10 -t 100
	/usr/sbin/mkiss -c -l /dev/ttyUSB0 /dev/ttyz0

You may need the "-s baudrate" option to mkiss as well.

De

Re: Trying to get Ax25 running.

[Chuck Hast]

On Fri, 15 Oct 2004 21:28:46 -0400, Dennis Boone <drb@msu.edu> wrote:
>  > Now if I can just get the BPQKISS part running (CRC kiss)
>  >
>  > echo -e "\r\033@K1\r" > /dev/ttyUSB0
>  > modprobe ax25; modprobe kiss; modprobe mkiss
>  > /usr/sbin/kissattach -i 44.1.1.1 /dev/ttyUSB0 kiss0
>  > /usr/sbin/kissparms -p kiss0 -r 254 -s 1 -l 10 -t 100
> 
> If I understand correctly, only the mkiss utility speaks frame
> check on kiss ports.  Even if you don't need multiple ports, you
> need to run mkiss to get your checksums.  That would mean doing
> the following with the above, following Tomi's suggestion from
> earlier:
> 
>         echo -e "\r\033@K1\r" > /dev/ttyUSB0
>         modprobe ax25; modprobe kiss; modprobe mkiss
>         /usr/sbin/kissattach -i 44.1.1.1 /dev/ptyz0 kiss0
>         /usr/sbin/kissparms -p kiss0 -r 254 -s 1 -l 10 -t 100
>         /usr/sbin/mkiss -c -l /dev/ttyUSB0 /dev/ttyz0
> 
> You may need the "-s baudrate" option to mkiss as well.
> 

You were right. That worked. I am noticing one thing, when I establish
a connection that goes through a digi or two, it looks like the
frame counters get screwed up not sure what is going on, but
what I see is the I frame is sent, the far end ask for a repeate
and off it goes again, it looks ike the far end is not getting the
right frame number. If I send a new line again, the previous
line is sent on to the target.

Re: Trying to get Ax25 running.

[Dennis Boone]

> /usr/sbin/kissparms -p kiss0 -r 254 -s 1 -l 10 -t 100

 > You were right. That worked. I am noticing one thing, when I establish
 > a connection that goes through a digi or two, it looks like the
 > frame counters get screwed up not sure what is going on, but what I
 > see is the I frame is sent, the far end ask for a repeate and off it
 > goes again, it looks ike the far end is not getting the right frame
 > number. If I send a new line again, the previous line is sent on to
 > the target.

I've been thinking about your kissparms statement, and wonder if it's
part of the problem.

Unless this is a digi, the "-r 254 -s 1" timing parameters are far too
aggressive and should probably be removed or changed.  (-s 1 isn't even
valid according to my kissparms manpage, which says it needs to be in
even 10's.)  Even if it is a digi, "-r 128 -s 10" is probably closer to
sane, unless your local network gurus have something else worked out.

The "-t 100" means your radio needs to be able to turn around from
receive to transmit in 100 ms.  That's pretty fast for most rigs,
both in terms of your transmitter, and in terms of the receivers at
the other end.  I've never had a rig which would run faster than 150,
and many have been 200 or slower.  You might want to try "-t 200".
What kind of radio is involved?

The cheap way to test all of this would be to just comment out kissparms,
reboot, and see how the behavior changes.  Defaults are something like
"-r 63 -s 10 -t 300".

De

Re: Trying to get Ax25 running.

[Tomi Manninen]

On Sat, 2004-10-16 at 04:28, Dennis Boone wrote:

> 	echo -e "\r\033@K1\r" > /dev/ttyUSB0
> 	modprobe ax25; modprobe kiss; modprobe mkiss
> 	/usr/sbin/kissattach -i 44.1.1.1 /dev/ptyz0 kiss0
> 	/usr/sbin/kissparms -p kiss0 -r 254 -s 1 -l 10 -t 100
> 	/usr/sbin/mkiss -c -l /dev/ttyUSB0 /dev/ttyz0

Kissparms should be called *after* mkiss. Otherwise the commands
won't reach the TNC...

-- 
Tomi Manninen / OH2BNS / KP20ME04

Re: Trying to get Ax25 running.

[Chuck Hast]

On Sat, 16 Oct 2004 15:45:27 +0300, Tomi Manninen <oh2bns@sral.fi> wrote:
> On Sat, 2004-10-16 at 04:28, Dennis Boone wrote:
> 
> >       echo -e "\r\033@K1\r" > /dev/ttyUSB0
> >       modprobe ax25; modprobe kiss; modprobe mkiss
> >       /usr/sbin/kissattach -i 44.1.1.1 /dev/ptyz0 kiss0
> >       /usr/sbin/kissparms -p kiss0 -r 254 -s 1 -l 10 -t 100
> >       /usr/sbin/mkiss -c -l /dev/ttyUSB0 /dev/ttyz0
> 
> Kissparms should be called *after* mkiss. Otherwise the commands
> won't reach the TNC...
> 

I have done that, but I still have a problem. When I run the ax25-up file that
is set up for for the mkiss line, it starts up ok the first time, but
when I run the
ax25-down file that ax25-config generates it does not shut down a mkiss entry
if I do a ps -e I see a PID and mkiss if I do a ps -r I see that it is
the attachment
to the ttyz0 port that does not go away. If I go back to the original
kiss set up
the ax25-down script tears it down just fine. There is probably a lot
of stuff that
I do not need in that script right now that is just clouding things for me.

Do you have a recommendation for a short script that will shut down the ax25
stuff?

Re: Trying to get Ax25 running.

[Tomi Manninen]

On Sat, 2004-10-16 at 16:16, Chuck Hast wrote:

> I have done that, but I still have a problem. When I run the ax25-up file that
> is set up for for the mkiss line, it starts up ok the first time, but
> when I run the
> ax25-down file that ax25-config generates it does not shut down a mkiss entry

Hmm.. I guess the simple solution would be to do a "killall mkiss" 
somewhere near the top of the script. It should be placed before the 
kissattach processes are killed.

> if I do a ps -e I see a PID and mkiss if I do a ps -r I see that it is
> the attachment
> to the ttyz0 port that does not go away. 

This makes me wonder if the pty behaviour has changed along the way and
if my suggestion about the order of kissattach/mkiss is valid anymore...
Oh well... :)

-- 
Tomi Manninen / OH2BNS / KP20ME04

Re: Trying to get Ax25 running.

[Chuck Hast]

On Sat, 16 Oct 2004 16:52:02 +0300, Tomi Manninen <oh2bns@sral.fi> wrote:
> On Sat, 2004-10-16 at 16:16, Chuck Hast wrote:
> 
> > I have done that, but I still have a problem. When I run the ax25-up file that
> > is set up for for the mkiss line, it starts up ok the first time, but
> > when I run the
> > ax25-down file that ax25-config generates it does not shut down a mkiss entry
> 
> Hmm.. I guess the simple solution would be to do a "killall mkiss"
> somewhere near the top of the script. It should be placed before the
> kissattach processes are killed.
> 
> > if I do a ps -e I see a PID and mkiss if I do a ps -r I see that it is
> > the attachment
> > to the ttyz0 port that does not go away.
> 
> This makes me wonder if the pty behaviour has changed along the way and
> if my suggestion about the order of kissattach/mkiss is valid anymore...
> Oh well... :)
> 
> 
> 

here is the ax25-down script that is supposed to kill it all.
I am not using any of this but just the AX25 stuff. I run listen
manually right now.
I am just trying to sort through it all.

-----------------------------------------------------------------
#!/bin/bash
#
# Einen eventuell laufenden ax25d beenden
if [ -s /var/run/ax25d.pid ]; then
  tmp="`cat /proc/\`cat /var/run/ax25d.pid\`/cmdline`"
  if [ "$tmp" == "/usr/sbin/ax25d" ]; then
    kill `cat /var/run/ax25d.pid`
  else
    echo "stale \"ax25d\" pid-file, deleting..."
  fi 
  rm -f /var/run/ax25d.pid
fi
# Monitor beenden
if [ -s /var/run/listen.pid ]; then
  tmp="`cat /proc/\`cat /var/run/listen.pid\`/cmdline`"
  if [ "$tmp" = "/usr/bin/listen" ]; then
    kill `cat /var/run/listen.pid`
  else
    echo "stale \"listen\" pid-file, deleting..."
  fi
  rm -f /var/run/listen.pid
fi
echo "$(ls /proc/sys/net/ax25)" > /tmp/ax25-config.tmp
read Auswahl < /tmp/ax25-config.tmp
i=0
while [ "$Auswahl" != "" ]
do
let i=i+1
awk ' NR == '$i' { print $1 }' /tmp/ax25-config.tmp > /tmp/ax25-config-tmp
read Auswahl < /tmp/ax25-config-tmp
if [ "$Auswahl" != "" ]; then 
ifconfig "$Auswahl" down
fi
done
# Startkiss0
killproc -KILL /usr/sbin/kissattach > /dev/null
modprobe -r ax25; modprobe -r kiss; modprobe -r mkiss > /dev/null
# Endkiss0
--------------------------------------------------------------


-- 
Chuck Hast 
To paraphrase my flight instructor;
"the only dumb question is the one you DID NOT ask resulting in my going
out and having to identify your bits and pieces in the midst of torn
and twisted metal."