[arm-allstar] Advantages of a hosted hub node

Sat Jun 15 13:44:48 EDT 2019

Joshua,

  The only reason in my mind to have a server at a data center is if you do
not have good or any Internet connectibility. This is the case for more
people in the US than most know. Obviously not in major metropolitan areas
but the US is way behind in both Internet connectivity and quality. Many
other countries surpass us in getting good Internet to everyone that wants
it.  So in those cases the only alternative is to put the server somewhere
that has good Internet like a data center. The Pi farm has that in mind.
Why have a PC running Allstar virtually, which BTW does not always work
that well, when you can have a real Pi server running there with the best
Internet possible. So that is the reason for the Pi farm. If you have
Internet and are not having issues with connectivity that you don't need a
node at a data center. I think in the past, like 10 or more years ago, it
was the norm to have large hubs run from data centers. This is no longer
the case unless you are out in the sticks and have little or no Internet.
Unfortunately that mindset still lingers.

*73 Doug*

*WA3DSP*

*http://www.crompton.com/hamradio <http://www.crompton.com/hamradio>*

On Sat, Jun 15, 2019 at 12:39 PM "Joshua Nulton via ARM-allstar" <
arm-allstar at hamvoip.org> wrote:

> I agree most are interested for the "social" aspects. I can think of one
> major advantage and that is people that can not forward their ports or want
> AIX access on the road. They can have their normal node connect
> persistently to their "hub" and forward their DTMF commands to the remote
> node, making their personal node more or less act as a proxy to bypass
> connectivity issues.
>
> I guess I am just fishing for more reasons to be interested in the Pi-Farm
> Doug, where has your marketing intuition gone? haha :)
>
> What would be the advantages of renting space on the farm? I am not being
> negative, I really am trying to underatand the idea. :)
>
> KG5EBI
>
> On Sat, Jun 15, 2019, 11:00 AM <arm-allstar-request at hamvoip.org> wrote:
>
> > Send ARM-allstar mailing list submissions to
> >         arm-allstar at hamvoip.org
> >
> > To subscribe or unsubscribe via the World Wide Web, visit
> >         http://lists.hamvoip.org/cgi-bin/mailman/listinfo/arm-allstar
> > or, via email, send a message with subject or body 'help' to
> >         arm-allstar-request at hamvoip.org
> >
> > You can reach the person managing the list at
> >         arm-allstar-owner at hamvoip.org
> >
> > When replying, please edit your Subject line so it is more specific
> > than "Re: Contents of ARM-allstar digest..."
> >
> >
> > Today's Topics:
> >
> >    1. Re: use an alternate network interface for vpn (David McGough)
> >    2. Re: Installing SSL cert in HamVoIP image (David McGough)
> >    3. Advantages of hosted hub node (Joshua Nulton)
> >    4. Re: Advantages of hosted hub node (Doug Crompton)
> >    5. ERROR[403] chan_echolink.c: (Mike Besemer)
> >    6. Re: ERROR[403] chan_echolink.c: (Doug Crompton)
> >
> >
> > ----------------------------------------------------------------------
> >
> > Message: 1
> > Date: Sat, 15 Jun 2019 09:45:18 -0400 (EDT)
> > From: David McGough <kb4fxc at inttek.net>
> > To: "\"Tony Ross via ARM-allstar\"" <arm-allstar at hamvoip.org>
> > Subject: Re: [arm-allstar] use an alternate network interface for vpn
> > Message-ID:
> >         <Pine.LNX.4.44.1906150943540.26900-100000 at goliath.inttek.net>
> > Content-Type: TEXT/PLAIN; charset=US-ASCII
> >
> >
> >
> > Tony,
> >
> > Did you get this resolved?  If not, I'll send you more info for a
> > solution.
> >
> > 73, David KB4FXC
> >
> >
> >
> > On Thu, 13 Jun 2019, "Tony Ross via ARM-allstar" wrote:
> >
> > > Sorry for all the "???..." clutter that resulted from a use of
> > > fixed-width font. To re-phrase my request:
> > >
> > > How to use the ztly5vn64v 192.168.192.142 vpn interface, instead of the
> > > wlan0 192.168.1.30 interface, please.
> > >
> > > _______________________________________________
> > >
> > > ARM-allstar mailing list
> > > ARM-allstar at hamvoip.org
> > > http://lists.hamvoip.org/cgi-bin/mailman/listinfo/arm-allstar
> > >
> > > Visit the BBB and RPi2/3 web page - http://hamvoip.org
> > >
> >
> >
> >
> > ------------------------------
> >
> > Message: 2
> > Date: Sat, 15 Jun 2019 09:59:39 -0400 (EDT)
> > From: David McGough <kb4fxc at inttek.net>
> > To: "\"Brad Trogdon via ARM-allstar\"" <arm-allstar at hamvoip.org>
> > Cc: Brad Trogdon <Brad at trogdon.org>
> > Subject: Re: [arm-allstar] Installing SSL cert in HamVoIP image
> > Message-ID:
> >         <Pine.LNX.4.44.1906150950120.26900-100000 at goliath.inttek.net>
> > Content-Type: TEXT/PLAIN; charset=US-ASCII
> >
> >
> > Brad,
> >
> > Take a look at the acme-tiny software. It's very easy to use for
> > generating single-site (not wildcard)  certificates.  If you need info
> for
> > configuring apache/tls in the HamVoIP distro, send me a follow-up
> message.
> >
> > Here is the software. The instructions are on this page, too:
> >
> > https://github.com/diafygi/acme-tiny
> >
> > I'm running apache/tls on several RPi3 systems and it works great.
> >
> >
> > 73, David KB4FXC
> >
> >
> > On Fri, 14 Jun 2019, "Brad Trogdon via ARM-allstar" wrote:
> >
> > > Hello all,  I anticipate this is kind-off off topic but is specific to
> > the
> > > HamVoIP image.
> > >
> > > I am current in updates and wanting to install a SSL cert on the
> > Raspberry
> > > Pi which is running my node.  I have been directed to Certbot.com and
> > they
> > > have step by step instructions specific to OS and WebServer.  In our
> case
> > > Apache and Arch Linux.  (URL to Page:
> > > https://certbot.eff.org/lets-encrypt/arch-apache)
> > >
> > > I fail at Step 1 trying to install the packages.
> > >
> > > sudo pacman -S certbot certbot-apache
> > >
> > > Results in error:
> > >
> > > error: target not found: certbot
> > > error: target not found: certbot-apache
> > >
> > > I do not want to break my ability to maintain updates for HamVoIP and
> > > thought I would ask the experts before proceeding.
> > >
> > > Thanks in advance for your wisdom.
> > >
> > > -Brad
> > > ~~
> > > _______________________________________________
> > >
> > > ARM-allstar mailing list
> > > ARM-allstar at hamvoip.org
> > > http://lists.hamvoip.org/cgi-bin/mailman/listinfo/arm-allstar
> > >
> > > Visit the BBB and RPi2/3 web page - http://hamvoip.org
> > >
> >
> >
> >
> > ------------------------------
> >
> > Message: 3
> > Date: Sat, 15 Jun 2019 20:59:55 +0700
> > From: Joshua Nulton <kg5ebi at gmail.com>
> > To: arm-allstar at hamvoip.org
> > Subject: [arm-allstar] Advantages of hosted hub node
> > Message-ID:
> >         <
> > CAOpEAy4kawustLBR_sByjNNQTSN78mYHSj9ASNM+SndtT7ifZQ at mail.gmail.com>
> > Content-Type: text/plain; charset="UTF-8"
> >
> > I know some have said an off site hosted link node could be advantageous
> to
> > those with poor to no internet and I can't wrap my head around that, but
> I
> > am sure there must be numerous advantages to having a hub node. Could
> y'all
> > name as many as you can think of please?
> >
> > Thanks,
> > Jae
> > KG5EBI
> >
> >
> > ------------------------------
> >
> > Message: 4
> > Date: Sat, 15 Jun 2019 11:12:18 -0400
> > From: Doug Crompton <wa3dsp at gmail.com>
> > To: ARM Allstar <arm-allstar at hamvoip.org>
> > Subject: Re: [arm-allstar] Advantages of hosted hub node
> > Message-ID:
> >         <
> > CAMp6vsuteaXnqdurX4FLh0gnQW8YamB++68cUFfomiHWwwsNbQ at mail.gmail.com>
> > Content-Type: text/plain; charset="UTF-8"
> >
> > Joshua,
> >
> > In Allstar people tend to conflate the word "hub" with something special.
> > Maybe it is because on IRLP where you have to ask for permission to be
> > granted and run a reflector.  In Allstar terminology a "hub" is simply a
> > connection point where there are two or more other nodes connected. It is
> > an understanding among a group of people that they will all connect to
> one
> > node.  Anyone can create a "hub" in Allstar. There is nothing special
> about
> > it and no special configuration. As long as you have the Internet
> bandwidth
> > to do it, and in this day and age most do, you can set one up. It is
> more a
> > matter of advertising than anything else. Running hamvoip in turbo mode
> > without any radios a single server could easily handle 60+ connections.
> > There are very few "hubs" that have that many connections and in a case
> > where they might the load can be distributed over more than one server.
> > This is the beauty of Allstar because you have the flexibility to create
> > and do this. Here is Philadelphia I run at least three hubs using 10
> local
> > servers and several remote. There are more than 65 direct connections
> > throughout the world. This is all done on Pi's and on a single Comcast
> > Internet connection.
> >
> >
> > *73 Doug*
> >
> > *WA3DSP*
> >
> > *http://www.crompton.com/hamradio <http://www.crompton.com/hamradio>*
> >
> > On Sat, Jun 15, 2019 at 10:01 AM "Joshua Nulton via ARM-allstar" <
> > arm-allstar at hamvoip.org> wrote:
> >
> > > I know some have said an off site hosted link node could be
> advantageous
> > to
> > > those with poor to no internet and I can't wrap my head around that,
> but
> > I
> > > am sure there must be numerous advantages to having a hub node. Could
> > y'all
> > > name as many as you can think of please?
> > >
> > > Thanks,
> > > Jae
> > > KG5EBI
> > > _______________________________________________
> > >
> > > ARM-allstar mailing list
> > > ARM-allstar at hamvoip.org
> > > http://lists.hamvoip.org/cgi-bin/mailman/listinfo/arm-allstar
> > >
> > > Visit the BBB and RPi2/3 web page - http://hamvoip.org
> > >
> >
> >
> > ------------------------------
> >
> > Message: 5
> > Date: Sat, 15 Jun 2019 11:44:49 -0400
> > From: "Mike Besemer" <mwbesemer at cox.net>
> > To: "ARM Allstar" <arm-allstar at hamvoip.org>
> > Subject: [arm-allstar] ERROR[403] chan_echolink.c:
> > Message-ID: <001501d52391$449ba9e0$cdd2fda0$@cox.net>
> > Content-Type: text/plain;       charset="us-ascii"
> >
> > Been receiving the error below for several days in AST Log.  Echolink
> works
> > fine, so I'm assuming that this is just an issue with a specific Echolink
> > server being unavailable; is that correct?
> >
> > "ERROR[403] chan_echolink.c: connect() failed to connect to the Echolink
> > server server5.echolink.org"
> >
> > 73,
> >
> > Mike
> > WM4B
> >
> >
> >
> >
> >
> > ------------------------------
> >
> > Message: 6
> > Date: Sat, 15 Jun 2019 11:57:53 -0400
> > From: Doug Crompton <wa3dsp at gmail.com>
> > To: ARM Allstar <arm-allstar at hamvoip.org>
> > Subject: Re: [arm-allstar] ERROR[403] chan_echolink.c:
> > Message-ID:
> >         <CAMp6vsu0Ac4wp-KsWtBg--3CW8vYyL0G=
> > yy2wg0gU8bRrAYrNw at mail.gmail.com>
> > Content-Type: text/plain; charset="UTF-8"
> >
> > Mike,
> >
> >  Yes that is correct. We had a discussion about this last week. There
> must
> > be three servers defined in echolink.conf but only one has to actually
> > work. Server5 has been down for awhile now.  You can use server1, 2, and
> 3
> > and that message will go away. That is as long as all of those are
> working.
> > But the bottom line is that as long as one is working and you are getting
> > the data from it all is fine.  You can check that in the client with  -
> > echolink dgdump or dbget.
> >
> >
> > *73 Doug*
> >
> > *WA3DSP*
> >
> > *http://www.crompton.com/hamradio <http://www.crompton.com/hamradio>*
> >
> > On Sat, Jun 15, 2019 at 11:47 AM "Mike Besemer via ARM-allstar" <
> > arm-allstar at hamvoip.org> wrote:
> >
> > > Been receiving the error below for several days in AST Log.  Echolink
> > works
> > > fine, so I'm assuming that this is just an issue with a specific
> Echolink
> > > server being unavailable; is that correct?
> > >
> > > "ERROR[403] chan_echolink.c: connect() failed to connect to the
> Echolink
> > > server server5.echolink.org"
> > >
> > > 73,
> > >
> > > Mike
> > > WM4B
> > >
> > >
> > >
> > > _______________________________________________
> > >
> > > ARM-allstar mailing list
> > > ARM-allstar at hamvoip.org
> > > http://lists.hamvoip.org/cgi-bin/mailman/listinfo/arm-allstar
> > >
> > > Visit the BBB and RPi2/3 web page - http://hamvoip.org
> > >
> >
> >
> > ------------------------------
> >
> > Subject: Digest Footer
> >
> > _______________________________________________
> > ARM-allstar mailing list
> > ARM-allstar at hamvoip.org
> > http://lists.hamvoip.org/cgi-bin/mailman/listinfo/arm-allstar
> >
> >
> > ------------------------------
> >
> > End of ARM-allstar Digest, Vol 61, Issue 12
> > *******************************************
> >
> _______________________________________________
>
> ARM-allstar mailing list
> ARM-allstar at hamvoip.org
> http://lists.hamvoip.org/cgi-bin/mailman/listinfo/arm-allstar
>
> Visit the BBB and RPi2/3 web page - http://hamvoip.org
>