[arm-allstar] The Node is Working!!!!

[Lu Vencl]

This happened to me two years ago. I noticed one morning  that I could not reach my devices on my 1 gig fiber. That’s when I realized my public IP was not matching the reported WAN ip. I complained to the ISP and they set me up with a free static public IP. So worth a try. Call, complain, and threaten to leave and they will likely give it to you. Hopefully. 
They are doing this as most users don’t need a public IP. But those that do end up getting it. The approach (although I don’t agree with it as they never notified me) helps preserve IP’s. 
Lu
KA4EPS


> On Feb 6, 2022, at 6:18 PM, Richard Harkins WØFH via ARM-allstar <arm-allstar at hamvoip.org> wrote:
> 
> Many rural ISPs are doing something called double NAT. There's actually
> another router in front of yours. In one installation we worked on, the
> router was actually inside the wireless ISP antenna. Unless the ISP will
> forward the ports through their router, you're sunk.
> 
> The easiest way to tell if this is the case is to look at the IP address
> assigned to the internet (WAN) side of YOUR router. If there is no double
> NAT, the IP address in your router will match the IP address  you get when
> you go to the website https://whatismyipaddress.com/.
> 
> If the IP address on the internet (WAN) side of YOUR router is in one of
> these ranges:
> Class A: 10.0. 0.0 to 10.255. 255.255.
> Class B: 172.16. 0.0 to 172.31. 255.255.
> Class C: 192.168. 0.0 to 192.168. 255.255.
> 
> You are double NATed.
> 
> Rick W0FH
> 
>> On Sun, Feb 6, 2022 at 1:33 PM "Steve Bosshard (NU5D) via ARM-allstar" <
>> arm-allstar at hamvoip.org> wrote:
>> 
>> It is working - I was told by one of the folks here that a Hamvoip /
>> Allstarlink Node should be able connect to Echolink by forwarding the
>> appropriate ports in my router on my home non-static IP connection.  I
>> did so.  I spent several hours on a couple of telephone conversations -
>> talk you through, checking *.conf files - and after each go around,
>> when I attempted to connect to Echolink - "LINK CONNECTION FAILED"
>> 
>> It was suggested that I probably corrupted the echolink program on the
>> SD card - so I re-imaged and re-setup.  Even changed from my wired
>> internet provider to my cellular mobile hotspot - same story.
>> 
>> The crux is that I could not make an Allstarlink Node to Echolink
>> connection by CLI, Supermon, or OTA,  (and as I expected) vice versa.
>> Allstarlink node connections were trouble free.
>> 
>> So, for a mere $10/month, on top of a very costly (rural internet has
>> little competition - 10 down 1.5 up $60/mo) connection,  The ISP sold me
>> a Static IP with port forwarding.  10 Minutes Later -
>> http://52.128.62.134/supermon/link.php?nodes=559820 and all is well.
>> 
>> I wish I knew whether mine was a unique problem with my ISP or if this
>> is common.  I would hate for someone else to have to look for something
>> amiss when everything was working as advertised, hence this query.
>> 
>> So, the question I have, is "should an Allstarlink Node, connected to a
>> non-static ip garden variety home internet service, be able to connect
>> to an Echolink Node ?"
>> 
>> That said, HamVoip and Allstarlink looks like a great platform and I am
>> very grateful for the folks who were so willing to help.  73, steve nu5d
>> 
>> --
>> ✞  ΙΧΘΥΣ
>> _______________________________________________
>> 
>> 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