[FADCA] TelPac app integrated

[Chuck Hast]

Folks,
I have the Telpac integrated into the Linux FPAC box. 

Here is what it looks like if you ssh into the box and issue the
telpac command or you connect to kp4djt-10 v 813626


KP4DJT-8 (Commands = ?) : telpac
Trying KP4DJT-10 @ 3100,813626... Type <RETURN> to abort
*** Connected to KP4DJT-10 @ 3100,813626 (Escape: ~. )
*** Connecting to kn6kb.no-ip.com ...

TelPac-Node/LinuX Rev0.9b11 (dl5di May  9 2005)

*** Nodecall: >KP4DJT-10<
This is the KP4DJT-10 TelPac application running on the KP4DJT
LINUX FPAC switch.
*** Connected

Winlink 2000 Telnet Logon OK

[WL2K-3.0.80-B2FIHM$]
KN6KB Winlink 2000 Telnet Server
Telpac packet node registration at: www.winlink.org/status/Telpac.aspx

KP4DJT VIA KP4DJT-10 DE KN6KB >


If you are on the lan ports of the switch a simple connect to kp4djt-10
will get you the wl2k server, if you are on the network a connect to
kp4djt-10 @ 813626  (remember that the full string is
c kp4djt-10 v switch 813626 where switch is your local switch call)

The local direct LAN freq is 145.03, but you can hit it from any
networked switch that has connectivity to 813626...

Once I realized that I had left out the callsign in the first line of the
telpac.cfg file and added it, the whole thing came up just fine. Now to
get airmail in one of these pieces of junk and get it up and running.

Setting the telpac node up as a application that the FPAC switch
talks to was very easy. I was just not looking at the small stuff like
call sign placement.
-- 
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."