There is Internet, pages are not loaded - not DNS / proxy / hosts / tariff / cable / etc, but what?

Question

Android

Anemez: I went to the Internet under Debian 9 using a Galaxy A3 2016 phone and a usb cord (modem mode in the phone).
I bought a new phone - Galaxy M62, android 11, One UI 3.1 (i.e. latest updates) - stopped working. The cord from micro-USB to Type-C has been updated (if anyone is joking). As a result, we have through the cord on the computer and on the laptop:
1. There is Internet on the phone, the tariff ("Communication Z" from Beeline) implies the distribution, the operator called - everything is OK, balance> 0, roaming, coverage, network signal level - everything is OK .
2. If you distribute through a WiFi access point, everything is also OK (tested on several smartphones and a laptop with Debian 9).
3. The USB cable is working: the connection is stable, the statistics utilities do not show any errors, you can watch videos and transfer large files - everything is ok.
4. Utilities ping and *traceroute of various kinds work without comment, netstat, ifconfig, ethtool, networkctl, etc. nothing suspicious comes up. The configuration files did not change, I tried to change ttl and mtu - without result.
The native Telegram client is working , joining the DHT qBittorrent network, torrents are famously loaded via uTP connection... ) or completely if small.
6. Firefox and Opera(chromium) load either very light sites or almost nothing - they always wait for the data to finish loading.
7. wget hangs like this:
wget ya.ru
--2021-10-25 17:06:21-- ya.ru
Recognizing ya.ru (ya.ru)… 87.250.250.242, 2a02:6b8::2:242
Connecting to ya.ru (ya.ru)|87.250.250.242|:80... connection established.
HTTP request sent. Waiting for a response… 302 Found
Address: https://ya.ru/ [jump]
--2021-10-25 17:06:22-- https://ya.ru/
Connecting to ya.ru (ya.ru) |87.250.250.242|:443... connection established.
HTTP request sent. Waiting for response… 200 Ok
Length: 60496 (59K) [text/html]
Saving to: "index.html"

index.html 0%[ ] 0 --.-KB/s

8. Windows 10 on a VirtulalBox virtual machine through NAT and Briged Adapter behaves similarly - there are pings, but no pages.

9. Googled all day. Android on the settings menu checked everything (by eye) - there are no comments.

Where to dig further - I do not know. What do you think?
---------------
UPD: addition 1:
1. this is how it works: debian -- comp -- usb -- old phone -- wifi -- new phone -- 4g -- opsos.

2. The metric, it seems, also does not affect.

Answer 1

it looks like a problem with the MTU - interface settings in the studio
also try to ping the external server with large packets
ping ya.ru -f -l 1450
, reducing the value if the ping fails

Answer 2

The previous answer is most likely correct. On Beeline, I encountered several times that packets larger than 1360 (or 1361, I don’t remember) do not go through. Most likely, something is connected with fragmentation but it is inaccurate. From Windows it is checked with a regular ping, if -l 1362 or more timeout, and -l 1361 passes, then yes, change the MTU