1. Current Location: Home >  Router Encyclopedia >  Using the stopwatch to test the router restart, powering on to WiFi can connect to it does six things

Using the stopwatch to test the router restart, powering on to WiFi can connect to it does six things

Flowchart for router restart and startup: From 0 to 120 seconds, complete six tasks in order before the network connects

Last week, I changed the placement of the AX3000T at home, unplugged it and moved it to a new spot. The phone immediately started popping up notifications: camera offline, speaker offline, door lock offline, a series of rattling noises. I had nothing better to do, so I counted from the moment I plugged in to the phone being able to open the webpage: 1 minute and 50 seconds. During this time, notifications came back one by one by itself, and the last one was about the robot vacuum, which dragged on for four minutes.

I used to wait just a minute or two, always feeling the router was "slow to respond." This time, after carefully counting, I realized that in just over a minute, it was very busy, doing six tasks in order in one go. If any one was left unfinished, your internet just wouldn't work. More practically, by understanding the sequence of these six things, you can immediately identify the root cause of the problem after a restart without internet—the symptoms blocked by steps four and five are completely different.

Let's count them all first: from powering on to being able to access the internet, the six things go in order

First, let me show you the stopwatch record for my machine. Your machine will have both fast and slow versions, but the order won't change

What ? What ? . . . 5. in to send numbers to all devices in home. for to work state
is it doing during the phase timedo you see here
10~10 seconds kernel self-check lights are on or off, can't access the background
2. 10~ 20 seconds to read the configuration from flash memory back to memory light, start flashing regularly
3. 20~40 seconds: WiFi RF activates, broadcasting names, phone can find WiFi
40~70 seconds WAN port to ask for or dial numbers WiFi can connect, but no network
DHCP opens70~110 secondsthe
6. 80~120 secondsbinding, forwarding, scheduling, and other services to return, everything is restored to its original

Note the misalignment between steps three and four—WiFi activated first, network connections later. That's why, after restarting, you always find WiFi and connect successfully, but the webpage just won't open. Many people panic at this point, thinking the router is broken or the password is lost, but in fact, it's still waiting in line at step four. With this watch in mind, just wait.

For the first ten seconds, it "opens its eyes": no response to pressing it, don't rush to pull it out

After

ten seconds of plugging in, the router does the same thing as pressing the computer power button: the CPU moves system programs from the flash memory into memory and starts running, first checking if the hardware is present and if the memory is working well. At this stage, the light language varies by brand. In my case, the light flashes once and then goes off, while Xiaomi's device usually has the orange light stay on for a few seconds— that orange light means "starting," not a malfunction.

In those ten seconds, if you type 192.168.1.1 in your browser, the page will probably spin because the backend web service hasn't even started yet. My mom did this before: after rebooting, she would say "Can't get into the backend" just ten seconds later, then unplug and replug it in, going back and forth three times. Actually, you haven't waited enough; every time you pull the strings, you have to start over from the beginning.

By the way, a common misunderstanding: when powered on, you can't hear the fan spin or feel it doesn't warm to the touch—all of this is normal. At this stage, the system's power consumption is only two or three watts; it only starts to increase once WiFi and forwarding are running.

The second thing: Reading the configuration from flash memory back to memory and rebooting the Nengzhi card is also the secret here

The router's "memory" is stored in two layers. Your broadband account, WiFi name and password, port forwarding rules—all written in flash memory, not lost when powered off; And its running state—the hanging connections, the temporary data running in memory—is all stored in memory, and when the power is cut off, it resets to zero. I previously wrote a dedicated article about the difference between these two the difference between flash memory and internal memory. I completely understood these two when I couldn't install plugins during flashing.

So the second thing is to read the configuration from the flash memory back into memory as it is, so it can relive it according to the configuration. Because memory resets immediately after losing power, rebooting became the first trick for network management: the messy connection ledger was cleared and recounted, the NAT session table started from zero, and the full memory dropped back—The memory usage of a 256MB machine dropped from 80% to 30% thanks to this effort.

This is the fundamental difference between rebooting and reset: reboot only clears memory, while the configuration is still read back from flash memory; The reset also erases the configuration in the flash memory and restores it from scratch. So don't forget the password when restarting, and clean everything when resetting—don't confuse these two.

Third and fourth things: WiFi goes first, WAN port goes for directions

Step three: WiFi starts broadcasting the name on RF. This doesn't depend on anyone—the router can do it themselves, so it always comes first. Your phone is searched and connected, but at this moment, all you have in hand is an "internal department ticket"—the way out isn't open yet.

The fourth step is to seek the way, which can be divided into two situations. The optical modem is router-modep; the router's WAN port sends a DHCP request to the superior and waits for the modem to send an IP, which is basically instant. The optical modem switched to a bridge, so the router has to dial through PPPoE and submit the broadband account and password for authentication. if the account and password don't match, it's "authentication failed"; if the line is blocked, it's "server unresponsive". These two types of error reports have completely different root causes, and I am here error code has been dismantled one by one in the article.

After restarting, there's no internet, but WiFi is working fine. There's a 90% chance it's stuck at step four. At this point, don't restart the router repeatedly. First, check the optical modem's light: LOS red flashing is a problem with the optical path, slow PON flashing means registration failed. You need to follow the optical modem's approach to check— The PON registration process has nothing to do with the router; restarting the router a hundred times won't fix it.

Fifth and sixth things: DHCP opens and brings the whole family back, and service returns one by one

Step five: Once the router has its own network, start the DHCP server and issue commands to all home devices. On the device side, you also have to redo the process of requesting an account: mobile computers are fast, and it's done in seconds; Devices like cameras and door locks that only recognize 2.4G slow devices take a few minutes to reconnect, I wrote about network configuration failures. After reboot, reconnection is just repeating the same route. So the order of notifications is basically the ranking of the characteristics of each device's network card.

Step 6 may look unremarkable, but it actually has plenty of pitfalls. Static IP binding tables and port forwarding rules are read from the configuration and reactivated; UPnP mappings are registered by the device itself and need to be reissued when the device returns, so The mappings in the UPnP list appear sequentially after restarting, not all at once.

The most sinister one is system time. The router doesn't have a battery, so the outage time resets to zero. After power comes in, you have to rely on NTP to check the network for time—but since timing itself requires the network to connect first, it's always the slowest to recover time. If the timing doesn't match, functions like scheduled restart and WiFi timer switch get all messed up. 90% of the late-night timer failure to execute is because of this. My set the reset time to 4 a.m. One time, after rebooting, the time reset to zero, and the next timer was miscalculated by a day.

Why does it take 30 seconds to unplug the battery, and what order should you search when there's no internet

?

Here are two practical tips for wrapping things up.

First, you have to wait 30 seconds before plugging it back in after unplugging the power and restarting—not some kind of superstition. The capacitors in the power supply hold residual power, and the moment you plug them in, the chip is half-dead—at best, it does another self-check, at worst, it drops halfway through writing the configuration. Wait 30 seconds to discharge the capacitor, completely ending the previous round. I tried waiting 5 seconds before plugging it in, and the machine started up, but the WiFi name was the default name used during initialization—the configuration wasn't fully read, so I had to restart again.

Second, after rebooting, there was no internet, so I searched backward in the order of the six things:

? , the fourth The network has it. .
What step should you do first when the problem is stuck
Can't access the backend, the light is off. Step one or twowait for 2 minutes before checking
WiFi. Thestep is to check the modem light and check the connection
connected to a certain device and hasn't returned. Step five: disconnect the device and reconnect
Timing and forwarding are not workingStep six: First, check the system time

In the end, it comes down to one thing: the one or two minutes of "no internet" after a restart is a process, not a malfunction. The real warning is that after waiting two minutes, you still can't get up—that's the real problem in step four. Follow the optical modem and dialing approach to check—stop trying to restart the game.

Read More


Copyright Notice Scan to read on mobile
All Rights Reserved: 《SHUNOT》 => 《Using the stopwatch to test the router restart, powering on to WiFi can connect to it does six things》
Article URL: https://www.shunot.com/en/lybk/1145.html
Unless otherwise stated, all articles are original by 《SHUNOT》. Reposting is welcome! Please indicate the original URL when reposting, thank you.

Contact Us

Online Consultation: Click here to send me a message

WeChat ID: master_135

Scan to follow