[arm-allstar] HamVoIP on T-Mobile home service

[Joe Moskalski]

>From what it sounds like to me is the external public IP address of the
network on T Mobiles end changed. This will cause your node in the allstar
database now to be invalid until all the nodes you are trying to connect to
update their database file. This is normally done on a timed basis using a
cron job in linux. My guess is, after a day or two the nodes your are
trying to connect to will update their database file and will allow you to
connect because they can authenticate you as a registered node again.

On Mon, Oct 17, 2022, 12:37 PM "Patrick Perdue via ARM-allstar" <
arm-allstar at hamvoip.org> wrote:

> Yes, that was done. The specialist, at least the one we got, had as much
> of a clue as the CSR people.
>
> They said something like "check the network requirements of whatever you
> are trying to connect to and call us back. There are no flags on your
> account. Have a nice day."
>
>
> On 10/17/2022 11:07 AM, "Greg Stahlman via ARM-allstar" wrote:
> > Because 90% of the CSR calls are something simple like a power cycle or
> > cable connections, they , nor anyone else's CSR will have a clue.  The
> thing
> > to do is ask for a "specialist".  They have people they can transfer you
> to
> > that are WAY more helpful.  If you call, just tell them you have checked
> all
> > connections and have problems connecting to specific IP addresses and you
> > want to talk to a specialist.  The ones I have spoken to are VERY good!
> > Wprth the wait usually.
> >
> > -----Original Message-----
> > From: ARM-allstar [mailto:arm-allstar-bounces at hamvoip.org] On Behalf Of
> > "Patrick Perdue via ARM-allstar"
> > Sent: Sunday, October 16, 2022 6:24 PM
> > To: Don Backstrom - AA7AU via ARM-allstar <arm-allstar at hamvoip.org>
> > Cc: Patrick Perdue <borrisinabox at gmail.com>
> > Subject: [arm-allstar] HamVoIP on T-Mobile home service
> >
> > Greetings:
> >
> > Today, I was helping someone who is using T-Mobile's 5G home internet
> > service with a clear node. Everything was working fine until just a few
> days
> > ago, but then they were suddenly unable to connect to most nodes. A few
> > worked here and there, but mostly not. Everything was auto-congesting.
> Any
> > DNS query, regardless of what server was used, took almost exactly 5
> > seconds. Interestingly, the clear node seems to have
> > 1.1.1.1 set up as the default resolver. I tried quad 9, a couple of root
> > nameservers, and 127.0.0.1. None of that made any difference.
> >
> > No ICMP, so couldn't ping out, either. I tried switching from DNS to flat
> > file lookup, but that didn't help. I eventually solved the problem by
> > routing his connection through a Wireguard VPN. They have the same
> problem
> > when using their phone as a hotspot.
> >
> > I was doing all this remotely, so I have no idea about what hardware is
> > being used as the gateway.
> >
> > Just wondering if anyone else has seen this specifically with T-Mobile.
> > Naturally, their CSR's don't have a clue.
> >
> >
> > 73
> >
> > N2DYI
> >
> > _______________________________________________
> >
> > 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
> _______________________________________________
>
> 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
>