[arm-allstar] Node not starting

[Doug Crompton]

Robby,

 We need more information. Are you using Hamvoip software? Is this a new
problem or are you just starting out? Are you registering? What happens
when you DTMF to connect? Are you getting a beep? A cannot connect message?

Login to your system, In the main menu select start bash shell. At the
Linux prompt type   check_reg.sh and hit return. You should see that you
are registered. If not try shutting down your system off for about 5
minutes and boot back up and look again. If it is not registering let us
know your node number.

You can also go into the client from the menu and there if you keyup and
press your DTMF keys you will see them decoded on the screen. You should
see proper decoding for each character. If not check your levels in
simpleusb.

Also in the future please start a new subject (topic) instead of hijacking
an existing one. I changed the subject.


*73 Doug*

*WA3DSP*

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


On Mon, Jan 20, 2020 at 10:26 PM "T L Roberson via ARM-allstar" <
arm-allstar at hamvoip.org> wrote:

> I’m having problems with getting my raspberry pi to connect to a node any
> suggestions from anyone Robby/KK5QT
>
>
> Sent from AT&T Yahoo Mail for iPhone
>
>
> On Monday, January 20, 2020, 4:42 PM, Patrick Perdue via ARM-allstar <
> arm-allstar at hamvoip.org> wrote:
>
> Likewise, I'm running a stock ASL node (50631) on a $5/month Linode,
> which is working great. I'm pretty sure all connected nodes are hamvoip
> distributions. While I have a Gigabit symmetric internet connection at
> my house, I feel better about putting a hub on a higher tear of service
> just because ISPs generally tend to peer better with data centers than
> home connections, regardless of how much available bandwidth they may have.
>
> I keep a couple of nodes connected with the permanent connection method,
> no need for Cron jobs. If the connection drops, it will be
> re-established when things work again, at least this has been my
> experience.
>
>
> On 1/20/2020 2:46 PM, "KY220GROUP--- via ARM-allstar" wrote:
> > Mike I'm running my hub #49799 at vultr.com. Works great for me for
> five bucks a month. I don't have to worry about firewalls and incoming
> connections to either of my repeaters. I set a cron job to auto-connect
> from each repeater node to the hub every 30 minutes in case of a problem,
> most connects are done on the hub for distribution to my 220 and 440
> repeaters and soon my 2 meter repeater. Echolink is ran on the hub also
> with the call kk4wh-r. It works well for a hub at places where you use a
> cell connection or can only have an outbound connection. I also think that
> the RPi hub that Doug mentioned is an excellent idea.
> >
> > 73
> > Tim Webb - KK4WH(606)909-2094
> >
> >      On Saturday, January 18, 2020, 11:24:28 PM EST, Doug Crompton via
> ARM-allstar <arm-allstar at hamvoip.org> wrote:
> >
> >  Mike,
> >
> >  You could do it with a second node on that server but personally I like
> to
> > separate the HW especially as cheap as it is. In this case the cost of
> > another Pi and power supply. One would run your repeater and the other
> the
> > hub that could be connected to the repeater if desired. This also gives
> > better redundancy and is easier to maintain.
> >
> >
> > *73 Doug*
> >
> > *WA3DSP*
> >
> > *http://www.crompton.com/hamradio <http://www.crompton.com/hamradio>*
> >
> > On Sat, Jan 18, 2020 at 9:59 PM "Mike Sullivan via ARM-allstar" <
> > arm-allstar at hamvoip.org> wrote:
> >
> >> I'm planning on NNX'ing our club's repeater node and making x0 a
> headless
> >> hub, with x1 as the repeater. The hub will be used to link the area
> nodes
> >> as we bring them online for nets and such. What is the easiest way to go
> >> about adding a node that is just acting as a connection point? Or would
> I
> >> be better off using a second Pi for the connection?
> >>
> >> Mike
> >> _______________________________________________
> >>
> >> 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/4 web page - http://hamvoip.org
> >>
> > _______________________________________________
> >
> > 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/4 web page - http://hamvoip.org
> >
> > _______________________________________________
> >
> > 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/4 web page - http://hamvoip.org
> _______________________________________________
>
> 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/4 web page - http://hamvoip.org
>
>
>
> _______________________________________________
>
> 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/4 web page - http://hamvoip.org