[FADCA] Telpac revisited

[Russell Oder]

Keep working on this, Chuck.


----- Original Message ----- 
From: "Chuck Hast" <wchast at gmail.com>
To: "Florida Amateur Digital Communication Association"
<fadca at mailman.qth.net>
Sent: Friday, October 22, 2004 10:30 PM
Subject: Re: [FADCA] Telpac revisited


> On Fri, 22 Oct 2004 21:50:14 -0400, Bill Sinbine <n4xeo at bellsouth.net>
wrote:
> >
> >
> > Hi All
> >
> > I was looking back at my saved messages looking for something and I came
> > across this old message and felt that it had merit to be re posted since
> > bud and I were just talking about it Wednesday night.
> >
> > With the increase in Telpac stations we need to have the standard for
the
> > quick connects in FPAC...
> >
> >      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?
>
> This standardization is good. I was looking for a FPAC dos config file but
guess
> it is at the EOC!
>
> I did look at the FPAC Linux and it allows for any type of alias, so you
could
> potentially have different CALL signs under the same switch.
>
> Here is the area in the FPAC Linux config file that deals with aliases.
>
> -------------------------- Begin insertion
> -------------------------------------------------
> 5.8.  Alias section
>
>   Alias section is similar to Application section, but maps a new
>   connection to the requested callsign. For instance the user connection
>   F6FBB-3 will be re-routed to F6KRQ-3 address 931501 (the default DNIC
>   of the switch will be used).
>
>   The Alias section will hold one or more Alias blocks. Each block will
>   specify one alias. Use as many blocks as needed in this section.
>
>        #
>        # List of aliases
>        #
>
>        Alias = F6FBB-2
>                Path = F6FBB-2,931501
>        End
>
>        Alias = F6FBB-3
>                Path = F6KRQ-3,931501
>        End
>
> --------------------------- 
End ----------------------------------------------
>
> Now here is the part that is even more interesting and this is
> where I believe the Linux telpac node piece will fall into place.
>
>
> This looks quite similar to the alias part but it actually connects
> you to a particular application.
>
> -------------------------- Begin insertion
> -------------------------------------------------
>   5.5.  Application section
>
>   The Application section includes a list of lines. Each line associates
>   a LINUX application to a callsign. So if the user connects the
>   specified callsign, he will be linked to the LINUX program.
>
>
>        #
>        # Other applications
>        #
>
>        Application
>                F6FBB-1 = /usr/sbin/call_tcp serveur 1022
>        End
> --------------------------- 
End ----------------------------------------------
> If this was the telpac_node app then the user connecting to
> f6fbb-1 would be directed to the telpac_node app on the
> switch, now you no longer need to use a named pipe to
> get there if I understand this correctly.
>
> You could also be connected to many other services such
> as INFO and Wide-INFO (411 and 555)
>
> I am now working on a machine that I can mess up and just
> reboot or reload as I learn the ax.25 and network stuff. I am
> using Debian for it as a large number of the developers are
> amateurs and have worked to make sure all of the code is
> stable and viable.
>
> I have the AX25 stuff running under SuSE but need a separate
> machine really as this is my work machine and need it to do
> paid work, so can not afford to have it lock up or mess up as I
> have done several times while trying to get this stuff to work.
> _______________________________________________
> FADCA mailing list
> FADCA at mailman.qth.net
> http://mailman.qth.net/mailman/listinfo/fadca
>