


Solve the problem that Linux cannot access the external network
Question:
A certain Linux server cannot ping the domain name, the following prompts:
Preparation :
First make sure the router is connected and the router can access the external network. This can be confirmed by accessing the gateway.
[root@localhost ~]# ping 192.168.1.1 PING 192.168.1.1 (192.168.1.1) 56(84) bytes of data. 64 bytes from 192.168.1.1: icmp_seq=1 ttl=64 time=2.96 ms 64 bytes from 192.168.1.1: icmp_seq=2 ttl=64 time=1.75 ms
Free video tutorial sharing: linux video tutorial
If you are sure that there is no problem with the network, you can solve it through the following steps:
1 . Make sure the domain name server is set up. If not, it is recommended to set up Google's public DNS service. It should not cause problems.
[root@localhost ~]# cat /etc/resolv.conf search localdomain
Because my DNS is not set up, pinging from the external network fails. Add dns to the file
[root@localhost ~]# vi /etc/resolv.conf search localdomain nameserver 202.98.96.68 nameserver 61.139.2.69 ~
2. Make sure the gateway has been set
# grep GATEWAY /etc/sysconfig/network-scripts/ifcfg* /etc/sysconfig/network-scripts/ifcfg-eth0:GATEWAY=192.168.40.1
If not, add the gateway as follows:
# route add default gw 192.168.40.1
Or manually After writing the /etc/sysconfig/network-scripts/ifcfg* file, restart the network service:
# service network restart
3. Ensure that dns resolution is available
# grep hosts /etc/nsswitch.conf hosts: files dns
If there is a problem with any of the above, correct it and test again , it should be no problem:
#ping -c 3 www.baidu.com PING www.a.shifen.com (220.181.6.175) 56(84) bytes of data. 64 bytes from 220.181.6.175: icmp_seq=0 ttl=50 time=9.51 ms 64 bytes from 220.181.6.175: icmp_seq=1 ttl=50 time=8.45 ms 64 bytes from 220.181.6.175: icmp_seq=2 ttl=50 time=8.97 ms --- www.a.shifen.com ping statistics --- 3 packets transmitted, 3 received, 0% packet loss, time 2002ms rtt min/avg/max/mdev = 8.450/8.977/9.511/0.446 ms, pipe 2
Recommended related articles and tutorials: linux tutorial
The above is the detailed content of Solve the problem that Linux cannot access the external network. For more information, please follow other related articles on the PHP Chinese website!

Hot AI Tools

Undresser.AI Undress
AI-powered app for creating realistic nude photos

AI Clothes Remover
Online AI tool for removing clothes from photos.

Undress AI Tool
Undress images for free

Clothoff.io
AI clothes remover

AI Hentai Generator
Generate AI Hentai for free.

Hot Article

Hot Tools

Notepad++7.3.1
Easy-to-use and free code editor

SublimeText3 Chinese version
Chinese version, very easy to use

Zend Studio 13.0.1
Powerful PHP integrated development environment

Dreamweaver CS6
Visual web development tools

SublimeText3 Mac version
God-level code editing software (SublimeText3)

Hot Topics



The key differences between CentOS and Ubuntu are: origin (CentOS originates from Red Hat, for enterprises; Ubuntu originates from Debian, for individuals), package management (CentOS uses yum, focusing on stability; Ubuntu uses apt, for high update frequency), support cycle (CentOS provides 10 years of support, Ubuntu provides 5 years of LTS support), community support (CentOS focuses on stability, Ubuntu provides a wide range of tutorials and documents), uses (CentOS is biased towards servers, Ubuntu is suitable for servers and desktops), other differences include installation simplicity (CentOS is thin)

How to use Docker Desktop? Docker Desktop is a tool for running Docker containers on local machines. The steps to use include: 1. Install Docker Desktop; 2. Start Docker Desktop; 3. Create Docker image (using Dockerfile); 4. Build Docker image (using docker build); 5. Run Docker container (using docker run).

CentOS installation steps: Download the ISO image and burn bootable media; boot and select the installation source; select the language and keyboard layout; configure the network; partition the hard disk; set the system clock; create the root user; select the software package; start the installation; restart and boot from the hard disk after the installation is completed.

CentOS has been discontinued, alternatives include: 1. Rocky Linux (best compatibility); 2. AlmaLinux (compatible with CentOS); 3. Ubuntu Server (configuration required); 4. Red Hat Enterprise Linux (commercial version, paid license); 5. Oracle Linux (compatible with CentOS and RHEL). When migrating, considerations are: compatibility, availability, support, cost, and community support.

Docker process viewing method: 1. Docker CLI command: docker ps; 2. Systemd CLI command: systemctl status docker; 3. Docker Compose CLI command: docker-compose ps; 4. Process Explorer (Windows); 5. /proc directory (Linux).

Troubleshooting steps for failed Docker image build: Check Dockerfile syntax and dependency version. Check if the build context contains the required source code and dependencies. View the build log for error details. Use the --target option to build a hierarchical phase to identify failure points. Make sure to use the latest version of Docker engine. Build the image with --t [image-name]:debug mode to debug the problem. Check disk space and make sure it is sufficient. Disable SELinux to prevent interference with the build process. Ask community platforms for help, provide Dockerfiles and build log descriptions for more specific suggestions.

Docker uses Linux kernel features to provide an efficient and isolated application running environment. Its working principle is as follows: 1. The mirror is used as a read-only template, which contains everything you need to run the application; 2. The Union File System (UnionFS) stacks multiple file systems, only storing the differences, saving space and speeding up; 3. The daemon manages the mirrors and containers, and the client uses them for interaction; 4. Namespaces and cgroups implement container isolation and resource limitations; 5. Multiple network modes support container interconnection. Only by understanding these core concepts can you better utilize Docker.

VS Code system requirements: Operating system: Windows 10 and above, macOS 10.12 and above, Linux distribution processor: minimum 1.6 GHz, recommended 2.0 GHz and above memory: minimum 512 MB, recommended 4 GB and above storage space: minimum 250 MB, recommended 1 GB and above other requirements: stable network connection, Xorg/Wayland (Linux)
