New Member
•
7 Messages
phone (Samsung A53 5G) hotspot routing issue
My new mobile service has hotspot issues. I cannot reach port 22 on my amazon
aws instances using the Hotspot. Other than this, the Hotspot seems to be
working normally. I have been doing this using Verizon, for years before switching
to Att this month. I have home Fiber too, and that *is* permitting my traffic.
Hopefully someone here can help me resolve this, perhaps seeing the traceroute snippets
I'll attach below. Is there a firewall problem at 12.244.0.26 maybe? Does first Wireless
LAN adapter shown (below) need a "connection-specific DNS suffix" like shown for the second (Fiber)?
I have not reached a suitable technical contact thus far.
Thanks for any help,
Samsung A53 5G Android 12.1
--- HOTSPOT Client Port 22 Network Timeout [external IP 166.205.218.108]------------------------
Wireless LAN adapter Wi-Fi:
Connection-specific DNS Suffix . :
IPv6 Address. . . . . . . . . . . : 2600:381:4223:d489:1142:823b:dc8d:7e0e
Temporary IPv6 Address. . . . . . : 2600:381:4223:d489:4452:6de8:44b7:3804
Link-local IPv6 Address . . . . . : fe80::1142:823b:dc8d:7e0e%3
IPv4 Address. . . . . . . . . . . : 192.168.76.22
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : fe80::5065:2fff:feae:2853%3
192.168.76.183
Here, Port 22 *unreachable* from Hotspot client PC
C:\build\tracetcp_v1.0.3>tracetcp.exe 34.198.231.205:22 -t 500 -c
[34.198.231.205:22] 1 6 ms 4 ms 3 ms 192.168.76.183
[34.198.231.205:22] 2 346 ms * * 107.243.2.10
[34.198.231.205:22] 3 * * * Request timed out.
[34.198.231.205:22] 4 * * * Request timed out.
[34.198.231.205:22] 5 * * * Request timed out.
[34.198.231.205:22] 6 * * * Request timed out.
[34.198.231.205:22] 7 42 ms 287 ms * 12.244.0.26
[34.198.231.205:22] 8 * * * Request timed out.
... omitting successive timeouts
[34.198.231.205:22] 29 * * * Request timed out.
[34.198.231.205:22] 30 * * * Request timed out.
Port 80 is reachable using Hotspot
C:\build\tracetcp_v1.0.3>tracetcp.exe 34.198.231.205:80 -t 500 -c
[34.198.231.205:80] 1 4 ms 4 ms 22 ms 192.168.76.183
[34.198.231.205:80] 2 Dest. in 59 ms. Port OPEN on 34.198.231.205
--- FIBER Client Port 22 works as intended [external IP 76.218.236.50] ------------------------
Wireless LAN adapter Wi-Fi:
Connection-specific DNS Suffix . : attlocal.net
IPv6 Address. . . . . . . . . . . : 2600:1700:cc0:1c60::3c
IPv6 Address. . . . . . . . . . . : 2600:1700:cc0:1c60:1142:823b:dc8d:7e0e
Temporary IPv6 Address. . . . . . : 2600:1700:cc0:1c60:c536:1c63:3391:8121
Link-local IPv6 Address . . . . . : fe80::1142:823b:dc8d:7e0e%3
IPv4 Address. . . . . . . . . . . : 192.168.1.67
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : fe80::de8d:8aff:fe18:bbc2%3
192.168.1.254
Ports 22 and 80 *are* reachable from Fiber client PC (port 80 not shown)
C:\build\tracetcp_v1.0.3>tracetcp.exe 34.198.231.205:22 -t 500 -c
[34.198.231.205:22] 1 4 ms 3 ms 3 ms 192.168.1.254 [dsldevice.attlocal.net]
[34.198.231.205:22] 2 5 ms 4 ms 5 ms 104.185.72.1 [104-185-72-1.lightspeed.rlghnc.sbcglobal.net]
[34.198.231.205:22] 3 5 ms 129 ms 344 ms 99.173.77.8
[34.198.231.205:22] 4 * * * Request timed out.
[34.198.231.205:22] 5 * * * Request timed out.
[34.198.231.205:22] 6 226 ms 459 ms 22 ms 32.130.17.9
[34.198.231.205:22] 7 17 ms 14 ms 19 ms 12.244.0.26
[34.198.231.205:22] 8 * * * Request timed out.
... omitting successive timeouts
[34.198.231.205:22] 22 * * * Request timed out.
[34.198.231.205:22] 23 * * Dest. in 23 ms. Port OPEN on 34.198.231.205
My EC2 security groups allow access to clients 166.205.218.108 and 76.218.236.50
tonydi
ACE - Guru
•
9.9K Messages
1 year ago
Moving this post to the Wireless forum
0
0
josephmorgan3591
New Member
•
7 Messages
1 year ago
is there a better forum to float this in front of?
0
0
ATTHelp
Community Support
•
220.9K Messages
1 year ago
Hey, @josephmorgan3591. Thanks for reaching out to us for assistance with your hotspot.
We have a very helpful article that will provide suggestions to help with your mobile hotspot. The first suggestion is to use the AT&T Troubleshoot and Resolve tool. We believe this will be helpful in identifying the problem and providing solutions to fix it. This article also provides other information about setting up and connecting your mobile hotspot.
We hope this helps! If you have any other questions or concerns, please reach back out to us.
TT, AT&T Community Specialist
0
0
josephmorgan3591
New Member
•
7 Messages
1 year ago
Can anyone look at the traceroute output and confirm my suspicions that port 22 is being blocked by ATT?
0
0
josephmorgan3591
New Member
•
7 Messages
1 year ago
The totality of support for this deal breaking issue has been to reference articles covering how to turn hotspot feature on. The terms of service seem to indicate that port 22 should work as it does under verizon.
0
0
ATTHelp
Community Support
•
220.9K Messages
1 year ago
Hello, @josephmorgan3591! We want to address your concerns regarding the hotspot and port 22 access!
Based on the information you have provided, let's meet in a direct message to further investigate what may causing you to not have access to the Amazon AWS. Please check your Direct Message Inbox (it's the chat icon next to the bell icon in the upper right corner of the Forums).
In the meantime, you can switch to Wi-Fi, to access the Amazon AWS.
Look forward to chatting with you soon.
Thank you for reaching out to AT&T Community Forums!
Rachel, AT&T Community Specialist
0
0
josephmorgan3591
New Member
•
7 Messages
1 year ago
Hi,
Thanks for responding. I am trying to fix this:
Dell/Windows ---> A53 5G/Hotspot ---> Amazon AWS
ssh/port:22 ---> * blocked *
I am unable to switch to Wi-Fi, so in the meantime I am unable to access Amazon AWS.
The issue is outlined above. Thanks for helping. I have not heard anything regarding escalated ticket CM20220627_153967881.
0
0
josephmorgan3591
New Member
•
7 Messages
1 year ago
CM20220627_153967881
0
0