# Mobile Internet **URL:** \ **Category:** AllStarLink\ **Created:** [October 12, 2024, 7:54pm UTC](https://community.allstarlink.org/t/mobile-internet/22040 "2024-10-12T19:54:43Z")\ **Posts on this page:** 20\ **Page:** 1
**Author:** ![KD5FMU](https://community.allstarlink.org/user_avatar/community.allstarlink.org/kd5fmu/32/2113_2.png) [@KD5FMU](https://community.allstarlink.org/u/KD5FMU)\ **Post date:** [October 12, 2024, 7:54pm UTC](https://community.allstarlink.org/t/mobile-internet/22040/1 "2024-10-12T19:54:43Z")
Hello All, I am having an VERY frustrating issue with mobile internet providers. I have AT&T/Firstnet mobile Hotspot and a T-Mobile Mobile HotSpot. My ASL3 Nodes will connect to them BUT the ONLY node I can get them to connect to is 55553 The Parrot Node in Plano Texas. I can not understand why. I did connect one of my nodes to a Verizon HotSpot of a friend and the connection worked and I was able to connect to any active node. If I were to reach out to AT&T or T-Mobile to discuss possible firewall issues what specifically would I refer to? Ports? DNS? Here is the weird part. If I enter my cloud hub into the node section of my rpt.conf mobile node i.e. 576335 = [radio@198.58.124.150](mailto:radio@198.58.124.150)/576335,NONE and I enter my node into the Cloud server rpt.conf file and they will connect! So Does anyone have ANY idea why I can’t connect? Or What Steps I need to take with the cellular carrier? Any and ALL help is appreciated. 73 DE KD5FMU Freddie Mac [kd5fmu@gmail.com](mailto:kd5fmu@gmail.com) ---
**Author:** ![N8EI](https://community.allstarlink.org/user_avatar/community.allstarlink.org/n8ei/32/4254_2.png) [@N8EI](https://community.allstarlink.org/u/N8EI)\ **Post date:** [October 13, 2024, 12:18am UTC](https://community.allstarlink.org/t/mobile-internet/22040/2 "2024-10-13T00:18:47Z")
For anyone who comes across this later, this is an issue where the AT&T and T-Mobile hotspots are handling web/HTTP traffic differently from IAX traffic. IAX traffic is how nodes link. In this situation, the HTTP registration process causes the registration servers to see one IP while the IAX traffic is using a different one. In this **limited circumstance** , use of IAX-based registration is recommended. > **[IAX-Based Registration - AllStarLink Manual](https://allstarlink.github.io/adv-topics/iaxreg/)** > > AllStarLink Manual ---
**Author:** ![W5SSN](https://community.allstarlink.org/letter_avatar_proxy/v4/letter/w/ecb155/32.png) [@W5SSN](https://community.allstarlink.org/u/W5SSN)\ **Post date:** [October 26, 2024, 2:40pm UTC](https://community.allstarlink.org/t/mobile-internet/22040/3 "2024-10-26T14:40:07Z")
That fixed me up. I am now connecting to nodes!!! For the record I’m on a T-Mobile 5G home internet connection. Thank you for what little hair I have left, 73. Mike - W5SSN ---
**Author:** ![N5AD](https://community.allstarlink.org/user_avatar/community.allstarlink.org/n5ad/32/4127_2.png) [@N5AD](https://community.allstarlink.org/u/N5AD)\ **Post date:** [December 15, 2025, 3:03pm UTC](https://community.allstarlink.org/t/mobile-internet/22040/4 "2025-12-15T15:03:45Z")
I am having EXACTLY this same issue. I followed the instructions given. Now my node does not show registered. I set it up for iax registration and disabled http registration. No registration shows up and now i still cannot connect to other nodes nor can they connect to me. my node is 654580 and recently moved it to the mountaintop repeater site behind a t-mobile hotspot running on an inseego mifi x pro 5g hotspot router. the online documentation for this device says that port forwarding is an option. can anyone smarter than me offer any solution to my issue?’ ---
**Author:** ![N8EI](https://community.allstarlink.org/user_avatar/community.allstarlink.org/n8ei/32/4254_2.png) [@N8EI](https://community.allstarlink.org/u/N8EI)\ **Post date:** [December 15, 2025, 3:41pm UTC](https://community.allstarlink.org/t/mobile-internet/22040/5 "2025-12-15T15:41:08Z")
654580 was seen last online 2025-12-15 09:47 UTC. So if it's been up this whole time, then your Internet is not working properly or you have a bad password. ---
**Author:** ![N8EI](https://community.allstarlink.org/user_avatar/community.allstarlink.org/n8ei/32/4254_2.png) [@N8EI](https://community.allstarlink.org/u/N8EI)\ **Post date:** [December 15, 2025, 3:41pm UTC](https://community.allstarlink.org/t/mobile-internet/22040/6 "2025-12-15T15:41:36Z")
What does `iax2 show registry` report? ---
**Author:** ![N5AD](https://community.allstarlink.org/user_avatar/community.allstarlink.org/n5ad/32/4127_2.png) [@N5AD](https://community.allstarlink.org/u/N5AD)\ **Post date:** [December 15, 2025, 3:52pm UTC](https://community.allstarlink.org/t/mobile-internet/22040/7 "2025-12-15T15:52:49Z")
host [2607:7700:0:49::3415:a9c5]:4569 dnsmgr y username 654580 percieved unregistered referesh 60 state request sent 1 IAX2 registrations the password is correct. The internet is working just fine. It was registered until i changed the registration from http to iax. ---
**Author:** ![WA3WCO](https://community.allstarlink.org/user_avatar/community.allstarlink.org/wa3wco/32/3123_2.png) [@WA3WCO](https://community.allstarlink.org/u/WA3WCO)\ **Post date:** [December 15, 2025, 6:55pm UTC](https://community.allstarlink.org/t/mobile-internet/22040/8 "2025-12-15T18:55:08Z")
It looks like your node is trying to register with an IPv6 address. Is your node not able to get an IPv4 address from the mobile hotspot? ---
**Author:** ![N5AD](https://community.allstarlink.org/user_avatar/community.allstarlink.org/n5ad/32/4127_2.png) [@N5AD](https://community.allstarlink.org/u/N5AD)\ **Post date:** [December 15, 2025, 7:21pm UTC](https://community.allstarlink.org/t/mobile-internet/22040/9 "2025-12-15T19:21:38Z")
no idea on that. I just now turned http registration back on, so is that what you are seeing? I had turned it off and was attempting to register through the iax. ---
**Author:** ![WA3WCO](https://community.allstarlink.org/user_avatar/community.allstarlink.org/wa3wco/32/3123_2.png) [@WA3WCO](https://community.allstarlink.org/u/WA3WCO)\ **Post date:** [December 15, 2025, 7:44pm UTC](https://community.allstarlink.org/t/mobile-internet/22040/10 "2025-12-15T19:44:56Z")
> [@N5AD](#): > > so is that what you are seeing? I was commenting on the `iax2 show registry` output you kinda pasted in above that started off with : ```auto host [2607:7700:0:49::3415:a9c5]:4569 ``` That `2607:...` string is an IPv6 address. While we hope to support IPv6 in the future we're not there yet. Curently, all AllStarLink nodes must have IPv4 addresses for connectivity. ---
**Author:** ![N8EI](https://community.allstarlink.org/user_avatar/community.allstarlink.org/n8ei/32/4254_2.png) [@N8EI](https://community.allstarlink.org/u/N8EI)\ **Post date:** [December 15, 2025, 9:14pm UTC](https://community.allstarlink.org/t/mobile-internet/22040/11 "2025-12-15T21:14:13Z")
What does your authentication configuration look like either for HTTP or IAX registration? The hostname should be `register.allstarlink.org` which doesn't have an IPv6 address. The address `2607:7700:0:49::3415:a9c5` is a T-Mobile address but why your box is using it doesn't make much sense. ---
**Author:** ![N5AD](https://community.allstarlink.org/user_avatar/community.allstarlink.org/n5ad/32/4127_2.png) [@N5AD](https://community.allstarlink.org/u/N5AD)\ **Post date:** [December 15, 2025, 9:40pm UTC](https://community.allstarlink.org/t/mobile-internet/22040/12 "2025-12-15T21:40:04Z")
IAX register =\> 654580:\*\*\*\*\*\*@register.allstarlink.org rpt\_http\_registrations.conf register =\> 654580:\*\*\*\*\*\*@register.allstarlink.org i get what you are saying re the ipv6 addresses. No idea why, but research suggests that tmobile hot spots are forcing ipv6 and on a slim chance, I may be able to tell the router to force ipv4 addressing. I’ll have to make the trek up the mountain to see for sure. May lose some 5g and only ahve lte but i is only servicing allstar so that may not be an issue. ---
**Author:** ![N8EI](https://community.allstarlink.org/user_avatar/community.allstarlink.org/n8ei/32/4254_2.png) [@N8EI](https://community.allstarlink.org/u/N8EI)\ **Post date:** [December 16, 2025, 12:07am UTC](https://community.allstarlink.org/t/mobile-internet/22040/13 "2025-12-16T00:07:16Z")
It seems very unlikely you're getting a v6-only connection. That wouldn't be useful for a lot of things, not just break ASL. Make sure your IPv4 network configuration is pulling a DHCP address and isn't hard-coded from before or something. ---
**Author:** ![N5AD](https://community.allstarlink.org/user_avatar/community.allstarlink.org/n5ad/32/4127_2.png) [@N5AD](https://community.allstarlink.org/u/N5AD)\ **Post date:** [December 16, 2025, 1:39am UTC](https://community.allstarlink.org/t/mobile-internet/22040/14 "2025-12-16T01:39:01Z")
so, this network is fresh out of the box. plug in, turn on, connect. no setup needed. so SOME information i have come across suggests that tmobile hot spots are forcing ipv6. it also SUGGESTs that it may be possible to force ipv4. i’ll have to go up the mountain to be sure. ---
**Author:** ![Gregory](https://community.allstarlink.org/user_avatar/community.allstarlink.org/gregory/32/4494_2.png) [@Gregory](https://community.allstarlink.org/u/Gregory)\ **Post date:** [December 16, 2025, 2:24pm UTC](https://community.allstarlink.org/t/mobile-internet/22040/15 "2025-12-16T14:24:45Z")
I am having the same issue with Tmobile. They have changed something . . . I have made a connection once or twice but then no more. No matter what I did it would not connect again. Watching this thread. ---
**Author:** ![N8EI](https://community.allstarlink.org/user_avatar/community.allstarlink.org/n8ei/32/4254_2.png) [@N8EI](https://community.allstarlink.org/u/N8EI)\ **Post date:** [December 16, 2025, 2:56pm UTC](https://community.allstarlink.org/t/mobile-internet/22040/16 "2025-12-16T14:56:48Z")
I think it's imperative for anyone to understand that a mobile hotspot connection like a T-Mobile, AT&T, or Verizon that is a stock, commercial connection is not recommended for AllStarLink and it's increasingly unlikely people can "make it work". As we're continue to have an explosion of IP-connected devices to cellular networks, we're reaching a tipping point where even Carrier Grade NAT (GCN) connectivity is constrained and they're doing all sorts of various games and network optimizations to keep things working for **web browsing and streaming**. The likely short term fix will be 44Net Connect which is a recently-announced service from ARDC. That will give up a public iP address and ability to use VPN up to that system seamlessly. Once I get access, I'm planning to work on some directions and scripting to do it "out of the box" (more or less) for ASL3 Appliances. However the long-term fix is to take action on the plans to completely overhaul the registration and IP-directory-based system for one that is key-based. Then IP addresses don't matter and IPv6 connectivity will work as a native component. ---
**Author:** ![NY2US](https://community.allstarlink.org/user_avatar/community.allstarlink.org/ny2us/32/3212_2.png) [@NY2US](https://community.allstarlink.org/u/NY2US)\ **Post date:** [December 17, 2025, 5:58am UTC](https://community.allstarlink.org/t/mobile-internet/22040/17 "2025-12-17T05:58:20Z")
I think perhaps adding a How-To in the core documentation about CGNAT’d nodes with some tutorials might finally put an end to this rehashed issue? Great suggestion to use .44Net for a public IP, I believe the user would have to put their public IP in iax.conf for the bindaddr=. ANOTHER long time solution for Greg (mentioned elsewhere): Users can expand their primary (home) node number from Allstarlink to a block of 10 node numbers. Then, set one of those node numbers aside and advertise THAT as your remote node number. At the remote CGNAT’d node, create a persistent connection back to that set aside dedicated node number, and in rpt.conf, append to startup\_macro = \*_xxx\_. Note: For stability at remote unattended nodes, create a couple of cron jobs (crontab -e) and add as follows: # Restart asterisk at 0400h every Monday-Saturday 00 4 \* \* \* 1-6 “systemctl restart asterisk” # Reboot server at 0400h every Sunday 00 4 \* \* \* 0 /sbin/shutdown -r now Been running those for years and I sleep well at night. ---
**Author:** ![KK6RQ](https://community.allstarlink.org/user_avatar/community.allstarlink.org/kk6rq/32/3511_2.png) [@KK6RQ](https://community.allstarlink.org/u/KK6RQ)\ **Post date:** [December 17, 2025, 10:12am UTC](https://community.allstarlink.org/t/mobile-internet/22040/18 "2025-12-17T10:12:44Z")
0400h…? Right in the middle of my best conversations! ---
**Author:** ![N8EI](https://community.allstarlink.org/user_avatar/community.allstarlink.org/n8ei/32/4254_2.png) [@N8EI](https://community.allstarlink.org/u/N8EI)\ **Post date:** [December 17, 2025, 2:42pm UTC](https://community.allstarlink.org/t/mobile-internet/22040/19 "2025-12-17T14:42:00Z")
> [@NY2US](#): > > I think perhaps adding a How-To in the core documentation about CGNAT’d nodes with some tutorials might finally put an end to this rehashed issue? Great suggestion to use .44Net for a public IP, I believe the user would have to put their public IP in iax.conf for the bindaddr=. You don't need any special configuration in Asterisk. Now that 44Net Connect is released, people can try: > **[44Net Connect for ASL - AllStarLink Manual](https://allstarlink.github.io/adv-topics/44net-connect/)** > > AllStarLink Manual I just published this yesterday and asked a few people to test before announcing it more widely. But if you take a stock ASL3 install and put 44Net Connect full-tunnel on it, everything should basically "just work". ---
**Author:** ![N5AD](https://community.allstarlink.org/user_avatar/community.allstarlink.org/n5ad/32/4127_2.png) [@N5AD](https://community.allstarlink.org/u/N5AD)\ **Post date:** [December 17, 2025, 3:40pm UTC](https://community.allstarlink.org/t/mobile-internet/22040/20 "2025-12-17T15:40:22Z")
my question is why isn’t the iax registration working for this? [Next page](https://community.allstarlink.org/t/mobile-internet/22040.md?page=2)