[FADCA] Network Status E-Central Flroida

[Chuck Hast]

On 6/17/05, bud thompson <budt at cfl.rr.com> wrote:
> 
> ----- Original Message -----
> From: "Chuck Hast" <wchast at gmail.com>
> To: "Florida Amateur Digital Communication Association"
> <fadca at mailman.qth.net>
> Cc: "DICK K4FUY SEM CO EC" <dickfess at juno.com>; "JAX BBS KC4OUA"
> <willy3jax at covad.net>; "Mike Mullikin W8EHH" <w8ehh at cfl.rr.com>; "earl
> leach" <wx4j1 at comcast.net>; "Dave N4GMU" <n4gmu at bellsouth.net>; "Charlie
> N3PPC" <ccrook at cfl.rr.com>
> Sent: Friday, June 17, 2005 08:45
> Subject: Re: [FADCA] Network Status E-Central Flroida
> 
> 
> On 6/17/05, bud thompson <budt at cfl.rr.com> wrote:
> > Friday 0820
> >
> > The network is back to 'normal' working from the Orlando Switch through to
> > Jacksonville. (Thanks to KC4OUA for fixing the NTS X1-J node!)  Also, this
> >  >despite the fact that my retuning the 9.6kb UHF Backbone radio at Orlando
> > initially appeared to make things worse!  The link seems to be about the
> > same now, >so not sure about my initial impressions after the tuning.
> 
> Do the two switches digipeat through that node or does a user have to
> connect to
> the node and issue a connect through the neighbor swich to get to the
> destination?
> Sounds like that node would be a great place to test a Linux switch running
> both
> FPAC and NetRom, it does IP so that takes care of the only other thing taht
> X1-J
> brings to the table, and it runs FPAC so it gives a added ability to the
> site.
> 
> --
> Chuck Hast
> 
> * * *
> 
> Chuck-  The only present route between St. Augustine and JAX is via the STA
> LAN to the NTS X1-J node.  That will change soon when we get an FPAC at
> Orange Park and perhaps another at JAX. (I think that is what is planned.)
> I belive that Russ and Bill KC4OUA are planning something like you are
> recommending.


That is good, I think the more protocols we have to play with the more people
will come back and play. Some people lilke NetRom, with Linux we can give
them NR. We can also give them Flex, and several other callsign routed
protocols. WP gives you the ability to route a call based on callsigns with
FPAC Linux, but the routing is address based so it is much simpler and does
not demand near as much memory to store network data as the callsign
based networks do.

> 
> Meanwhile I have two secret weapons - David KO3O and Dan WH6A, both in
> Volusia County who will be working with N3PPC to get LINUX FPAC working in
> E. Central Florida.  Once it works on the bench, we'll  make the change
> first at Orlando while here at my ATH where we have an internet connection
> and can confirm compatibility with DOS FPAC at DeLand.  Then we'll change
> over DeLand to LINUX FPAC.

Yes Dan has already been passing info along we are trying to get the fpacuser
login to Bills machine to drop direct to the app like it does on mine and now
Bernard's machine over in Paris. For some reason it refuses to cooperate, we
shall have to see what it is, I just changed a few other things but
still get the
failure when I try to log into it.


> 
> Looking forward to joining the LINUX FPAC team!
> 

Yep and once you do you will wonder why you did not do it sooner,
I know that the learning curve is a different direction than what you
are used to but once you start getting familiar with it you really will
start to like it.

Think of it as a toolbox with thousands of tools to use, the trick is
to figure out how to select the ones you need and use them. Makes
for a very configurable machine.

Things like switches and fileservers do not need a GUI, so you run
such devices with only that needed to make the work right and that
way conserve space, memory and machine cycles for real stuff like
moving packets. 


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