Unable to get data from tethered mobile phone

Routers
1

Hi,

I have a strange issue that I can’t seem to figure out and I hope that you can help.

I’m using a mobile phone as a proxy with the tethering option.

I have setup port forwarding and I am able to connect to it with 192.168.8.1:1111

The mobile phone receives and sends data (the mobile apps show data coming and going through the app), but I am not able to receive anything from the request.

I am using a local computer connected to 192.168.8.100 and have granted firewall rules that basically allow everything, yet I am still unable to get any data back from the request.

I am testing by using things like curl --socks5 192.168.8.1:1111 https://www.testing.com/ and it just hangs…

What is wrong here? Can you help?

Thanks!

3

Hi,

To help us better understand the issue, could you please provide:

  1. The router model and firmware version you are using
  2. A detailed description or diagram of your network topology, including:
    • IP addresses of all involved devices
    • Connection methods (USB tethering, hotspot, wired/wireless)
    • The role of each device (for example, proxy server, port forwarding rules details)
4

Hi,

Thank you for responding. After lots of investigating, it appears to be a limitation from my internet service provider.

They seem to be blocking CONNECT. Tihs allows me to access HTTP websites but not HTTPS websites.

”blocking outbound TLS/SSL tunneling” or “Captive WiFi Proxy Restrictions” ???

I’m pretty sure that has nothing to do with you guys…. but if you want me to explain more and maybe you could still help that would be sweet. Please let me know!

5

Thank you for the update.

You may try using curl’s verbose mode (-vvv) and compare the outputs for HTTP and HTTPS to help isolate the issue.

curl -vvv --socks5 192.168.8.1:1111 https://example.com
curl -vvv --socks5 192.168.8.1:1111 http://example.com

Additionally, please check:

  1. The PC running curl has the correct system time and the required root CA certificate installed and trusted.
  2. The target server is indeed serving HTTPS.