Problems using MKISS

Problems using MKISS

[Stephen Brown Jr]

I am trying to share a KISS tnc on a serial port for APRS and MKISS
seems to be the way to do it, but I can't get it work for whatever
reason. I have two machines, Im using AXIP to carry traffic back and
forth between them. Here is my setup:

Debian linux "Sarge" 3.1 using stock 2.4 kernel (this the box the TNC
is located on)
KISS mode TNC on /dev/ttyS4, AX25 and MKISS modules loaded and working
Ran mkiss -s 9600 /dev/ttyS4 /dev/ptyp0, then ran kissattach
/dev/ttyp0 aprs 192.168.1.6, port successfully binds to ax0

I have ax25ipd setup to go to my other machine using udp, port 415. I
am able to pass AX.25 traffic between both machines no problem, but
when I start up ax25ipd on the box with the tnc on it, I got this:

fetching tty device parameters: Invalid argument

I was following section 6.1.1.1 of this as a guide in setting this up
(the MKISS section):

http://www.faqs.org/docs/Linux-HOWTO/AX25-HOWTO.html

Should this work as intended? In the end I want a bidrectional AXIP
link between the two machines that will share the TNC.

Stephen
N1VLV

Re: Problems using MKISS

[Brett Mueller]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Stephen Brown Jr wrote the following on 03/11/2007 17:05:
> I am trying to share a KISS tnc on a serial port for APRS and MKISS
> seems to be the way to do it, but I can't get it work for whatever
> reason. I have two machines, Im using AXIP to carry traffic back and
> forth between them. Here is my setup:
> 
> Debian linux "Sarge" 3.1 using stock 2.4 kernel (this the box the TNC
> is located on)
> KISS mode TNC on /dev/ttyS4, AX25 and MKISS modules loaded and working
> Ran mkiss -s 9600 /dev/ttyS4 /dev/ptyp0, then ran kissattach
> /dev/ttyp0 aprs 192.168.1.6, port successfully binds to ax0

Is your TNC a single or dual port unit?  Maybe it doesn't matter, but it
looks like your mkiss command is lacking a second pseudo-tty specification.
If your TNC is single port, perhaps using "rxecho" would work better for your
situation than mkiss?  I have several apps sharing a TNC on my BBS; only one
of them is actually attached to the TNC, but the others talk AX.25 "directly"
through the TNC via rxecho on the appropriate shared interfaces.

Hope this helps somehow...

73,

Brett, WA7V


-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)

iD8DBQFF+FZt+/Ps1x4JxWYRAlsaAKCqUAcQK1wV1+viSNeulgv5yr6WTgCeKVBd
PYa51okbm3dcWlSR3VDTEfk=
=Ld5g
-----END PGP SIGNATURE-----

Re: Problems using MKISS

[Stephen Brown Jr]

I am using a single port TNC (tnc-x) and maybe mkiss is not the right
tool for the job? I have tried rxecho, but that seemed to have a
"ping-pong" effect in that I was transmitting and receiving everything
back and forth between both ports, it's possible I set it up wrong.

What I am trying to accomplish is this, and I have not been succesfull
at it yet:

I have two TNC-X KISS mode TNC's, one for regular packet, one for APRS.

I run javaaprssrvr for Igate software, will soon run digi_ned for
digipeating/telemetry, and Xastir as a client on a seperate machine. I
would like to share all 3 apps with one TNC, and I will be connecting
Xastir to the box via an AXIP interface.

On the packet side, I will be running FBB, (X)net, and eventually jNOS
and whatever else I decide to experiment with later on :) I want to do
the same thing, share the TNC with a host of apps.

tnx and 73's
Stephen
K1LNX

On 3/14/07, Brett Mueller <wa7v@wa7v.com> wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> Stephen Brown Jr wrote the following on 03/11/2007 17:05:
> > I am trying to share a KISS tnc on a serial port for APRS and MKISS
> > seems to be the way to do it, but I can't get it work for whatever
> > reason. I have two machines, Im using AXIP to carry traffic back and
> > forth between them. Here is my setup:
> >
> > Debian linux "Sarge" 3.1 using stock 2.4 kernel (this the box the TNC
> > is located on)
> > KISS mode TNC on /dev/ttyS4, AX25 and MKISS modules loaded and working
> > Ran mkiss -s 9600 /dev/ttyS4 /dev/ptyp0, then ran kissattach
> > /dev/ttyp0 aprs 192.168.1.6, port successfully binds to ax0
>
> Is your TNC a single or dual port unit?  Maybe it doesn't matter, but it
> looks like your mkiss command is lacking a second pseudo-tty specification.
> If your TNC is single port, perhaps using "rxecho" would work better for your
> situation than mkiss?  I have several apps sharing a TNC on my BBS; only one
> of them is actually attached to the TNC, but the others talk AX.25 "directly"
> through the TNC via rxecho on the appropriate shared interfaces.
>
> Hope this helps somehow...
>
> 73,
>
> Brett, WA7V
>
>
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.6 (GNU/Linux)
>
> iD8DBQFF+FZt+/Ps1x4JxWYRAlsaAKCqUAcQK1wV1+viSNeulgv5yr6WTgCeKVBd
> PYa51okbm3dcWlSR3VDTEfk=
> =Ld5g
> -----END PGP SIGNATURE-----
> -
> 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: Problems using MKISS

[Bernard Pidoux]

Stephen Brown Jr wrote:
> I am using a single port TNC (tnc-x) and maybe mkiss is not the right
> tool for the job? I have tried rxecho, but that seemed to have a
> "ping-pong" effect in that I was transmitting and receiving everything
> back and forth between both ports, it's possible I set it up wrong.
> 
> What I am trying to accomplish is this, and I have not been succesfull
> at it yet:
> 
> I have two TNC-X KISS mode TNC's, one for regular packet, one for APRS.
> 
> I run javaaprssrvr for Igate software, will soon run digi_ned for
> digipeating/telemetry, and Xastir as a client on a seperate machine. I
> would like to share all 3 apps with one TNC, and I will be connecting
> Xastir to the box via an AXIP interface.
> 
> On the packet side, I will be running FBB, (X)net, and eventually jNOS
> and whatever else I decide to experiment with later on :) I want to do
> the same thing, share the TNC with a host of apps.
> 
> tnx and 73's
> Stephen
> K1LNX
> 
> On 3/14/07, Brett Mueller <wa7v@wa7v.com> wrote:
> Stephen Brown Jr wrote the following on 03/11/2007 17:05:
>> I am trying to share a KISS tnc on a serial port for APRS and MKISS
>> seems to be the way to do it, but I can't get it work for whatever
>> reason. I have two machines, Im using AXIP to carry traffic back and
>> forth between them. Here is my setup:
> 
>> Debian linux "Sarge" 3.1 using stock 2.4 kernel (this the box the TNC
>> is located on)
>> KISS mode TNC on /dev/ttyS4, AX25 and MKISS modules loaded and working
>> Ran mkiss -s 9600 /dev/ttyS4 /dev/ptyp0, then ran kissattach
>> /dev/ttyp0 aprs 192.168.1.6, port successfully binds to ax0
> 
> Is your TNC a single or dual port unit?  Maybe it doesn't matter, but it
> looks like your mkiss command is lacking a second pseudo-tty
> specification.
> If your TNC is single port, perhaps using "rxecho" would work better
> for your
> situation than mkiss?  I have several apps sharing a TNC on my BBS;
> only one
> of them is actually attached to the TNC, but the others talk AX.25
> "directly"
> through the TNC via rxecho on the appropriate shared interfaces.
> 
> Hope this helps somehow...
> 
> 73,
> 
> Brett, WA7V
> 

Hi,

You probably need to kissattach another pseudo TTY port (say port axip
to be declared into /etc/ax25/axports)

kissattach /dev/ptyq0 axip 192.168.1.6

and configure the other side of the tunnel /dev/ttyq0 in AXIP config file.

Actually I don't use axip itself but this is the way I did it using ax25ipd.

73 de Bernard, f6bvp

Re: Problems using MKISS

[Wilson G. Hein]

I could be wrong, but I think for a single port TNC there is no need for
mkiss. IIRC you would use just kissattach to control a single port kiss
tnc.


73 Willie

On Wed, 2007-03-14 at 16:23 -0400, Stephen Brown Jr wrote:
> I am using a single port TNC (tnc-x) and maybe mkiss is not the right
> tool for the job? I have tried rxecho, but that seemed to have a
> "ping-pong" effect in that I was transmitting and receiving everything
> back and forth between both ports, it's possible I set it up wrong.
> 
> What I am trying to accomplish is this, and I have not been succesfull
> at it yet:
> 
> I have two TNC-X KISS mode TNC's, one for regular packet, one for APRS.
> 
> I run javaaprssrvr for Igate software, will soon run digi_ned for
> digipeating/telemetry, and Xastir as a client on a seperate machine. I
> would like to share all 3 apps with one TNC, and I will be connecting
> Xastir to the box via an AXIP interface.
> 
> On the packet side, I will be running FBB, (X)net, and eventually jNOS
> and whatever else I decide to experiment with later on :) I want to do
> the same thing, share the TNC with a host of apps.
> 
> tnx and 73's
> Stephen
> K1LNX
> 
> On 3/14/07, Brett Mueller <wa7v@wa7v.com> wrote:
> > -----BEGIN PGP SIGNED MESSAGE-----
> > Hash: SHA1
> >
> > Stephen Brown Jr wrote the following on 03/11/2007 17:05:
> > > I am trying to share a KISS tnc on a serial port for APRS and MKISS
> > > seems to be the way to do it, but I can't get it work for whatever
> > > reason. I have two machines, Im using AXIP to carry traffic back and
> > > forth between them. Here is my setup:
> > >
> > > Debian linux "Sarge" 3.1 using stock 2.4 kernel (this the box the TNC
> > > is located on)
> > > KISS mode TNC on /dev/ttyS4, AX25 and MKISS modules loaded and working
> > > Ran mkiss -s 9600 /dev/ttyS4 /dev/ptyp0, then ran kissattach
> > > /dev/ttyp0 aprs 192.168.1.6, port successfully binds to ax0
> >
> > Is your TNC a single or dual port unit?  Maybe it doesn't matter, but it
> > looks like your mkiss command is lacking a second pseudo-tty specification.
> > If your TNC is single port, perhaps using "rxecho" would work better for your
> > situation than mkiss?  I have several apps sharing a TNC on my BBS; only one
> > of them is actually attached to the TNC, but the others talk AX.25 "directly"
> > through the TNC via rxecho on the appropriate shared interfaces.
> >
> > Hope this helps somehow...
> >
> > 73,
> >
> > Brett, WA7V
> >
> >
> > -----BEGIN PGP SIGNATURE-----
> > Version: GnuPG v1.4.6 (GNU/Linux)
> >
> > iD8DBQFF+FZt+/Ps1x4JxWYRAlsaAKCqUAcQK1wV1+viSNeulgv5yr6WTgCeKVBd
> > PYa51okbm3dcWlSR3VDTEfk=
> > =Ld5g
> > -----END PGP SIGNATURE-----
> > -
> > 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
> >
> -
> 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
-- 
Wilson G. Hein <wilson.hein@verizon.net>

Re: Problems using MKISS

[Stephen Brown Jr]

How would I get more than one app to talk to a single tty, ttyS4 in my
case, this is the port the TNC is connected to. This is the part of
the puzzle I seem to be missing......

73's
Stephen
K1LNX


On 3/15/07, Wilson G. Hein <wilson.hein@verizon.net> wrote:
> I could be wrong, but I think for a single port TNC there is no need for
> mkiss. IIRC you would use just kissattach to control a single port kiss
> tnc.
>
>
> 73 Willie
>
> On Wed, 2007-03-14 at 16:23 -0400, Stephen Brown Jr wrote:
> > I am using a single port TNC (tnc-x) and maybe mkiss is not the right
> > tool for the job? I have tried rxecho, but that seemed to have a
> > "ping-pong" effect in that I was transmitting and receiving everything
> > back and forth between both ports, it's possible I set it up wrong.
> >
> > What I am trying to accomplish is this, and I have not been succesfull
> > at it yet:
> >
> > I have two TNC-X KISS mode TNC's, one for regular packet, one for APRS.
> >
> > I run javaaprssrvr for Igate software, will soon run digi_ned for
> > digipeating/telemetry, and Xastir as a client on a seperate machine. I
> > would like to share all 3 apps with one TNC, and I will be connecting
> > Xastir to the box via an AXIP interface.
> >
> > On the packet side, I will be running FBB, (X)net, and eventually jNOS
> > and whatever else I decide to experiment with later on :) I want to do
> > the same thing, share the TNC with a host of apps.
> >
> > tnx and 73's
> > Stephen
> > K1LNX
> >
> > On 3/14/07, Brett Mueller <wa7v@wa7v.com> wrote:
> > > -----BEGIN PGP SIGNED MESSAGE-----
> > > Hash: SHA1
> > >
> > > Stephen Brown Jr wrote the following on 03/11/2007 17:05:
> > > > I am trying to share a KISS tnc on a serial port for APRS and MKISS
> > > > seems to be the way to do it, but I can't get it work for whatever
> > > > reason. I have two machines, Im using AXIP to carry traffic back and
> > > > forth between them. Here is my setup:
> > > >
> > > > Debian linux "Sarge" 3.1 using stock 2.4 kernel (this the box the TNC
> > > > is located on)
> > > > KISS mode TNC on /dev/ttyS4, AX25 and MKISS modules loaded and working
> > > > Ran mkiss -s 9600 /dev/ttyS4 /dev/ptyp0, then ran kissattach
> > > > /dev/ttyp0 aprs 192.168.1.6, port successfully binds to ax0
> > >
> > > Is your TNC a single or dual port unit?  Maybe it doesn't matter, but it
> > > looks like your mkiss command is lacking a second pseudo-tty specification.
> > > If your TNC is single port, perhaps using "rxecho" would work better for your
> > > situation than mkiss?  I have several apps sharing a TNC on my BBS; only one
> > > of them is actually attached to the TNC, but the others talk AX.25 "directly"
> > > through the TNC via rxecho on the appropriate shared interfaces.
> > >
> > > Hope this helps somehow...
> > >
> > > 73,
> > >
> > > Brett, WA7V
> > >
> > >
> > > -----BEGIN PGP SIGNATURE-----
> > > Version: GnuPG v1.4.6 (GNU/Linux)
> > >
> > > iD8DBQFF+FZt+/Ps1x4JxWYRAlsaAKCqUAcQK1wV1+viSNeulgv5yr6WTgCeKVBd
> > > PYa51okbm3dcWlSR3VDTEfk=
> > > =Ld5g
> > > -----END PGP SIGNATURE-----
> > > -
> > > 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
> > >
> > -
> > 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
> --
> Wilson G. Hein <wilson.hein@verizon.net>
>
> -
> 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: Problems using MKISS

[Chuck Hast]

On 3/15/07, Stephen Brown Jr <stephen.brown75@gmail.com> wrote:
> How would I get more than one app to talk to a single tty, ttyS4 in my
> case, this is the port the TNC is connected to. This is the part of
> the puzzle I seem to be missing......
>
I believe that this is the function of ax25d, you would use ax25d.conf to
set up the different apps that are talking to that port.

Here is a sample ax25d.conf file:




# /etc/ax25/ax25d.conf
#
<netrom>
parameters 1   10 * * * * *
NOCALL     * * * * * * L
default    * * * * * * *    root /usr/local/sbin/fpacnode fpacnode -q %S
#
#
#[djt14 via sp0 ]
#parameters 1   10 * * * * *
#NOCALL     * * * * * * *
#default    * * * * * * *    root /usr/sbin/fpacnode fpacnode
#

# StartRose
#{kp4djt-9 via rose}
#default    * * * * * * *       root /usr/sbin/node node 6pac0
# Endrose
#
# Start6pac8
[kp4djt-15 via 8 ]
NOCALL     * * * * * *  L
default    * * * * * *  -   root /usr/sbin/axspawn axspawn -w %u
# End6pac8
#
# Start6pac0
[kp4djt-0 via 0 ]
NOCALL     * * * * * *  L
default    * * * * * *  -   root /usr/sbin/axspawn axspawn -w %u
# Endkiss0
#
# Start axip
[kp4djt-12 via 9 ]
NOCALL     * * * * * *  L
default    * * * * * *  -    root /usr/sbin/axspawn axspawn -w %u
# End axip
#
# KP4DJT-5 TelPac
#
[KP4DJT-10 via 9 ]
NOCALL     * * * * * * L
default    * * * * * * -  root /usr/sbin/telpac_node telpac_node -q %S
# End TelPac Node
#
(END)

You really need to read the ax25 how-to, this part of it has not changed
that much.

In my case I am running a FPAC switch and FPAC does most of this so the
ax25d is not used, we multiplex several services on a single TNC, the switch,
the TelPac app, others have BBS on a port, each one has a different call or
alias for access, but all are on the same port/tty.

-- 
Chuck Hast  -- KP4DJT --
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: Problems using MKISS

[Stephen Brown Jr]

Ok, that will work good for regular connected mode packet, how would I
set it up for APRS? I have two apps, both of which will run in the
background and a third app(xastir) connected via an AXIP link from
another box.

I'm getting closer........

On 3/15/07, Chuck Hast <wchast@gmail.com> wrote:
> On 3/15/07, Stephen Brown Jr <stephen.brown75@gmail.com> wrote:
> > How would I get more than one app to talk to a single tty, ttyS4 in my
> > case, this is the port the TNC is connected to. This is the part of
> > the puzzle I seem to be missing......
> >
> I believe that this is the function of ax25d, you would use ax25d.conf to
> set up the different apps that are talking to that port.
>
> Here is a sample ax25d.conf file:
>
>
>
>
> # /etc/ax25/ax25d.conf
> #
> <netrom>
> parameters 1   10 * * * * *
> NOCALL     * * * * * * L
> default    * * * * * * *    root /usr/local/sbin/fpacnode fpacnode -q %S
> #
> #
> #[djt14 via sp0 ]
> #parameters 1   10 * * * * *
> #NOCALL     * * * * * * *
> #default    * * * * * * *    root /usr/sbin/fpacnode fpacnode
> #
>
> # StartRose
> #{kp4djt-9 via rose}
> #default    * * * * * * *       root /usr/sbin/node node 6pac0
> # Endrose
> #
> # Start6pac8
> [kp4djt-15 via 8 ]
> NOCALL     * * * * * *  L
> default    * * * * * *  -   root /usr/sbin/axspawn axspawn -w %u
> # End6pac8
> #
> # Start6pac0
> [kp4djt-0 via 0 ]
> NOCALL     * * * * * *  L
> default    * * * * * *  -   root /usr/sbin/axspawn axspawn -w %u
> # Endkiss0
> #
> # Start axip
> [kp4djt-12 via 9 ]
> NOCALL     * * * * * *  L
> default    * * * * * *  -    root /usr/sbin/axspawn axspawn -w %u
> # End axip
> #
> # KP4DJT-5 TelPac
> #
> [KP4DJT-10 via 9 ]
> NOCALL     * * * * * * L
> default    * * * * * * -  root /usr/sbin/telpac_node telpac_node -q %S
> # End TelPac Node
> #
> (END)
>
> You really need to read the ax25 how-to, this part of it has not changed
> that much.
>
> In my case I am running a FPAC switch and FPAC does most of this so the
> ax25d is not used, we multiplex several services on a single TNC, the switch,
> the TelPac app, others have BBS on a port, each one has a different call or
> alias for access, but all are on the same port/tty.
>
> --
> Chuck Hast  -- KP4DJT --
> 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: Problems using MKISS

[Chuck Hast]

On 3/15/07, Stephen Brown Jr <stephen.brown75@gmail.com> wrote:
> Ok, that will work good for regular connected mode packet, how would I
> set it up for APRS? I have two apps, both of which will run in the
> background and a third app(xastir) connected via an AXIP link from
> another box.
>
> I'm getting closer........
I was looking at Xastir docs and it appears that it will work with the ax25
stack. But first thing you want to do is make sure that you have the stack
up and running, once you think it is working try to make a call out that port
or use Listen to monitor the port and send some ax25 data to the TNC, if
Listen shows it then the port is receiving, same thing, if you can use call
and establish a connection with a remote system, then your ax25 stack is
working, that done you can then proceed to the integration of Xastir to the
system. I have not done that so you will need to talk to some of the Xastir
people.



-- 
Chuck Hast  -- KP4DJT --
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: Problems using MKISS

[Curt, WE7U]

On Thu, 15 Mar 2007, Chuck Hast wrote:

> I was looking at Xastir docs and it appears that it will work with the ax25
> stack.

Yes.  It'll work with the AX.25 stack -or- with the "soundmodem"
driver set up as a serial KISS TNC -or- with a KISS TNC on a direct
serial port -or- with a non-KISS TNC on a direct serial port.

Of course the only way to share TNC's with other apps is to use the
AX.25 stack.

Xastir has a "View->Incoming Data" dialog so you can see whether
packets are coming in at all once you set up an AX.25 interface in
Xastir and enable it.

You'll also have to do "chmod 4755 /usr/local/bin/xastir" as root in
order to give Xastir the proper privileges to open an AX.25
networking port.  Xastir drops privileges to normal user level
unless it's messing with ports where it needs root privilege.

--
Curt, WE7U.   APRS Client Comparisons: 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: Problems using MKISS

[William McKeehan]

Is there a way to setup Xastir on one linux box and have it talk to the AX.25
stack on a second box?

I'm guessing that if this is possible, I would need to setup an AX.25 stack on
the box where Xastir is running and somehow configure it to talk to the AX.25
stack on the other box.

Is this possible?
-- 
William McKeehan

On Thu, March 15, 2007 10:41 am, Curt, WE7U wrote:
> On Thu, 15 Mar 2007, Chuck Hast wrote:
>
>> I was looking at Xastir docs and it appears that it will work with the ax25
>> stack.
>
> Yes.  It'll work with the AX.25 stack -or- with the "soundmodem"
> driver set up as a serial KISS TNC -or- with a KISS TNC on a direct
> serial port -or- with a non-KISS TNC on a direct serial port.
>
> Of course the only way to share TNC's with other apps is to use the
> AX.25 stack.
>
> Xastir has a "View->Incoming Data" dialog so you can see whether
> packets are coming in at all once you set up an AX.25 interface in
> Xastir and enable it.
>
> You'll also have to do "chmod 4755 /usr/local/bin/xastir" as root in
> order to give Xastir the proper privileges to open an AX.25
> networking port.  Xastir drops privileges to normal user level
> unless it's messing with ports where it needs root privilege.
>
> --
> Curt, WE7U.   APRS Client Comparisons: 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!"
> -
> 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: Problems using MKISS

[Curt, WE7U]

On Thu, 15 Mar 2007, William McKeehan wrote:

> Is there a way to setup Xastir on one linux box and have it talk to the AX.25
> stack on a second box?

Yes.  You'd turn on "Interface->Enable Server Ports" on the Xastir
instance running on the system with the AX.25 stack.  This makes a
TCP/IP port available which the other Xastir can connect to.

You'd also need to enable gating of your packets through that system
to the RF interfaces via the ~/.xastir/data/nws-stations.txt file.
Enter the callsign-SSID of the remote Xastir station on a separate
line in that file.

I don't recall whether you'd have to enable igating on the Xastir
interface and globally on the File->Configure->Defaults dialog as
well.  Test it and see.  In any case I'm running a wireless laptop
at home sometimes with Xastir, gating to RF via another Xastir on
the desktop which is hooked to the TNC.  Same basic setup as what
you're asking about.

--
Curt, WE7U.   APRS Client Comparisons: 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: Problems using MKISS

[William McKeehan]

Well, the box with the AX.25 stack and TNC does not have the memory to run
Xastir (or X windows for that matter). So running Xastir there and enabling
the server port is not an option for me.
-- 
William McKeehan

On Thu, March 15, 2007 11:04 am, Curt, WE7U wrote:
> On Thu, 15 Mar 2007, William McKeehan wrote:
>
>> Is there a way to setup Xastir on one linux box and have it talk to the
>> AX.25
>> stack on a second box?
>
> Yes.  You'd turn on "Interface->Enable Server Ports" on the Xastir
> instance running on the system with the AX.25 stack.  This makes a
> TCP/IP port available which the other Xastir can connect to.
>
> You'd also need to enable gating of your packets through that system
> to the RF interfaces via the ~/.xastir/data/nws-stations.txt file.
> Enter the callsign-SSID of the remote Xastir station on a separate
> line in that file.
>
> I don't recall whether you'd have to enable igating on the Xastir
> interface and globally on the File->Configure->Defaults dialog as
> well.  Test it and see.  In any case I'm running a wireless laptop
> at home sometimes with Xastir, gating to RF via another Xastir on
> the desktop which is hooked to the TNC.  Same basic setup as what
> you're asking about.
>
> --
> Curt, WE7U.   APRS Client Comparisons: 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: Problems using MKISS

[Curt, WE7U]

On Thu, 15 Mar 2007, William McKeehan wrote:

> Well, the box with the AX.25 stack and TNC does not have the memory to run
> Xastir (or X windows for that matter). So running Xastir there and enabling
> the server port is not an option for me.

So run "aprsd" instead?

--
Curt, WE7U.   APRS Client Comparisons: 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: Problems using MKISS

[William McKeehan]

I did not realize that aprsd could connect to the AX.25 stack as opposed to
directly to the TNC.

I'll fetch it and have another look, thanks for the suggestion.
-- 
William McKeehan

On Thu, March 15, 2007 11:08 am, Curt, WE7U wrote:
> On Thu, 15 Mar 2007, William McKeehan wrote:
>
>> Well, the box with the AX.25 stack and TNC does not have the memory to run
>> Xastir (or X windows for that matter). So running Xastir there and enabling
>> the server port is not an option for me.
>
> So run "aprsd" instead?
>
> --
> Curt, WE7U.   APRS Client Comparisons: 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: Problems using MKISS

[Curt, WE7U]

On Thu, 15 Mar 2007, William McKeehan wrote:

> I did not realize that aprsd could connect to the AX.25 stack as opposed to
> directly to the TNC.
>
> I'll fetch it and have another look, thanks for the suggestion.

There are several versions of aprsd floating around out there,
modified by various people.  At least one of them can.  Probably the
SourceForge.org latest version?

--
Curt, WE7U.   APRS Client Comparisons: 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: Problems using MKISS

[Chuck Hast]

On 3/15/07, Curt, WE7U <archer@eskimo.com> wrote:
> On Thu, 15 Mar 2007, William McKeehan wrote:
>
> > I did not realize that aprsd could connect to the AX.25 stack as opposed to
> > directly to the TNC.
> >
> > I'll fetch it and have another look, thanks for the suggestion.
>
> There are several versions of aprsd floating around out there,
> modified by various people.  At least one of them can.  Probably the
> SourceForge.org latest version?
>
APRSD is what I have got to get working on our switches, we are going to
add a 144.99 port on the switches for WX and other remote metering equip-
ment so we can move them off of 144.39... Most of that stuff is quite low
power so a nice quiet channel would be a good thing... There is some
packet but not nearly enough to cause any pain and agony, and indeed in
some places the original users welcome the remote sensor activity as it
puts something on their dead channel... (hint, hint, need some activity on
your LAN channel bring some remote sensors on it, most are just a few
watts and do not cause that much of a problem)

-- 
Chuck Hast  -- KP4DJT --
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: Problems using MKISS

[Hamish Moffatt]

On Thu, Mar 15, 2007 at 09:10:37AM -0700, Curt, WE7U wrote:
> On Thu, 15 Mar 2007, William McKeehan wrote:
> 
> > I did not realize that aprsd could connect to the AX.25 stack as opposed to
> > directly to the TNC.
> >
> > I'll fetch it and have another look, thanks for the suggestion.
> 
> There are several versions of aprsd floating around out there,
> modified by various people.  At least one of them can.  Probably the
> SourceForge.org latest version?

All of the 2.14 versions can. Earlier versions had my special "vk3sb"
flavour which could. 

The sourceforge.net version is the latest "official" version though 
it's not being actively developed.

Hamish
-- 
Hamish Moffatt VK3SB <hamish@debian.org> <hamish@cloud.net.au>

Re: Problems using MKISS

[Stephen Brown Jr]

I've got Xastir running over an AXIP link to another box using
AX25IPD. I set up my /etc/ax25/axports file on both machines, ran
kissattach on the associated interfaces, and I'm able to pass packets
between both machines.

William, if you want some configs let me know.....

I'm still not real clear on how I would "share" my TNC sitting on
/dev/ttyS4 however....

73's
Stephen
K1LNX


On 3/15/07, William McKeehan <mckeehan@mckeehan.homeip.net> wrote:
> I did not realize that aprsd could connect to the AX.25 stack as opposed to
> directly to the TNC.
>
> I'll fetch it and have another look, thanks for the suggestion.
> --
> William McKeehan
>
> On Thu, March 15, 2007 11:08 am, Curt, WE7U wrote:
> > On Thu, 15 Mar 2007, William McKeehan wrote:
> >
> >> Well, the box with the AX.25 stack and TNC does not have the memory to run
> >> Xastir (or X windows for that matter). So running Xastir there and enabling
> >> the server port is not an option for me.
> >
> > So run "aprsd" instead?
> >
> > --
> > Curt, WE7U.   APRS Client Comparisons: 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!"
> >
>
> -
> 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: Problems using MKISS

[Bill Vodall WA7NWP]

> > Is there a way to setup Xastir on one linux box and have it talk to the AX.25
> > stack on a second box?

Yes - this is actually taken from some of the Xastir docs..

  http://nwp.ampr2.net/jnos/RemoteSerial

As long as you're on one Linux box, it works best to KISSATTACH the
external device and then multiple applications can all use the AX25
device at the same time.  If you need to access it from an application
that talks KISS but not Linux-AX25, then use the net2kiss command to
bring the AX25 data to a virtual serial port.  That's how JNOS talks
"packet" on a linux system.

73
Bill - WA7NWP

>
> Yes.  You'd turn on "Interface->Enable Server Ports" on the Xastir
> instance running on the system with the AX.25 stack.  This makes a
> TCP/IP port available which the other Xastir can connect to.
>
> You'd also need to enable gating of your packets through that system
> to the RF interfaces via the ~/.xastir/data/nws-stations.txt file.
> Enter the callsign-SSID of the remote Xastir station on a separate
> line in that file.
>
> I don't recall whether you'd have to enable igating on the Xastir
> interface and globally on the File->Configure->Defaults dialog as
> well.  Test it and see.  In any case I'm running a wireless laptop
> at home sometimes with Xastir, gating to RF via another Xastir on
> the desktop which is hooked to the TNC.  Same basic setup as what
> you're asking about.
>
> --
> Curt, WE7U.   APRS Client Comparisons: 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!"
> -
> 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: Problems using MKISS

[William McKeehan]

Bill, this looks very good! I had not noticed this in the docs before and the
solution presented in the FAQ did not work well for me, but the net2kiss looks
like it may just get me what I want!

Thanks!
-- 
William McKeehan

On Thu, March 15, 2007 1:03 pm, Bill Vodall WA7NWP wrote:
>> > Is there a way to setup Xastir on one linux box and have it talk to the
>> AX.25
>> > stack on a second box?
>
> Yes - this is actually taken from some of the Xastir docs..
>
>   http://nwp.ampr2.net/jnos/RemoteSerial
>
> As long as you're on one Linux box, it works best to KISSATTACH the
> external device and then multiple applications can all use the AX25
> device at the same time.  If you need to access it from an application
> that talks KISS but not Linux-AX25, then use the net2kiss command to
> bring the AX25 data to a virtual serial port.  That's how JNOS talks
> "packet" on a linux system.
>
> 73
> Bill - WA7NWP

Re: Problems using MKISS

[William McKeehan]

The link to remserial and net2kiss turns out to be exactly what I wanted.

I have a soundmodem TNC which is controlled by the AX.25 stack. digi_ned talks
to the ax.25 stack as does javaprssrvr.

Today I added net2kiss which talks to ax.25 and creates a virtual serial port;
the virtual serial port looks like a kiss TNC to anything that attaches.

Then I added the remserial to redirect that virtual serial port to another
machine. I connected Xastir to another virtual serial port created by
remserial.

So here's my setup.

Box 1 (server box)
Soundmodem/AX.25 (setup described in an earlier message)
net2kiss - net2kiss -a -i ax0 -s /tmp/net2kisslink &
remserial - remserial -d -p 23000 -s "9600 raw" /tmp/net2kisslink &

Box 2 (client box)
remserial - remserial -d -r 192.168.1.201 -p 23000 -l /dev/remserial1 /dev/ptmx &
Xastir - Serial KISS TNC connected to /dev/remserial1

Now if I could just get remserial to compile on cygwin I'd be very happy.
-- 
William McKeehan

> On 3/15/07, William McKeehan <mckeehan@mckeehan.homeip.net> wrote:
>>
>> Bill, this looks very good! I had not noticed this in the docs before and
>> the
>> solution presented in the FAQ did not work well for me, but the net2kiss
>> looks
>> like it may just get me what I want!
>>
>> Thanks!
>> --
>> William McKeehan
>>
>> On Thu, March 15, 2007 1:03 pm, Bill Vodall WA7NWP wrote:
>> >> > Is there a way to setup Xastir on one linux box and have it talk to
>> the
>> >> AX.25
>> >> > stack on a second box?
>> >
>> > Yes - this is actually taken from some of the Xastir docs..
>> >
>> >   http://nwp.ampr2.net/jnos/RemoteSerial
>> >
>> > As long as you're on one Linux box, it works best to KISSATTACH the
>> > external device and then multiple applications can all use the AX25
>> > device at the same time.  If you need to access it from an application
>> > that talks KISS but not Linux-AX25, then use the net2kiss command to
>> > bring the AX25 data to a virtual serial port.  That's how JNOS talks
>> > "packet" on a linux system.
>> >
>> > 73
>> > Bill - WA7NWP
>>
>

Re: Problems using MKISS

[Chuck Hast]

On 3/15/07, Curt, WE7U <archer@eskimo.com> wrote:
> On Thu, 15 Mar 2007, Chuck Hast wrote:
>
> > I was looking at Xastir docs and it appears that it will work with the ax25
> > stack.
>
> Yes.  It'll work with the AX.25 stack -or- with the "soundmodem"
> driver set up as a serial KISS TNC -or- with a KISS TNC on a direct
> serial port -or- with a non-KISS TNC on a direct serial port.
>
> Of course the only way to share TNC's with other apps is to use the
> AX.25 stack.
>
> Xastir has a "View->Incoming Data" dialog so you can see whether
> packets are coming in at all once you set up an AX.25 interface in
> Xastir and enable it.
>
> You'll also have to do "chmod 4755 /usr/local/bin/xastir" as root in
> order to give Xastir the proper privileges to open an AX.25
> networking port.  Xastir drops privileges to normal user level
> unless it's messing with ports where it needs root privilege.
>
Ahh, I knew that if I waited long enough I would get the info on how to set
up a Xastir port on a Linux FPAC switch so we can add that function to
our switch stack.....



-- 
Chuck Hast  -- KP4DJT --
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: Problems using MKISS

[William McKeehan]

I have javaprssrvr setup to talk to ax25:
  TNCModule=javAPRSDigi
  digiTNCInterface=ax25Interface
  ax25TNCPortName=aprs

Then I also have digi_ned talking to ax25
  digi_ned -p aprs
(notice the same port name was used).

Then I have the aprs port setup in my axports file:
  aprs    KI4HDU  9600    255     2       SOUNDMODEM
  #kiss   KI4HDU-0        9600    255     2       KISS

The kiss line was used when I had a kiss mode TNC attached. I would change hte
port in the javaprssrvr ini and the digi_ned startup to use the kiss port as
opposed to the aprsw port.

Before I startup javaprssrvr and digi_ned, I start ax25d (/usr/sbin/ax25d);
before I startup ax25d, I start my low level interfaces.
For the aprs port defined above:  /usr/sbin/sounmodem -M -s
For the kiss port defined above: /usr/sbin/kissattach /dev/ttyS0 kiss
192.168.10.1

Note that the port name on the kissattach command, "kiss", matches the port
defined in the axports file.

So I can have multiple things accessing the same TNC on the same box (via the
ax25d), but I have not yet figured out how to do that remotely.

Hope this helps!

-- 
William McKeehan

On Thu, March 15, 2007 10:16 am, Stephen Brown Jr wrote:
> Ok, that will work good for regular connected mode packet, how would I
> set it up for APRS? I have two apps, both of which will run in the
> background and a third app(xastir) connected via an AXIP link from
> another box.
>
> I'm getting closer........

Re: Problems using MKISS

[Stephen Brown Jr]

Xastir works well with the AX.25 stuff(as it should), I'm able to get
packets between both machines using AXIP, the hard part is trying to
figure out how to get data to/from the TNC to Xastir using AXIP on the
remote machine where the TNC is connected. I've seen AX25d come up
more than once, can AX25d be used for APRS or is it more geared
towards conventional connected mode packet?

Maybe AX25d is what I need to focus my sights on?

On 3/15/07, William McKeehan <mckeehan@mckeehan.homeip.net> wrote:
> I have javaprssrvr setup to talk to ax25:
>   TNCModule=javAPRSDigi
>   digiTNCInterface=ax25Interface
>   ax25TNCPortName=aprs
>
> Then I also have digi_ned talking to ax25
>   digi_ned -p aprs
> (notice the same port name was used).
>
> Then I have the aprs port setup in my axports file:
>   aprs    KI4HDU  9600    255     2       SOUNDMODEM
>   #kiss   KI4HDU-0        9600    255     2       KISS
>
> The kiss line was used when I had a kiss mode TNC attached. I would change hte
> port in the javaprssrvr ini and the digi_ned startup to use the kiss port as
> opposed to the aprsw port.
>
> Before I startup javaprssrvr and digi_ned, I start ax25d (/usr/sbin/ax25d);
> before I startup ax25d, I start my low level interfaces.
> For the aprs port defined above:  /usr/sbin/sounmodem -M -s
> For the kiss port defined above: /usr/sbin/kissattach /dev/ttyS0 kiss
> 192.168.10.1
>
> Note that the port name on the kissattach command, "kiss", matches the port
> defined in the axports file.
>
> So I can have multiple things accessing the same TNC on the same box (via the
> ax25d), but I have not yet figured out how to do that remotely.
>
> Hope this helps!
>
> --
> William McKeehan
>
> On Thu, March 15, 2007 10:16 am, Stephen Brown Jr wrote:
> > Ok, that will work good for regular connected mode packet, how would I
> > set it up for APRS? I have two apps, both of which will run in the
> > background and a third app(xastir) connected via an AXIP link from
> > another box.
> >
> > I'm getting closer........
>

Re: Problems using MKISS

[J. Lance Cotton]

on 3/15/2007 8:38 AM Stephen Brown Jr said the following:
> How would I get more than one app to talk to a single tty, ttyS4 in my
> case, this is the port the TNC is connected to. This is the part of
> the puzzle I seem to be missing......

When you "kissattach" to ttyS4, a network device (ax0 or similar) is 
created. Like the "ethernet device", eth0, access is not exclusive.

The AX.25 network device ax0 is then associated with the appropriate entry 
in /etc/axports. Multiple apps can access the device this way. You don't 
have to split the streams up.

This is as I understand it -- I may be wrong.

-Lance KJ5O

-- 
J. Lance Cotton, KJ5O
joe@lightningflash.net
http://kj5o.lightningflash.net
Three Step Plan: 1. Take over the world. 2. Get a lot of cookies. 3. Eat the 
cookies.