This is happening very often....it happened to me and to several
others after I learned. It is a "sky is falling" syndrome. For me it
was not clear that you must include MKISS. My previous experience
with ham TCPIP has been JNOS, and kiss is defined in those cases you
have to send two ports data via one COM port, as happens with KAM,
KPC-4 or KPC-9612.
With Linux, you MUST INCLUDE MKISS. It has been a different mindset,
so just adhere to it and go ahead.
TIOCSETD is a "discipline" that sets something. Without mkiss, you
are asking your serial ports to do something you have not "trained"
them for, and they are complaining they don't know how to do it.
If you have a modularized kernel, you must load the proper modules
before using AX25. I do not use modules by now.
Shouldn't it be added some warning in the ax25-utils distribution, as
we are needing a refresh in the HOW-TO's and it has not been possible,
that MKISS MUST BE COMPILED IN, and MODULES LOADED (if you use them)
before AX25 works ? This is happening way too often and seemingly
many are following the wrong lead. It happened to me before, and
keeps on happening.
Just a thought. Excuse me for the layman explanation. I hope this
helps in some way.
73 de Jose, CO2JA.
-----
On 17 Feb 99 at 23:18, Bob LaFont wrote:
> Can someone with AX25 Linux experience help Gary with his questions ?
>
> Gary is not subscribed to this list. You can either send replies directly
> to Gary at [EMAIL PROTECTED] or reply to me and I willl forward to
> Gary.
>
> Thank you
>
> 73 / Bob
>
> -----Original Message-----
> From: [EMAIL PROTECTED] [SMTP:[EMAIL PROTECTED]]
> Sent: Wednesday, February 17, 1999 9:48 PM
> To: wa2mno
> Subject: Linux Help
>
> Hi Bob
> I did get some info from VK2KTJ on the conference bridge regarding versions
> and what utils go together. So far I have installed Slackware 3.5 which
> contains
> the 2.0.34 kernel and then applied the 2.0.35 patch which I am told is
> needed to
> work with the ax25-utils-2.1.42a package and the net-tools-1.33a-alpha
> package.
> All of this seemed to compile OK , creating proper subdirectories. I am
> still
> having a problem with the ax25 talking to my COM 1 (or) 2 ports. I place
> the
> TNC in the KISS mode and have it connected to the COM port 1. Then I try to
> use
> the following cmd: kissattach -i 44.94.248.213 /dev/ttyS0 vhf (having
> modified the
> axports file port name to vhf) This returns an error to me: kissattach:
> TIOCSETD:
> Invalid argument. Can you define TIOSETD to me? or see any invalid
> argument?
> When Linux boots up, it shows a serial port driver loaded but says the
> port is not set active. I have a set of older instructions that used the
> axattach command which I saw in an earlier util ver 2.0.12c that I compiled
> but that command does seem available in the new utils.
> ttyS0 and ttyS1do appear in the /dev listing. The ports work fine using
> the paket6 program under DOS indicating they are working. A telephone modem
> command ATDT run under Linux ONLY flashes the lights on my external Hayes
> modem which seems to mean that Linux will talk to the ports but the ham
> utils are not working.
> You mentioned the slattach command which is in the kernel. I understand
> that
> is used to configure a slip connection?? Do I need to configure the COM
> port
> to a slip connection before attaching or should the utils talk directly to
> the port?
> I am struggling and learning. Any direction you can give me would be
> appreciated. Thanks.
> 73s de Gary/W0DYD
> a25 - w0dyd-3 mailbox
> or [EMAIL PROTECTED]
>
> ---
Ing. Jose A. Amador | Telf: (537) 20-7814
Depto de Telecomunicaciones | E-Mail: [EMAIL PROTECTED]
ISPJAE |
