[FADCA] Re: NTS traffic transmittal and delivery:
Stacey & Bob H.
[email protected]
Tue, 18 Feb 2003 23:58:17 -0500
John,
Also What Town do you live in?
Do you have packet?
If so do you have a Home PBBS?
If you didn't get the original message I sent I will be happy to send it
again. It has an attachment with all the Florida zip codes and associated
City's.
PS: I saw the msg to Bud a with Zip codes that you can handle traffic to. I
can build the list from that msg unless you have some free time.
Bob N4WFH
----- Original Message -----
From: "jdaughtry" <[email protected]>
To: <[email protected]>
Sent: Tuesday, February 18, 2003 09:18
Subject: Re: [FADCA] Re: NTS traffic transmittal and delivery:
> I can and do handle nts into and out of the following counties
> Sumter
> Citrus
> northern Polk
> Hernando
> i also have a route to a voice nts hound
> John
> ----- Original Message -----
> From: "bud thompson" <[email protected]>
> To: <[email protected]>
> Cc: "Phyllis Ann West, KA4FZI" <[email protected]>; "earl e leach"
> <[email protected]>
> Sent: Tuesday, February 18, 2003 6:51 AM
> Subject: Re: [FADCA] Re: NTS traffic transmittal and delivery:
>
>
> >
> > > NTS traffic may cycle through VHF/DIGITAL HF/DIGITAL VHF/VOICE
HF/VOICE
> > and
> > > back again until it reaches it's destination.
> > > My idea is to not have NTS traffic sent to a PBBS and HOPE someone
> > delivers
> > > it.
> >
> > Bob - you are absolutely correct - that is precisely why we don't put
NTS
> > traffic out on the local packet networks unless we have an assigned NTS
> Home
> > for it. If we do that blindly it dies a slow death. We don't have that
> all
> > set up yet in Florida because we (1) don't have enough BBS, (2) don't
have
> > enough NTS folks on digital and (3) don't have enough backbones in place
> to
> > get all around the network.
> >
> > Did you read about that on the FADCA web pages?
> >
> > If you like I can send you the list of NTS Home BBS w/ZIPs as it stands
> now.
> > That is certainly a place to start.
> >
> > That said, right now, my converting from Conventional Winlink on HF to
> WL2K
> > is not complete as I've not got the packet side of WL2K working yet -
too
> > busy with other stuff! So, my participating in the auto switching of
NTS
> > addresses has come to a halt until I get the packet side going. My
plan
> > was to have the N3PPC BBS become the NTS switch (taking over the
function
> I
> > did) as he is also on the packet network. We can use other NTS switches
on
> > the packet network as well. (NTS "switch" is only a routing function
based
> > on NTS addressing.)
> >
> > Of course the packet network is not quite all complete (not all
backbones
> > get us everywhere yet), and we don't have BBS at all LANS, nor do we
have
> > NTSers on packet everyplace. That is what needs to be worked on for
sure.
> >
> > Meanwhile....
> >
> > We have Earl WX4J (near JAX) who is the NFL STM on Classic Winlink HF
and
> > on the packet network. You might want to be sure you are working with
> him.
> > He, Phil KF4FZI near Ft. Myers(?), N4XEO Bill in Ft. Pierce, Nick N4SS
> > (Pensacola) and I all guarded a 40M pactor frequency to transfer NTS
> > messages around the state. That was all Classic Winlink and will still
> work
> > as a way to get traffic over distances. N4SS is ill and likely will not
> be
> > back on the air, N4XEO should be back on soon, and I don't know if Phil
is
> > still monitoring or not. It would be good to keep that 40M PacTOR layer
> > (yes, it is just another layer) going for NTS traffic as well as
> EOC-to-EOC
> > traffic until we get the rest of the network integrated.
> >
> > I'm not discouraging what you want to accomplish - only feel you may be
> > going off in a direction that will dilute a system that is (almost)
> already
> > there. I recommend you see if you can tie this all together rather than
> > start something that might not integrate into the packet network later.
> We
> > just don't have enough folks interested to have disparate systems.
> >
> > 73,
> > 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: "Stacey & Bob H." <[email protected]>
> > To: "FADCA List" <[email protected]>
> > Cc: "bud thompson" <[email protected]>
> > Sent: Monday, February 17, 2003 21:42
> > Subject: [FADCA] Re: NTS traffic transmittal and delivery:
> >
> >
> > > >Bob- you may be re-inventing the wheel... What you want to accomplish
> > needs
> > > to be done, >but it may be closer at hand than you think.
> > >
> > >
> > >
> > > Bud
> > >
> > > What I want to accomplish is to use a digital mode to send to another
> > > Amateur interested in delivery or re transmittal of NTS traffic. The
way
> > the
> > > Digital system is presently NTS traffic goes to it's destination and
> sits
> > > until it expires without delivery or doesn't make it to the
destination
> > PBBS
> > > because their is no path. This is unacceptable.
> > >
> > > I'm not trying to re invent the wheel. I'm trying to spread the load
of
> > NTS
> > > traffic I receive to other participating Amateurs. The Traffic is
being
> > sent
> > > to a specific Amateur whom has agreed to deliver or pass on NTS
traffic.
> > > This will insure that the NTS Traffic will be sent from one Amateur to
> > > another until delivery.
> > >
> > > NTS traffic may cycle through VHF/DIGITAL HF/DIGITAL VHF/VOICE
HF/VOICE
> > and
> > > back again until it reaches it's destination.
> > >
> > > My idea is to not have NTS traffic sent to a PBBS and HOPE someone
> > delivers
> > > it. My idea is to build a list of Amateurs that will accept NTS
traffic
> > sent
> > > to them for delivery or passage on to another Amateur until delivered.
> > >
> > > Bob N4WFH
> > >
> > > ---- Original Message -----
> > > From: bud thompson
> > > To: Stacey & Bob H. ; Frank AC4MK ; WB4TOV Harold ; KG4KCB Harry ;
> > KA4TTS
> > > Jack ; KD4GR Jim ; KF4OPT Jimmy ; AD4IH Joe ; WA9VND Laura ; K4LNP
Mark
> ;
> > > WX4H Mort ; KD4CQG Phyllis ; W4AAA Randy ; KQ4AZ Rick ; K4DWF Tom ;
> WB2FGL
> > > Tony ; WD4IUD Walt ; KE4VBA Warren ; K4DDY Wolf ; Bill W4HCS ; N4EP
Bill
> ;
> > > N4LTT Bill ; WR4FSU Bob ; K9SHT Bruce ; Wilbur AB4XK ; AA4CH ; NR2F
> > Charlie
> > > ; WD4GDB Chet ; AE4MR Dave ; N4GMU Dave ; KB4MON Dennis ; N9MN Don ;
> Earl
> > > K4FQU ; Ed ; W4WYR Evelyn
> > > Sent: Monday, February 17, 2003 21:07
> > > Subject: Re: NTS traffic transmittal and delivery:
> > >
> > >
> > > Deltona
> > >
> > > Monday Feb 17 2050EST
> > >
> > >
> > >
> > > Bob- you may be re-inventing the wheel... What you want to
accomplish
> > > needs to be done, but it may be closer at hand than you think.
> > >
> > >
> > >
> > > I encourage a coordinated effort of getting NTS folks on digital -
we
> > can
> > > use all the experienced message handling people we can get. Get out
the
> > > laptops/tncs/(soundcards)/2M radios and set up a portable packet to
use
> at
> > > shelters, hospitals, incident command. Also be sure an experienced
> > traffic
> > > handler/packet operator is on duty at your EOC.
> > >
> > >
> > >
> > > I suggest the following reading - it won't take long
> > >
> > >
> > >
> > > go to www.fadca.org
> > >
> > >
> > >
> > > Then click on Packet Articles about half way down in the left pane.
> > >
> > >
> > >
> > > Read "NTS MESSAGES ON THE DIGITAL NETWORKS" which is simply the
> > protocol
> > > to be used for NTS on digital. Then read "STATUS OF DIGITAL NTS IN
> > FLORIDA"
> > > which explains (1) the way it should/could be and (2) the way it
> actually
> > > is. The main problem is we don't have enough BBS on line on the
Layered
> > > Packet Network. If each LAN had an active BBS and each of those had
> > active
> > > folks watching for NTS traffic it would work swell.
> > >
> > >
> > >
> > > We do not need 7+ to handle NTS messages. BBS-to-BBS binary
> compression
> > > will do the work just fine. FBB BBS handles/routes NTS messages just
> > fine,
> > > providing we have "NTS friendly" BBS in a lot of communities. I'd
like
> > > nothing more than to have that here on the Layered Network as there
are
> > many
> > > NTS messages that go wanting on the 75M fone net (3940) most mornings.
> We
> > > could just take them and put them on packet - IF we had BBS all over.
> > >
> > >
> > >
> > > I suggest we all get together and support the layered packet network
> in
> > > our communities. Get you ham club/ARES group to sponsor/support a
> > > LAN/switch. Get a BBS on each LAN and the NTS traffic should flow
just
> > > fine.
> > >
> > >
> > >
> > > I may comment more on this reference note later.
> > >
> > >
> > >
> > > 73,
> > >
> > > bud N0IA
> > >
> > >
> > >
> > > PS: All that said, my main focus for digital messaging for EMCOMMs
is
> > with
> > > E-mail - that would include the traditional NTS role of Health and
> Welfare
> > > messages. Guess you might as well also read "Whither Goest NTS?"at
the
> > same
> > > web site.
> > >
> > >
> > >
> >
---------------------------------------------------------------------
> > > "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: Stacey & Bob H.
> > > To: Frank AC4MK ; WB4TOV Harold ; KG4KCB Harry ; KA4TTS Jack ;
KD4GR
> > Jim
> > > ; KF4OPT Jimmy ; AD4IH Joe ; WA9VND Laura ; K4LNP Mark ; WX4H Mort ;
> > KD4CQG
> > > Phyllis ; W4AAA Randy ; KQ4AZ Rick ; K4DWF Tom ; WB2FGL Tony ; WD4IUD
> Walt
> > ;
> > > KE4VBA Warren ; K4DDY Wolf ; Bill W4HCS ; N4EP Bill ; N4LTT Bill ;
> WR4FSU
> > > Bob ; K9SHT Bruce ; N0IA Bud ; Wilbur AB4XK ; AA4CH ; NR2F Charlie ;
> > WD4GDB
> > > Chet ; AE4MR Dave ; N4GMU Dave ; KB4MON Dennis ; N9MN Don ; Earl K4FQU
;
> > Ed
> > > ; W4WYR Evelyn
> > > Sent: Monday, February 17, 2003 17:43
> > > Subject: NTS traffic transmittal and delivery:
> > >
> > >
> > >
> > > ----- Original Message -----
> > > From: Stacey & Bob H.
> > > To: Bud N0IA ; Bill N4XEO ; Eric KB6YNO ; Robin VE3VVS ; Billy
N4UF
> ;
> > > Chuck Hast ; Wilbur AB4XK ; Charles NR2F ; Earl K4FQU ; Bill KC7TSG
> > > Sent: Monday, February 17, 2003 12:48
> > > Subject: NTS traffic transmittal and delivery:
> > >
> > >
> > >
> > > Hello everyone, for those that don't know me. My name is Bob N4WFH
> in
> > > North Port, Fl. I'm the sysop for the KF4HFR Packet BBS. I enjoy
> > > ARES/NTS and Packet Radio.
> > >
> > > :Belief
> > >
> > > I don't believe Packet Radio can reliably get NTS traffic
delivered
> to
> > > the intended recipient. However, Packet Radio can be reliably used
> to
> > > send NTS traffic to designated Amateur Radio operators at a Packet
> BBS
> > > or directly to an Amateur Radio Packet station as a text file
using
> 7+
> > > or YAPP transfer protocol, where it can be delivered or passed
> along.
> > >
> > > :NTS List
> > >
> > > I would like develop an list of Amateur Radio Operators whom have
> VHF
> > > packet capability and regularly participate in the NTS system
either
> > > VHF/HF, Digital/Voice.
> > >
> > > :How to use the list
> > >
> > > I receive as many as twenty NTS msg's a day into KF4HFR packet BBS
> > > during events or Holiday times of the year. I cannot put all these
> > > msg's on voice Nets myself. I want to build an list of Amateurs
> > willing
> > > to help in passing these messages via Amateur Radio. From this
list
> I
> > > will build forwarding files that will separate the NTS traffic
into
> > > different files. Theses files will be sent to Amateurs based on
the
> > > information they submit in the list, using the following
guidelines.
> > >
> > > First, they will be sent to the Amateur in the delivery area.
> Second,
> > > if no particular Amateur is listed in the delivery area. They're
> sent
> > > to whom is closest to the delivery area. Third, if the message is
> out
> > > of Florida they will be sent to those with HF capabilities.
> > >
> > > These messages will be sent to an Amateur Radio Operator at their
> > local
> > > Packet BBS as a 7+ file or via directly connecting to a Packet
Radio
> > > Station. This will alleviate a copy of the message on every PBBS
it
> > > passes through where others might try to deliver.
> > >
> > > I due not want messages sent to a Packet BBS destination hoping an
> > > Amateur will pick them up. They need to be sent to a specific
> Amateur
> > > willing to handle traffic.
> > >
> > > :Attached files
> > >
> > > 1. flzipcodes.txt = This is an Alphabetical list of City's with
> their
> > > zip codes for Florida. When determining which City's you can
> deliver.
> > > Please include all zip codes for that City.
> > >
> > > When I compile all the information from various Amateurs and
> associate
> > > Callsigns with zip codes. You will be able to use notepad to
search
> > for
> > > the Amateur closest to the destination.
> > >
> > > 2. SWFDG.GIF = this is the current SWFDG network. The heavy dark
> lines
> > > and yellow areas are proposed.
> > >
> > > 3. Pkt_net.gif = this shows the FPAC network that is connected to
> > > SWFDG.
> > >
> > > 4. Nodelist.htm = this is the SEDAN Network that can be used to
> > connect
> > > to another packet station directly. This might work if there isn't
a
> > > Packet network between you an the destination Amateur.
> > >
> > > Note: I use this Network to connect to an Amateur in Sarasota that
> > > takes NTS traffic.
> > >
> > > 5. n4wfh.txt = My information. Please build yours using notepad
and
> > > attach to a msg back to me. It will make it easier to use later.
> > >
> > > :Information
> > >
> > > More information can be obtained about the Packet Network close to
> you
> > > via:
> > > F.A.D.C.A.: http://www.fadca.org
> > >
> > > More Information can be obtained via the SEDAN network near you
via:
> > > http://www.geocities.com/floridasedan/
> > >
> > > More information about Packet Radio via:
> > > www.packetradio.com
> > >
> > > I will be glad to help any and all.
> > > [email protected]
> > > n4wfh@kf4hfr.#swfl.fl.usa.noam
> > > 941.423.4661 (evening after 18:00)
> > >
> > > After building this list, I'll send it to each participate.
> > > I'm always open for suggestions to make this procedure work more
> > > efficiently. The primary goal being to deliver, accurately, via
> > Amateur
> > > Radio, NTS traffic to it's destination in the shortest time
period.
> > >
> > > 73, Bob N4WFH
> > >
> > > [email protected]
> > > n4wfh@kf4hfr.#swfl.fl.usa.noam
> > > Peace River Repeater Asso. (Webmaster)
> > > Home page: http://home1.gte.net/res04c83/prra.htm
> > > F.A.D.C.A.: http://www.fadca.org
> > > SkyWarn CH-176
> > > EL87vb
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > > --- StripMime Report -- processed MIME parts ---
> > > multipart/alternative
> > > text/plain (text body -- kept)
> > > text/html
> > > 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
> > >
> >
> >
> > _______________________________________________
> > FADCA mailing list
> > [email protected]
> > http://mailman.qth.net/mailman/listinfo/fadca
> >
>
>
> ---
> Outgoing mail is certified Virus Free. signed by jdaughtry
> Checked by AVG anti-virus system (http://www.grisoft.com).
> Version: 6.0.455 / Virus Database: 255 - Release Date: 2/13/03
>
> _______________________________________________
> FADCA mailing list
> [email protected]
> http://mailman.qth.net/mailman/listinfo/fadca