[arm-allstar] Inconsistent IP addresses - node doesn´t connect

[David McGough]

Hi Nathanael,

Okay about Columbia.  I suspect your mobile provider is using CGNAT
(Carrier Grade NAT)---that would likely explain why your IPv4 address is
constantly changing.  Without a VPN, AllStar certainly won't work, where
the address is regularly changing. You may even have problems getting a
VPN to work.  Or, you may have to find a local VPN provider who knows how
to interface mobile provider.

Another question is:  Are you only wanting to connect to a specific node 
back in the USA, or have generalized AllStar connectivity to any public 
node?  If you're only wanting connectivity to a small fixed group of 
nodes, you might try setting up your own VPN, first.  In this scenario, 
I'd probably try zerotier first, since it dynamically configures a lot 
of "gory details" and is VERY easy to deploy.


73, David KB4FXC




On Wed, 7 Jul 2021, Hotmail wrote:

> Hi David,
>     One more question… does it make sense that the public IP address changes very rapidly when using a mobile phone hotspot? I’m sorry if I’m asking dumb questions. I am trying to learn more about all of the networking side of things because I am not well educated in this area.
> Thanks again,
> Nathanael AD8GP
> 
> > On Jul 7, 2021, at 10:57 AM, David McGough <kb4fxc at inttek.net> wrote:
> > 
> > 
> > Hi Nathanael,
> > 
> > Where are you geographically located???  The check_connect.sh script seems 
> > to be showing a public IP address of: 191.156.32.152   ....Is that 
> > correct??  Are you using a VPN or are you in Columbia?
> > 
> > First, for node 55023, none of your IPv4 public addresses are the same??? 
> > For example:  191.156.41.17, 191.156.42.43, 191.156.32.152  ...Note that 
> > all the public addresses match on node 53642.
> > 
> > Second, various IP addresses in those IP subnets are on public 
> > blocklists, such as:
> > 
> > https://www.abuseipdb.com/check/191.156.41.17
> > https://www.abuseipdb.com/check/191.156.32.152
> > 
> > 
> > Something very odd is going on with that node, and this is likely why 
> > you're unable to successfully register.  Try obtaining an IPv4 address 
> > not on any blocklists and see if you're able to register.
> > 
> > 
> > 73, David KB4FXC
> > 
> > 
> >> On Wed, 7 Jul 2021, "Nathanael Griesert via ARM-allstar" wrote:
> >> 
> >> Hello,
> >>                I´m limping along trying to figure out why my new node 55023 will not connect, and as I have mentioned in a previous post, I suspect that using my iPhone hotspot as the internet connection has something to do with it. I have tried to see what my public IP address reports back as using three different methods. For my new node each method produces a different result, but for my old functioning node all methods produce the same IP (see tests below).
> >> 
> >>                Can anyone please help me understand why this is happening? And how I can fix it while still using my iPhone hotspot as a connection to the internet? If you know of an old post somewhere that explains this so that I can go read about it and not take up your time I really appreciate that too!
> >> 
> >> Best Regards,
> >> Nathanael Griesert AD8GP
> >> 
> >> 
> >> New Node 55023  (problem child)  external IP checks:
> >> 
> >> Method 1
> >> [root at MBP2013 sbin]# nslookup myip.opendns.com. resolver1.opendns.com
> >> Server:         resolver1.opendns.com
> >> Address:        208.67.222.222#53
> >> 
> >> Non-authoritative answer:
> >> Name:   myip.opendns.com
> >> Address: 191.156.41.17
> >> 
> >> Method 2
> >> [root at MBP2013 sbin]# check_reg.sh
> >> 
> >> Node - 55023 at IP address- 191.156.42.43, Port- 4569 is "Registered" at Server
> >> IP- 162.248.92.131 (register-central.allstarlink.org.), Port- 4569
> >> 
> >> DNS lookup returns - -ER|TIMEOUT
> >> 
> >> Method 3
> >> [root at MBP2013 sbin]# check_connect.sh
> >> 
> >>                Check Internet Connectivity
> >> 
> >>        Your local IP address is - 172.20.10.6
> >>        Your public IP address is - 191.156.32.152
> >> 
> >>        Current nameserver(s)
> >> 
> >>        nameserver 127.0.0.1
> >> 
> >> OLD Node 53642 (old faithful) external IP checks:
> >> 
> >> Method 1
> >> [root at moseslink1 sbin]# nslookup myip.opendns.com. resolver1.opendns.com
> >> Server:         resolver1.opendns.com
> >> Address:        208.67.222.222#53
> >> 
> >> Non-authoritative answer:
> >> Name:   myip.opendns.com
> >> Address: 198.254.80.95
> >> 
> >> Method 2
> >> [root at moseslink1 sbin]# check_reg.sh
> >> 
> >> Node - 53642 at IP address- 198.254.80.95, Port- 4569 is "Registered" at Server
> >> IP- 162.248.92.131 (register-central.allstarlink.org.), Port- 4569
> >> 
> >> DNS lookup returns - +OK|radio at 198.254.80.95:4569/53642,198.254.80.95
> >> 
> >> Method 3
> >> [root at moseslink1 sbin]# check_connect.sh
> >> 
> >>                Check Internet Connectivity
> >> 
> >>        Your local IP address is - 192.168.15.192
> >>        Your public IP address is - 198.254.80.95
> >> 
> >> 
> >> _______________________________________________
> >> 
> >> 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
> >> 
> > 
>