My guess without any real testing is that the egress IPs for even the IAX connections aren't consistent across where that traffic is popping out of the CGN system for T-Mobile.
You might try turning off ipv6 in your router.
T-Mo has had issues with ipv4 many times as I have seen it for several years.
Often self-corrects after 15m. Busy tower ?
I will try that next trip up there. it is a hike for sure. No not very busy. but we are wanting to increse usage an functionality.
Thank you! - This is working 100%
It took a week or two to get approved thru their process but my tunnel is configured and works while I am mobile. I tested for a couple of days before posting here but it all works.
The only thing I would add is the link to create the tunnel after the approval process is this one:
Thank you again for everyones help.
so, i have gone through the approval process. Is there any documentation on the steps necessary to configure a tunnel and what to do on the asl node?
Earlier in this post, @N8EI shared a link to ASL3 Manual : 44Net Connect for ASL. Does that information help?
I saw that. unfortunately, no it doesnât help much. Yes, I know the steps are there, they just are not linear. too much screen switching to make any sense of this. One of the things I loved about amateur radio when I first got licensed, was the willingness of others to teach and share their knowledge. Too many times I have asked questions on this forum only to be told it can be done, but never how. It is as if knowledge is a well guarded secret anymore.
That document describes step-by-step in linear order how to set up a stock ASL3 system for 44Net Connect. The process involves stitching multiple services together so you're going to have to use more than one "screen" to get the job done.
No one is trying to gatekeep knowledge but ASL is too large to write bespoke directions for every person's unique use case. Learning some Linux is a requirement of using ASL.
thank you for the dressing down. I am sure that is what I needed to hear. So, I have it possibly up and running on the node, I canât be sure since I CANâT get to my node now. What I could not find is how to get my pc on the network, as I am certain now that it must be on the network so that I can ACCESS my node again. I have installed wiregard on the pc, and it wantâs me to import my tunnel .conf file but there is NO documentation on where that may be located.
I'm not sure I understand your setup exactly. But if your node is not on your local network, when you brought up the wireguard tunnel it's a full tunnel as mentioned in the directions. When you created /etc/wireguard/wg0.conf did you copy-paste in the "wg-quick" configuration shown in your 44Net Connect configuration? If so, the public IP address of your node is now the last IP address on the third line of the configuration. For example, one of mine says:
[Interface]
PrivateKey = REPLACE_WITH_YOUR_PRIVATE_KEY
Address = fe80::d4f5:d927:2fbc:4283/128, 44.27.134.30/32
In this case, my IP address is 44.27.134.30. You should be able to SSH to yours if the tunnel came up correctly.
I did indeed copy-paste the information in the âwg-quickâ config file. I have tried to ssh into that ip address and it times out. looking on my dashboard on 44net it shows that the status is connected
this node is on a mountain top located some miles away from me right now. I can take the trek up there if needed but as of this moment, I have no access to the node. it is up and running as it should and evidenced by the fact that the messages are going out over the repeater but i just no longer can get into the node from here.
Interesting. That definitely should be working. Do you have any other host on that same remote network that you can SSH to and then SSH locally into the ASL node? Local-local LAN connections would still work.
Ok. I got back into my node. it is apparently up and running, however, I do not see it as registered on my allstarlink portal.
What does rpt show registrations report?
Host Username Perceived refresh state
54.44.147.201:443 654580 44.27.129.114:4569 179 registered
1 HTTP registration
so everything appears to be working now. incoming/outgoing connects are good to go. the only thing left is my dvmobile is not making the connection to this node. this may be for another thread. thank you for your assistance.