[arm-allstar] Any suggestions??

[Brad Trogdon]

Again thank you to everyone that offered suggestions.  The issue has
been resolved and it was no fault of the Pi or the HamVoIP image :)

Kip's experience was very close..

Issue is the Pi lost internet access..

For those that like details...

The mountain top site has a Microwave network that connects commercial
repeaters (Fleet System servicing 16 states) was disrupted because of
a lightning strike.  Network traffic (local traffic) was rerouted and
the port which I am connected was skipped in the process. (My port is
only access to public internet)  The Pi lost DNS so its Reverse SSH
could not find home.  A few minutes after they corrected routing and a
RF command to Reboot the Pi...    All was back in service!  Woo Hoo!!

Suggestions to everyone using Reverse SSH is to add a script that can
be executed over RF allowing you to remotely reboot the Pi.  In my
case it saved  me 1/2 day driving to the Mountaintop just to pull a
cord to reboot.

73 de W4INT
Lewisville, North Carolina



On Thu, Sep 5, 2019 at 12:00 PM <arm-allstar-request at hamvoip.org> wrote:
>
>
> Message: 1
> Date: Wed, 4 Sep 2019 15:28:53 -0400
> From: Brad Trogdon <Brad at trogdon.org>
> To: arm-allstar at hamvoip.org
> Subject: Re: [arm-allstar] ARM-allstar Digest, Vol 64, Issue 6
> Message-ID:
>
> Will try to answer all questions / Comments in a single sweep  :)
>
> Thanks to all that are trying to help!
>
> >    2. Re: Any suggestions?? (Mike Besemer)
> > What about Supermon?  Does it still work?
> > Wondering if the external IP has changed.
>
> Supermon has never been accessible.  The Pi is in a private network
> that I cannot access from outside.  Public IP address is STATIC and
> unchanged.  This is a Pi issue not network as the other servers and
> repeaters are functioning.
>
> >    3. Re: Any suggestions?? (John Simmons)
> > Do the facts that the time is wrong and SSH doesn't work indicate that
> > the network connection has been lost?
>
> Network is still up.  Just that the Pi refuses connection.
>
> >    4. Re: Any suggestions?? (Andrew Hull KE8HEV)
> > By default, the node will transmit its IP address during the boot up
> > procedure. Does that still work? What IP does it report?
> >
> > Assuming that the node does not plug directly into the public internet, do
> > you have a remote access method to the network at the tower site outside of
> > the node itself?
> >
> > Like NI0K mentioned, the fact that the time is off (by a lot!) indicates to
> > me that the time keeping daemon on the node can't access the time servers
> > anymore... and therefore, the node may not have internet connectivity at
> > all.
>
> Yes, it provides the Public IP address when the Pi Reboots.   I have
> to withold the actual address as its a public IP for a Microwave
> system that provides connectivity for many commercial repeater
> locations.   No, Cannot access any way other than the reverse SSH
> method that has failed.   It was still connected to other repeaters so
> I am sure connectivity is not the issue.  upon reboot I have not
> attempted to reconnect.
>
>
> >    5. Re: Any suggestions?? (Rory Bowers)
>
> The Public address Yes but no way to ping the Pi directly.   Unless
> their is a way to ping the Reverse SSH connection.
>
>
> ------------------------------
>
> Message: 2
> Date: Wed, 4 Sep 2019 18:32:50 -0500
> From: Kipton Moravec <kip at kdream.com>
> To: arm-allstar at hamvoip.org
> Subject: Re: [arm-allstar] Any suggestions??
> Message-ID: <446360bb-e86e-4891-b4fc-2578fbf78900 at kdream.com>
> Content-Type: text/plain; charset=utf-8; format=flowed
>
>  ?That happened to me a few days ago. I did not have my internet
> configured right. It was not able to get out, because the gateway was
> wrong. Fortunately I had another pi I could log into remotely on the
> same lan, then ssh to it to fix the gateway. So I am guessing it is
> internet link or configuration.
>
> Kip
**************