Home • Router Encyclopedia - Page 7
-
Packet capture by WebSocket, after handshake, no more hang-ups
opened the Home Assistant page on my phone, and the living room temperature jumped from 26.4°C to 26.5°C, and I didn't touch the screen. Why should the webpage move on its own? I set up the smallest WebSocket service on my computer, using the most basic socket to handle and break down the frame and walk through it. I finally understood this line that refused to hang up. ...
-
Looking back, I found that my blog already uses HTTP/3 and QUIC
Switching from WiFi to data on your phone, and the webpage suddenly stops being online? I flipped through the response heads and found that my own little blog had already announced the Alt-SVC H3. This article explains how QUIC created a new TCP on UDP, why the queue blocking disappeared, and when the home network will finally benefit....
-
Even after changing the encrypted DNS, I still got rushed to answer. After capturing the packet, I saw that UDP 53 was just a postcard
Changing DNS or still showing ads? I caught a bag and saw clearly: traditional DNS using UDP 53 is basically a postcard, with the website address blatantly written on it, and anyone can view or change it halfway. Encrypted DNS means putting postcards in an envelope: browser secure DNS, Android private DNS, and router side switches, each with its own layer. This article explains the path and costs in one go....
-
Break point relay and packet capture: Range and 206 work together so well, disconnect and keep going
If the download drops to 97%, do you have to start over? Breakpoint resume is completed by HTTP Range requests and 206 responses. I took a file from my own and split it into 4 segments in parallel, then reassembled the MD5 file exactly like the original. The secret to the multithreaded downloader's acceleration lies in this duo....
-
After ordering 404 and 502 one by one, the 4 is your fault, the 5 is the stationmaster's fault
The numeric codes 404, 502, and 301 are the first sentences of each server reply. I tried out a service that lets you randomly click status codes one by one. Numbers 4 are mostly your fault, 5 is the site admin's fault. If you can't open after reading, don't refresh blindly....
-
Open a magnetic link, download without a server, and inside is the file fingerprint
My cousin saw that I had pasted a string of characters starting with 'magnet' into qBittorrent, so he downloaded it and started running on its own. He asked me which cloud drive this URL was from. In fact, it's not a website at all—it's the fingerprint of a document. I used Python to split the link, calculating the tracker, DHT, and block verification accounts all at once....
-
If the TV casting screen can be found but the NAS name cannot connect, it will automatically detect and assign everything to mDNS management
typing \fnnas\ on the computer doesn't connect to NAS, so switching to 192.168.31.20 seconds to enter is not a faulty NAS, but mDNS failing to translate the name into a house number. I checked the UDP 5353 port thoroughly and figured out why casting can show up TVs and why names sometimes work and sometimes don't. ...
-
Using the stopwatch to test the router restart, powering on to WiFi can connect to it does six things
After the router restarts, it takes a minute or two to get the internet—not because it's slow, but because it does six tasks in order. I use a stopwatch to go from plug-in count to the phone being able to browse the web: kernel self-check, reading configurations, WiFi activating first, WAN dialing, DHCP dispatch, service returning. Once you understand this order, you can immediately see where to find the root cause of problems after restarting without internet....
-
You can freely drag the progress bar in videos, but in 10 minutes, it actually gets cut into 64 clips
Watching videos and dragging progress bars responds instantly, but downloading takes half a day. I dug into an M3U8 checklist and counted: a 10-minute video was split into 64 small clips, each 10 seconds at 1.9MB. The progress bar, quality switching, and live streaming delay were all thanks to this cutting method....
-
utm_source exposure of the click source, deleted the wrong parameter link and couldn't open it
The utm_source and utm_medium after the website address question mark are the operational statistics sources, showing which channel you clicked in; But the WeChat article parameter is the article's ID card, and deleting it directly results in an error and won't open the page. I tested the consequences of deleting parameter in two types of links, and here's a comparison table showing which can be deleted and which absolutely cannot be moved....

