[arm-allstar] SHARI node - working again

Thu May 19 12:16:59 EDT 2022

My pal let me know that he reconnected all the cables to the SHARInode and that now it is working correctly again.I suspect the RJ45 cable was inserted too loosely - but we will never know.
Thanks for all the troubleshooting ideas from the group.73 de K2HJnode 55511John Hysell

    On Thursday, May 19, 2022, 12:00:05 PM EDT, arm-allstar-request at hamvoip.org <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: SHARI node stopped connecting with new router and ISP
      (csmart8 at cogeco.ca)
  2. Re: SHARI node stopped connecting with new router and ISP
      (Patrick Perdue)
  3. Re: SHARI node stopped connecting with new router and ISP
      (Michael Webb)
  4. Re: Update 1.7-01 (Ken Arck)
  5. Re: Update 1.7-01 (Patrick Perdue)

----------------------------------------------------------------------

Message: 1
Date: Wed, 18 May 2022 11:53:44 -0400
From: <csmart8 at cogeco.ca>
To: "'ARM Allstar'" <arm-allstar at hamvoip.org>
Subject: Re: [arm-allstar] SHARI node stopped connecting with new
    router and ISP
Message-ID: <027801d86acf$747133a0$5d539ae0$@cogeco.ca>
Content-Type: text/plain;    charset="UTF-8"

Forwarding port 4569 is only for enabling incoming connections.

-----Original Message-----
From: ARM-allstar <arm-allstar-bounces at hamvoip.org> On Behalf Of "John D. Hysell via ARM-allstar"
Sent: May 18, 2022 11:36 AM
To: arm-allstar at hamvoip.org
Cc: John D. Hysell <jdhysell at yahoo.com>
Subject: [arm-allstar] SHARI node stopped connecting with new router and ISP

I built and configured a SHARI nodefor a blind ham friend, and then sent it to him andworked with him to optimize his use of the node.He was doing well with it until recently.
He had to change his home router as well as his internet provider and now hecannot get the node to connect to any other nodes.
I suspect that either his new router is blocking some key port (I had to useNAT to enable incoming connections to port 4569 earlier) OR The new internet provider is blocking something even before the packets hithis router.
Have you any ideas as far as what to look for? Have you heard of this behavior before?
thanks and 73John HysellK2HJ

_______________________________________________

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

------------------------------

Message: 2
Date: Wed, 18 May 2022 12:20:27 -0400
From: Patrick Perdue <borrisinabox at gmail.com>
To: "John D. Hysell via ARM-allstar" <arm-allstar at hamvoip.org>
Subject: Re: [arm-allstar] SHARI node stopped connecting with new
    router and ISP
Message-ID: <6017e554-6bb1-1c53-78c7-ef4fd78b5ab4 at gmail.com>
Content-Type: text/plain; charset=UTF-8; format=flowed

Greetings from another blind SHARI user:

Silly question, but is this SHARI connecting via WiFi?

Of course, the change of router would most likely mean a new SSID and/or 
passphrase, which would break the existing connectivity as defined in 
wpa_supplicant.

Does the node have a local IP address?

If the node has an IP address, does it show up as online on the 
Allstarlink status page?

Remember that you don't need incoming UDP 4569 forwarded to make 
outbound connections. Otherwise, you'd never be able to use a node on 
carrier-grade NAT without a VPN, so I'd start with making sure the node 
is actually connected to the network.

If it is, check it's registration status with check_reg.sh from bash, if 
you (or he) has access to that.

On 5/18/2022 11:35 AM, "John D. Hysell via ARM-allstar" wrote:
> I built and configured a SHARI nodefor a blind ham friend, and then sent it to him andworked with him to optimize his use of the node.He was doing well with it until recently.
> He had to change his home router as well as his internet provider and now hecannot get the node to connect to any other nodes.
> I suspect that either his new router is blocking some key port (I had to useNAT to enable incoming connections to port 4569 earlier)
> OR
> The new internet provider is blocking something even before the packets hithis router.
> Have you any ideas as far as what to look for??Have you heard of this behavior before?
> thanks and 73John HysellK2HJ
>
> _______________________________________________
>
> 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

------------------------------

Message: 3
Date: Wed, 18 May 2022 12:17:25 -0500
From: Michael Webb <mike.wg5eek at gmail.com>
To: ARM Allstar <arm-allstar at hamvoip.org>
Subject: Re: [arm-allstar] SHARI node stopped connecting with new
    router and ISP
Message-ID:
    <CALBTELSmfZkkt5NEn6e_1_RdconyHx2YcSa0_FOoYNo8Y3HJRw at mail.gmail.com>
Content-Type: text/plain; charset="UTF-8"

Make sure DHCP is enabled as well. If you want a static IP, it's best to
set it at the router. I've had my node set to static and even though it got
an IP address, it would not connect to the internet, could not even ping
google.com

On Wed, May 18, 2022, 12:00 PM "Patrick Perdue via ARM-allstar" <
arm-allstar at hamvoip.org> wrote:

> Greetings from another blind SHARI user:
>
> Silly question, but is this SHARI connecting via WiFi?
>
> Of course, the change of router would most likely mean a new SSID and/or
> passphrase, which would break the existing connectivity as defined in
> wpa_supplicant.
>
> Does the node have a local IP address?
>
> If the node has an IP address, does it show up as online on the
> Allstarlink status page?
>
> Remember that you don't need incoming UDP 4569 forwarded to make
> outbound connections. Otherwise, you'd never be able to use a node on
> carrier-grade NAT without a VPN, so I'd start with making sure the node
> is actually connected to the network.
>
> If it is, check it's registration status with check_reg.sh from bash, if
> you (or he) has access to that.
>
>
> On 5/18/2022 11:35 AM, "John D. Hysell via ARM-allstar" wrote:
> > I built and configured a SHARI nodefor a blind ham friend, and then sent
> it to him andworked with him to optimize his use of the node.He was doing
> well with it until recently.
> > He had to change his home router as well as his internet provider and
> now hecannot get the node to connect to any other nodes.
> > I suspect that either his new router is blocking some key port (I had to
> useNAT to enable incoming connections to port 4569 earlier)
> > OR
> > The new internet provider is blocking something even before the packets
> hithis router.
> > Have you any ideas as far as what to look for? Have you heard of this
> behavior before?
> > thanks and 73John HysellK2HJ
> >
> > _______________________________________________
> >
> > 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

------------------------------

Message: 4
Date: Wed, 18 May 2022 15:03:30 -0700
From: Ken Arck <ken at arcomcontrollers.com>
To: ARM Allstar <arm-allstar at hamvoip.org>
Subject: Re: [arm-allstar] Update 1.7-01
Message-ID: <mailman.1990.1652920063.2763.arm-allstar at hamvoip.org>
Content-Type: text/plain; charset="iso-8859-1"; format=flowed

Out of curiosity, are the any plans for HamVoip on x86 or x86_64 platforms?

Ken

At 05:32 AM 5/18/2022, you wrote:

>Hi Larry and Everyone,
>
>Updates are re-enabled as of this morning and all looks good.
>
>These updates resolve booting and functional issues with the very latest
>RPi4B v1.5 and RPiZ2W boards.
>
>Another announcement will be out soon.
>
>
>73, David K4FXC
>
>
>On Mon, 16 May 2022, "David McGough via ARM-allstar" wrote:
>
> >
> > Hi Larry,
> >
> > I've temporarily suspended the update, I realized one more feature needs
> > integration.  I expect to re-enable updates within the next 24 hours.
> >
> > BTW, this update includes a new SD flash image, which resolves the RPi4B
> > v1.5 boot issues, RPiZ2W issues, etc.
> >
> > I'll make an announcement on Tuesday.
> >
> > 73, David K4FXC
> >
> >
> > On Mon, 16 May 2022, "Larry Mollica via ARM-allstar" wrote:
> >
> > >
> > Already having Hamvoip version 1.6-21 running 
> on several systems for a while, just now went 
> to update another remote system. Surprise, it got:
> > ??? RPi2-3-4 Version 1.7-01 Allstar - May 15, 2022 - K4FXC
> >
> > Well okay. Wanting to test that on my home 
> system, I tried update on it and it decided there was nothing to do, still on:
> > ??? RPi2-3-4 Version 1.6-21 Allstar - January 
> 29, 2021 - KB4FXC                ???
> >
> > Both systems are Rpi 3B. I???ve tried the 
> update twice on the home system and it knows nothing about 1.7
> > Seems weird. Did the 1.7 update get rolled back or something?
> >
> > Thanks
> > LM
> >
> >
> >
> > <snip>
> >
> > _______________________________________________
> >
> > 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

------------------------------------------------------------------------------
President and CTO - Arcom Controllers
Makers of repeater controllers and accessories
Phone: (503) 678 6182
https://www.arcomcontrollers.com/
Authorized Dealers for Kenwood and Telewave.
We offer complete turn-key repeater packages!
"We don't just make 'em. We use 'em!"
[]

------------------------------

Message: 5
Date: Wed, 18 May 2022 22:43:58 -0400
From: Patrick Perdue <borrisinabox at gmail.com>
To: Ken Arck via ARM-allstar <arm-allstar at hamvoip.org>
Subject: Re: [arm-allstar] Update 1.7-01
Message-ID: <5ac7f40c-1cd0-d682-6801-a4338003f27f at gmail.com>
Content-Type: text/plain; charset=UTF-8; format=flowed

I'd sure love for that to be the case.

I recently got a Raspberry Pi installed in a datacenter for running 
HamVoIP. I want to deploy at a couple of other locations, but Pi's 
aren't easy to get, even for those types. X86/64 is plentiful.

On 5/18/2022 6:03 PM, "Ken Arck via ARM-allstar" wrote:
> Out of curiosity, are the any plans for HamVoip on x86 or x86_64 
> platforms?
>
> Ken
>
>
> At 05:32 AM 5/18/2022, you wrote:
>
>> Hi Larry and Everyone,
>>
>> Updates are re-enabled as of this morning and all looks good.
>>
>> These updates resolve booting and functional issues with the very latest
>> RPi4B v1.5 and RPiZ2W boards.
>>
>> Another announcement will be out soon.
>>
>>
>> 73, David K4FXC
>>
>>
>> On Mon, 16 May 2022, "David McGough via ARM-allstar" wrote:
>>
>> >
>> > Hi Larry,
>> >
>> > I've temporarily suspended the update, I realized one more feature 
>> needs
>> > integration.? I expect to re-enable updates within the next 24 hours.
>> >
>> > BTW, this update includes a new SD flash image, which resolves the 
>> RPi4B
>> > v1.5 boot issues, RPiZ2W issues, etc.
>> >
>> > I'll make an announcement on Tuesday.
>> >
>> > 73, David K4FXC
>> >
>> >
>> > On Mon, 16 May 2022, "Larry Mollica via ARM-allstar" wrote:
>> >
>> > >
>> > Already having Hamvoip version 1.6-21 running on several systems 
>> for a while, just now went to update another remote system. Surprise, 
>> it got:
>> > ??? RPi2-3-4 Version 1.7-01 Allstar - May 15, 2022 - K4FXC
>> >
>> > Well okay. Wanting to test that on my home system, I tried update 
>> on it and it decided there was nothing to do, still on:
>> > ??? RPi2-3-4 Version 1.6-21 Allstar - January 29, 2021 - 
>> KB4FXC??????????????? ???
>> >
>> > Both systems are Rpi 3B. I???ve tried the update twice on the home 
>> system and it knows nothing about 1.7
>> > Seems weird. Did the 1.7 update get rolled back or something?
>> >
>> > Thanks
>> > LM
>> >
>> >
>> >
>> > <snip>
>> >
>> > _______________________________________________
>> >
>> > 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
>
> ------------------------------------------------------------------------------ 
>
> President and CTO - Arcom Controllers
> Makers of repeater controllers and accessories
> Phone: (503) 678 6182
> https://www.arcomcontrollers.com/
> Authorized Dealers for Kenwood and Telewave.
> We offer complete turn-key repeater packages!
> "We don't just make 'em. We use 'em!"
> []
>
>
> _______________________________________________
>
> 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

------------------------------

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 96, Issue 23
*******************************************