The scene is back:
Working late at night, knocking on the code, suddenly finding linux out of the net? The bottom-right network icon changes, the browser doesn't work. This babysitting program, hand in hand to bring you back to life

Step 1: check these low-level errors first
Is wifi really connected
2 ️⃣ net card "sealed"
Open terminal, enter:
Ip a # or ifconfig
If the online card name (e. G. Eth0, wlan0) does not have an ip address (e. G. 192. 168. X), it's not connected at all
Step 2: try "reactivate law"
Linux internet services sometimes take a turn at the top of the air and give the orders:
# most desktop versions apply
# the old system uses this
Ten seconds after restart, try to refresh the page
Firewall: did you do it
Linux's own firewall could have killed the network
Temporary help:
Sudo systeml stop firewall # off firewall (deactivated after restart)
Turning off the internet would make it clear that the rules were problematic and could be followed up by rules on release。
Dns configuration: losing is like making the wrong phone
Can't get through to the ip but can't get to the web page? Mostly dns solver failure
# test googledns
General read dns:
Driver problem: hardware does not recognize webcards
Especially in dual systems/new linux
Terminal input:
Lspci |grep-i net
If the driver is not installed (e. G., some realtek cards), the drive will have to be downloaded on disks or installed after the usb shared network。
Last resort: route watch repair
The network's working, but it's not working? Probably lost the route
Ip route show
# default gateway (to your router ip)
Summary:
Linux is out of his mind. Ninety percent of the problems can be solved by this procedure
Check physical connections, boom, restart services, turn off firewalls for dns, check drive/routing
Five minutes of operation. Web is back in place




