Stackexchange iconStackexchangeSep 23, 2026 ~1 min source read

LTE modem: IPv4 ping works, but HTTPS connections are reset [closed]

I need help on my network, specifically my modem I have a Qualcomm MSM8916-based LTE/4G USB modem connected to a Linux machine. The LTE connection itself appears to work, but I am having a strange connectivity problem.

Share this story

Send the public story page.

Useful takeaways from this story.

I need help on my network, specifically my modem I have a Qualcomm MSM8916-based LTE/4G USB modem connected to a Linux machine.

What works ping google.com works over IPv4: $ ping -4 google.com PING google.com (64.233.170.113) 56(84) bytes of data.

The LTE connection itself appears to work, but I am having a strange connectivity problem.

Building the complete brief

The page is ready to read now. The fuller skim-friendly version will appear here automatically.

The useful part

I need help on my network, specifically my modem I have a Qualcomm MSM8916-based LTE/4G USB modem connected to a Linux machine. The LTE connection itself appears to work, but I am having a strange connectivity problem. What works ping google.com works over IPv4: $ ping -4 google.com PING google.com (64.233.170.113) 56(84) bytes of data.

How it works

  • 8 packets transmitted, 8 received, 0% packet loss rtt min/avg/max/mdev = 134.289/201.634/249.126/45.846 ms Pinging 8.8.8.8 does not work.
  • Network is unreachable and: $ curl -v -6 https://www.google.com IPv6: 2001:4860:4802:32::78 Trying [2001:4860:4802:32::78]:443...
  • For example: $ curl -v -4 https://www.google.com Host www.google.com:443 was resolved.
  • ALPN: curl offers h2,http/1.1 TLSv1.3 (OUT), TLS handshake, Client hello (1):
  • Connection reset by peer in connection to www.google.com:443 I get the same behavior with Cloudflare: $ curl -v -4 https://www.cloudflare.com Trying 104.16.124.96:443...

What to take from it

Connection reset by peer in connection to www.cloudflare.com:443 IPv6 does not appear to be available through the modem: $ ping -6 google.com ping: connect:

Details worth keeping

HTTPS connections fail during the TLS handshake. IPv6: (none) IPv4: 216.239.38.120 Trying 216.239.38.120:443... Connection reset by peer OpenSSL SSL_connect:

Keep reading in the app

Open the app view to save this story, compare related coverage, and continue from the same source.

Open in app