[arm-allstar] echolink issues

[Don Sayler]

Lawrence, it's just the one node.
It had been working perfectly since we brought Allstar up 2 years ago.
This behavior started just a few weeks ago.

On Sun, Oct 23, 2022 at 5:34 AM "Lawrence Roney via ARM-allstar" <
arm-allstar at hamvoip.org> wrote:

> Don,
>
> Sorry to state the obvious, but make sure you are not running more than
> one Echolink  node on your local network (behind the same router).
>
> Even firing up a smartphone (connected to Wi-Fi) or a desktop PC with
> Echolink to test the connection can confuse the Echolink registration
> servers as they will see multiple Echolink nodes coming from the same
> public IP address.
>
> If you want to test the connection, disconnect your smartphone from local
> Wi-Fi on the same network as the Echolink node.  Use cellular data to test
> OR use a proxy on the smartphone app.
>
> Per the Echolink website FAQ:
> Q. Can I run more than one node under the same callsign, or two nodes on
> the same Internet connection?
> Please keep in mind these rules regarding the EchoLink network:
>
> A. Each node logged into the system must have a separate callsign; you
> cannot run two instances of W1XYZ at the same time. Each node MUST be
> running behind its own distinct public IP address. This means that you
> cannot run W1XYZ and W1XYZ-L on the same shared Internet connection at the
> same time, unless you have made special arrangements with your ISP to be
> allocated more than one public address.
>
> Thanks,
>
> Lawrence - N6YFN
>
> _______________________________________________
>
> 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
>