[FADCA] TelPac app integrated

[Chuck Hast]

On 5/13/05, bud's Laptop <budt at cfl.rr.com> wrote:
> 
> ----- Original Message -----
> From: "Chuck Hast" <wchast at gmail.com>
> To: "FADCA" <fadca at mailman.qth.net>
> Cc: <n4xeo at bellsouth.net>; <N3PPC at winlink.org>; <W5TWR at winlink.org>;
> <W8EHH at winlink.org>; <willy3jax at covad.net>; <N4KOX at winlink.org>;
> <cyber-bill at juno.com>; <k4cjx at comcast.net>; <n6zue at arrl.net>;
> <WB4MOZ at winlink.org>; <n0ia-11 at winlink.org>; <N4ZEO at winlink.org>;
> <oderr at bellsouth.net>
> Sent: Thursday, May 12, 2005 8:10 PM
> Subject: [FADCA] TelPac app integrated
> 
> 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
> 
> * * *
> 
> Fantastic, Chuck-
> 
> Now for those of us who are (still) Windows-bound - what can we do to 'ssh'?
> I've never asked before out of ignorance- but is ssh a telnet operation?
> I've got a telnet client on my Airmail and a telnet channel on my Paclink
> AGW set up here in the laptop - of course the fact that I have an internet
> connection at the hotel  means I don't need to telnet to a TelPac node, but
> still, if I can, I'd like to check out your Telpac/FAPAC/Linux.

I do not have the telnet server up and running, I initially did not
instal it because
of security issues with telnet and at that time I was not thinking about needing
it because ssh is a inherent part of linux. Here is what you need to
ssh into the
machine, it is called PuTTY.
http://www.chiark.greenend.org.uk/~sgtatham/putty/download.html
Download it and install it.
Then you are going to need the following info in order to access the machine.
Name or address:
24.129.134.206
Make sure you have selected ssh on the putty screen and then hit the 'open'
button. You should be met with a simple screen that ask  you  "log in as:"
you will user "fpacuser". All commands are ended with a carrage return
also drop the quotes.
Then it will ask you for "fpacuser password"  to which you will reply with
"fpac".
At this point you should see the following:
login as: fpacuser
Sent username "fpacuser"
fpacuser at 192.168.1.105's password:
Welcome to Knoppix (Kernel 2.4.22-xfs)


FPAC-Node v 3.26 (fpac-dev)

callsign:

At the callsign prompt give your callsign and you will be greeted with a FPAC
login, as seen below

login as: fpacuser
Sent username "fpacuser"
fpacuser at 192.168.1.105's password:
Welcome to Knoppix (Kernel 2.4.22-xfs)


FPAC-Node v 3.26 (fpac-dev)

callsign: kp4djt
FPAC-Node v 3.26 (F6FBB - Dec 18 2002) for LINUX (help = h)

KP4DJT-8 (Commands = ?) :


At that point a question mark will give you the switch command list :

login as: fpacuser
Sent username "fpacuser"
fpacuser at 192.168.1.105's password:
Welcome to Knoppix (Kernel 2.4.22-xfs)


FPAC-Node v 3.26 (fpac-dev)

callsign: kp4djt
FPAC-Node v 3.26 (F6FBB - Dec 18 2002) for LINUX (help = h)

KP4DJT-8 (Commands = ?) : ?
?, Alias, ARC, ARC1, AXparms, AXStats, BBS, BBS1, Bye, CLW
Connect, Dest, EOC, Finger, Help, HOst, Info, IPLinks, IPRoutes, Links
Mheard, Nodes, PARis, PIng, Ports, Quit, ROQ, ROSE, Routes, RS_N
SRQ, STA1, STA24, Status, SYSop, Telnet, TELPac, TPA, TRace, Users
Wp

KP4DJT-8 (Commands = ?) :


I have noticed something, the system seems to respond to all the commands
but the Bye command. I can tell it to send me a list of messages, I can send
it the Info command and it responds to all of them, but when I send it the Bye
command it sets there and just does  nothing.  After a while it will
finally time
out or maybe the Bye does drop it but it appears to be quite a long period.



> 
> This is a major step for EMCOMMs - as you have pointed out - for those
> (hardened) FPAC sites to have a TelPac node associated minimizes the initial
> need locally for additional major network components such as backbones to
> everywhere.

Also this will allow those who are using their home equipment as telpac nodes
not to have to keep them on line all of the time, and at the same time
if there is
network connectivity into areas that are not served by a node, those areas now
have that service. Also as we move the trunks to higher and higher speeds the
response of a distant device will become much better, and for someone who is
out in rural parts of even Hillsborough County (Ft. Loansome comes to mind) that
and dialup maybe their only solution still.

At the same time this adds more functionality to the switch, allowing
it to route
the connection to the internal facility and out on a high speed
internet connection
giving much better response time.



-- 
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."