[Packet] Linux & axports.
Doug Laidlaw
[email protected]
Tue, 3 Jun 2003 18:14:44 +1000
Would it be worth saying that minicom is the Linux equivalent of Windows'=
=20
HyperTerminal? It can be used to access a phone BBs, like Telix. If you=
can=20
get the TNC's copyright message to print out on a terminal (in terminal=
=20
mode, not KISS mode) at least the TNC and the computer are talking to eac=
h=20
other. You don't use minicom to operate.
Doug.
On Tuesday 03 Jun 2003 3:24 pm, Shane Deering wrote:
> On Tue, 3 Jun 2003 03:59, Doug Younker wrote:
> > Evidently I didn't present my question clearly. I understand that KIS=
S
> > operation lets a more powerful computer and application take over the
> > work the TNCs embedded computer does. The person who made the first =
post
> > mentioned having trouble with minicom communicating to the TNC and th=
at
> > lead to discussion of AX25 and KISS. What does AX25 and KISS have to=
do
> > with an application that basically turns a computer into a dumb termi=
nal
> > not communicating properly with a TNC where the TNC handles the AX25?
>
> Nothing and that wasn't the problem. The problem was using a packet pro=
gram
> (xcall, a GUI version of call) that uses the built in kernel ax25.
> There is only one mention of minicom (which could talk to the TNC). The
> rest of the post is about using kernel ax25 (with a TNC). That means ei=
ther
> KISS or 6pack.
> If that's still not clear, imagine you were trying to get a packet prog=
ram
> to work that need to use flex or BPQ. You could use a dumb terminal to =
talk
> to the TNC, but your program didn't work. Your problem is getting BPQ o=
r
> flex to work. Not with your dumb terminal.
--=20
Linux: in a world without fences, who needs Gates?
--and what's more, it's immune to viruses.