[FADCA] Quick connect for TelPac
bud thompson
[email protected]
Mon, 14 Apr 2003 07:46:35 -0400
Deltona
Monday April 14 0705EST
Okay - -6 SSID it is for TelPac quick connect.
I'll set up the Orlando FPAC switch for
alias=6;KF4SIR-2, 407277, FLORL
until we move the Orlando Switch when it will be able to reach KF4SIR-2
direct w/o the FLORL digi
>Now, the question is what Telpac nodes are out there?
The only ones I know not on your list are
KF4SIR-2 (Orlando Lan)
Russ has one I think - he'll have to fill us in.
My WL2K packet port will eventually be on the DeLand LAN - I think for
operational considerations we can consider a WL2K Packet port the same as a
TelPAC - Rick KN6KB may need to confirm that. If so, then we can use the -6
as a quick connect for that as well. Except for backup purposes there would
not be any need for more than one TelPac or WL2K packet port on a LAN. It
would also be best if each LAN had one or the other, but until we get more
folks involved, we'll work with what we can get.
Dave N4ZKF may put one up on the DAB LAN.
We need to get the word out that setting up a TelPAC node is something that
ANYONE can do cheap - I'll put out a FADCA note on that later
> Adding additional quick connects to fpac above ssid -15 will not be
useable
> from a users tnc.
RE: Linux FPAC - What I'm proposing is that we use pure aliases - not ssids.
We would not be limited by the AX.25 convention. These could be any alpha
mnemonics - most TNCs will support that. Actually, over the long run, most
packet users will be using Airmail anyway and it supports connecting to a
mnemonic. (I'm fairly certain I checked that out.... but not a major problem
and it can be fixed if needed.)
The .cfg entry might look like this:
alias=TELPAC; KF4SIR-2,407277
or this
alias=TELPAC:N0IA,386336
The quick connect
C TELPAC
on a local port would get the user to the TelPac or WL2K station set up in
the alias.
Yes, some terminal programs support programmable hot keys or connect
scripts. Until we get Airmail working universally on our packet network, I
recommend WinPack - it has connect scripts for a pull-down menu as well as
assignment to hot keys. It also has a PBBS and will do "e-mail" - but I've
not checked out the e-mail compatibility with WL2K - I'd doubt it will work,
but we need to learn. Actually, Airmail needs some changes to support this
type of programmable scripting for connect scripts.
If you want to dream - eventually Airmail could be set up for a connect
script CATALOG - (WL2K has a fantastic catalog system.) The list of connect
scripts for a three-FPAC switch area can be established and maintained and
downloaded automatically from the internet. Once our network is filled in
with EOCs, BBSs, TelPaCs, etc. a tactical connect script for an
emergency/exercise inside a Last Mile could be made within a few minutes a
posted on the WL2K CMBO.. Before our fearless digital team left town to
drive 100 miles into the Last Mile each would just get on a local TelPac and
order the connect catalog. The updated connect scripting would be
automatically loaded into Airmail.
Yeah, it will be a while before we have that - but setting it up through
WL2K is a no brainier.
Thanks..
bud
---------------------------------------------------------------------
"Are you still wasting your time with spam?...
There is a solution!"
Protected by GIANT Company's Spam Inspector
The most powerful anti-spam software available.
http://www.giantcompany.com
----- Original Message -----
From: "John H. Green" <[email protected]>
To: <[email protected]>
Sent: Saturday, April 12, 2003 13:08
Subject: Re: [FADCA] Quick connect for TelPac
>
>
>
>
>
>
>
> Hi All
>
> I don't have a problem with using -6, well maybe a slight one. We have
> a bbs (n4joa) using -6 now, but I think this can be moved.. If there are
> no further comments I think I will get started making the changes. Now,
the
> question is what Telpac nodes are out there?
>
> Info is needed for the following that do not have a station listed:
>
>
>
> Lan / City TelPac/WL2K Station
> Arcadia / Brownsville
>
> Boca Raton
>
> Ft. Pierce
>
> Lake Harbor
>
> Lake Placid
>
> Melbourne kn6kb
> Okeechobee
>
> Sarasota
>
> Stuart
>
> Vero Beach
>
> West Palm Beach kd4lxb-2
>
>
> Please note - this list in not all inclusive, info is needed for other
areas
> also.
>
> Station should have a good reliable connection into the network,
preferably
> at a high speed.
>
>
>
> Bud, on your proposed lan frequency list you might include the TelPac
station
> and the quick connect..
>
>
>
> Now, the discussion on additional quick connects:
>
> Adding additional quick connects to fpac above ssid -15 will not be
useable
> from a users tnc. Most tnc's will not accept a connect request with -17 or
> -a. This is built into ax25 protocol. Since Fpac already uses -0 to -6
(quick
> connects) and -8, -9 -10 (switch call) this leave only 6 ssid's for
possible
> additional quick connects. Probably not enough for a busy EOC that has to
> connect to a bunch of shelters and other EOC's.
>
> An alternate solution might be to use the FPAC quick connects for
common
> things like TelPac, local BBS's, etc. and move the other needs to the
terminal
> program in the EOC, Shelter, etc. A simple program like Packcom has up to
> 40 function key positions (F1, shift F1, Alt F1 and Cntrl F1-10). Windows
> based terminal programs probably have even more. A cheat sheet could tell
> the operator which key to use for a certain connection. Using a standard
> program, identical key assignments and a cheat sheet should make it easier
> for the operators if they go to different location as needed.
>
> My 3 cents :-) (inflation,
> you know)
>
>
>
> 73 John
>
>
>
>
> bud thompson wrote:
>
>
> Deltona
> Thursday April 9 0535EST
>
> I agree on having a standard SSID for TelPac throughout the system.
>
> We discussed this a year ago when KN6KB first set up the SMS node which
> TelPac now transcends. At that time we only had the one SMS node KN6KB on
> the fledgling Melbourne FPAC switch and we decided on -4 ssid (W4MLB-4) as
> the standard. Changing a quick connect SSID in FPAC configuration is a
no
> brainer - except at Melbourne where we continue to not have site access,
now
> thanks to the War on Iraq! Hopefully that will be short lived - both the
> war and lack of site access.
>
> I'm not particular at this time, but we might consider the standard for
> TelPac as SSID -6 as that is the highest one available therefore stands
the
> best chance of not getting in he way of some already established.
>
> Here on the DeLand FPAC we already have SSIDs 0 through six assigned, but
> only 0 through five are presently in use. FPAC DOS presently restricts
> SSIDs for quick connect to a total of six, -1 though -6.
>
> Since we apparently cannot get any changes made to the FPAC DOS code -
>
> What I propose is that when we move to LINUX FPAC we establish more alias
> capability, which I naively assume could be done since LINUX
programs/stuff
> apparently can more readily be changed/modified at the user level. We
could
> actually use mnemonics - as we will certainly run out of ssids in the long
> run anyway. That way we could use TELPAC or WL2K (which is where TelPac
> leads), and others, such as EOC, DABBBS, etc. We could have as many as we
> decided was reasonably, perhaps 16 or so.
>
> Most Airmail mobiles (Sailors/RVers) who would be acquainted with WL2K
would
> be able to pick up this information on the Winlink web site - though it is
> not yet there since we are still in testing phase. Eventually, this
> information, along with the LAN frequencies could be set up as a WL2K
> catalog that can be requested via radio link.
>
> Additionally a link to the FADCA pages will be on the winlink web site and
> the LAN frequencies can be determined from the interactive map. I suggest
> we also have a list of LAN frequencies available there in text form -
>
> CITY COUNTY SWITCH CALL LAN FREQ
>
> Good job, John.
>
> bud N0IA
> ---------------------------------------------------------------------
> "Are you still wasting your time with spam?...
> There is a solution!"
>
> Protected by GIANT Company's Spam Inspector
> The most powerful anti-spam software available.
> http://www.giantcompany.com
>
>
> ----- Original Message -----
> From: "John H. Green" <[email protected]>
> To: "FADCA" <[email protected]>
> Sent: Wednesday, April 09, 2003 22:47
> Subject: [FADCA] Quick connect for TelPac
>
>
>
>
> Hi All
> I would like to suggest that we set up a standard ssid at each FPAC
> switch to connect to the nearest TelPac node. To open the discussion I
> suggest we use -3. Thus, here in the West Palm area connecting to
> k4pkt-3 would connect you to the kd4lxb-2 TelPac node. In the Stuart
> area connecting to k1vao-3 could connect to a TelPac node in the Stuart
> area or, utilizing the network, could connect to kd4lxb-2 in the West
> palm area. And so on.. :-)
> Once we get this setup a traveling user would only need to watch the
> beacon from the local switch to get the switch call (assuming they don't
> already know it) and connect to callsign-3 to get the nearest TelPac
> node. Of course, one still needs to find the local lan frequency - no
> easy task since they were removed from the repeater directory. :-(
>
> Present ssid use in South Fl.:
> -0 co-located bbs, otherwise unused.
> -1 Local bbs or as required locally.
> -2 As required locally.
> -3 Tampa Info Server (has been unavailable for over a year, network
> into Tampa out)
> -4 As required locally.
> -5 As required locally.
> -6 As required locally.
>
> Thoughts anyone??
>
> 73 John wb4moz
>
>
> _______________________________________________
> FADCA mailing list
> [email protected]
> http://mailman.qth.net/mailman/listinfo/fadca
>
>
>
>
>
> _______________________________________________
> FADCA mailing list
> [email protected]
> http://mailman.qth.net/mailman/listinfo/fadca
>
>
>
>
>
>
>
>
>
>
> --- StripMime Report -- processed MIME parts ---
> text/html (html body -- converted)
> The reason this message is shown is because the post was in HTML
> or had an attachment. Attachments are not allowed. To learn how
> to post in Plain-Text go to: http://www.expita.com/nomime.html ---
> _______________________________________________
> FADCA mailing list
> [email protected]
> http://mailman.qth.net/mailman/listinfo/fadca