How long after restarting the router before you can get online? I counted through the stopwatch, and from powering on to WiFi and connecting it to it, I did six things in one go

Last week,

changed the AX3000T position of the home unit, unplugged it and moved it back in. The phone immediately popped 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 one or two minutes, 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.

count them first: from powering on to being able to access the internet, the six things are done in order

first lay out the stopwatch record for my machine. Your machine will have both fast and slow ones, but the order won't change:

note the misalignment between steps three and four—WiFi activates first, network connects 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.

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

plugged in for ten seconds, the router does the same thing as pressing the computer power button: the CPU moves system programs from 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 signals differ by brand. In my case, the lights flash once and then go off, while Xiaomi's machines usually have orange lights that stay on for a few seconds— that orange light means "starting," not a fault.

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.

a misunderstanding: when powered on, you can't hear the fan spin or feel it doesn't warm to the touch—all 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.

second thing: the secret to reading configuration from flash memory back to memory and rebooting the Nenji card is also here

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 the difference between flash memory and memory, I completely understood the plugin when I couldn't install plugins during flashing.

the second thing is to read the configuration from the flash memory back into memory as it is, so it can relive the configuration accordingly. Because memory resets immediately after power outage, rebooting became the first trick to fix the network: the messy connection ledger was cleared and re-recorded, the NAT session table started from zero, and the fully charged memory dropped back—the 256MB machine's memory usage dropped from 80% to 30 thanks to this move.

this is the fundamental difference between a restart and a 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.

the third and fourth things: WiFi goes first, WAN connectivity goes to the

the third step, WiFi starts broadcasting the name. This doesn't rely on anyone—the router can do it on its own, 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 a path, 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 issues are completely different. I've broken them down one by one in error code article.

after restarting, there was no internet, but WiFi was working fine, so 90% of the time was stuck at step four. At this point, don't keep restarting the router. 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—PON registration process has nothing to do with the router, and restarting the router a hundred times won't fix it.

Fifth and Sixth Matters: DHCP opens and brings the whole family back, and service returns one by one

step five, once the router has its own network, turn on the DHCP server and issue commands to all family 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 minutes to reconnect. network setup pitfalls. I wrote an article about that after reboot, the reconnection is like reconnecting the same path over again. So the order of notifications is basically the ranking of the characteristics of each device's network card.

Step Six may seem insignificant, but it 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 UPnP list appear sequentially after reboot, 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 messed up, and 90% of the late-night timer failure to execute is due to this . My reset was set for 4: a.m., but once after restarting, the time reset to zero, and I mistakenly calculated the next timer by one day.

Why does it take 30 seconds to unplug

, and in what order should you search when there is no internet

two practical tips for finishing the show.

First, you have to wait 30 seconds before plugging it back in after unplugging and restarting—this isn't 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, I searched backward in the order of the six things:

In the end,

summed up in one sentence: the one or two minutes of "no internet" after a restart is a process, not a fault. 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.