{"id":460,"date":"2025-10-13T01:19:00","date_gmt":"2025-10-13T01:19:00","guid":{"rendered":"https:\/\/blog.ngocha.biz\/?p=460"},"modified":"2025-10-13T01:19:00","modified_gmt":"2025-10-13T01:19:00","slug":"list-linux-networking-troubleshooting-and-commands-beginners","status":"publish","type":"post","link":"https:\/\/blog.ngocha.biz\/?p=460","title":{"rendered":"17 Best Linux Networking and Troubleshooting Commands"},"content":{"rendered":"

Network configuration, diagnostics and general Linux troubleshooting <\/strong>are <\/strong>essential parts of System administration. Even for a developer who works with Linux systems, knowledge about Linux networking commands<\/strong> is an added advantage.<\/p>\n

Specifically, if you want to become a DevOps engineer<\/a> or be part of SRE, it is essential to know all the Linux troubleshooting commands<\/strong> as they will be part of your day-to-day activities.<\/p>\n

Also, in real-world production systems, knowing how to diagnose DNS failures, slow connections, or blocked ports is very important. <\/p>\n

This post will cover the important linux networking and troubleshooting commands<\/strong> that are natively available in Linux systems.<\/p>\n

What are the best Linux Networking and Troubleshooting Commands?<\/h2>\n

Following is the list of natively available troubleshooting commands.<\/p>\n

<\/p>\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
Command <\/strong><\/td>\nDescription<\/strong><\/td>\n<\/tr>\n
hostname<\/strong><\/code><\/td>\nTo check and set the hostname of the server.<\/td>\n<\/tr>\n
host<\/strong><\/code><\/td>\nTo get host DNS details<\/td>\n<\/tr>\n
ping<\/strong><\/code><\/td>\nChecks if the remote server is reachable using ICMP protocol<\/a>. It also shows the round trip time of packets.<\/td>\n<\/tr>\n
curl<\/strong><\/code><\/td>\nA cross-platform utility that is used to transfer data. It can be used for troubleshooting several network issues.<\/td>\n<\/tr>\n
wget<\/strong><\/code> <\/td>\nUtility to download files. Can be used for troubleshooting proxy connections and connectivity.<\/td>\n<\/tr>\n
ip<\/strong><\/code><\/td>\nA replacement for ifconfig<\/code>. Can be used to configure and retrieve information about systems network interfaces<\/td>\n<\/tr>\n
arp<\/strong><\/code><\/td>\nUtility to view and manage arp cache<\/a>. <\/td>\n<\/tr>\n
ss\/netstat<\/strong><\/code><\/td>\nPrimarily used to check the connections and PID on ports and Unix sockets.<\/td>\n<\/tr>\n
traceroute<\/strong><\/code><\/td>\nThis utility uses the ICMP protocol and finds the hops involved in reading the destination server. It also shows the time it takes between hops. <\/td>\n<\/tr>\n
mtr<\/strong><\/code><\/td>\nmtr is a mix of ping<\/code> and traceroute<\/code>. It also provides additional information like intermediate hosts and responsiveness.<\/td>\n<\/tr>\n
dig<\/strong><\/code><\/td>\nHelps you get the DNS records associated with a domain name.<\/td>\n<\/tr>\n
nslookup<\/strong><\/code><\/td>\nCommand similar to dig.<\/td>\n<\/tr>\n
nc<\/strong><\/code><\/td>\nutility to debug TCP\/UDP sockets.<\/td>\n<\/tr>\n
telnet<\/strong><\/code><\/td>\nIt can be used to test remote connectivity on ports<\/td>\n<\/tr>\n
route<\/strong><\/code><\/td>\nHelps you get all the route table information<\/td>\n<\/tr>\n
tcpdump<\/strong><\/code><\/td>\nThis utility helps you to capture network packets and analyze them for network issues.<\/td>\n<\/tr>\n
lsof<\/code><\/strong><\/td>\nlist all the open files and the process information that opened it<\/td>\n<\/tr>\n
resolvectl<\/code><\/strong><\/td>\nChecks DNS configuration and status<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n

<\/p>\n

Let’s understand each command and see how we can use it to troubleshoot Linux.<\/p>\n

\n
\ud83d\udccc<\/div>\n
Important Note:<\/strong><\/b> Every command\/utility mentioned in this post has many options and flags. <\/p>\n

Every command has a man page and you can use it to identify the flags and options that are required for your use case. <\/p>\n

For example, for ip<\/code> command, you can just type it man ip<\/code> in the terminal to get all the details about that command.<\/div>\n<\/div>\n

1. hostname<\/h3>\n

Hostname command is used to view the hostname of the machine and to set the hostname.<\/p>\n

hostname<\/code><\/pre>\n
You can use the hostname command to set a new hostname for the machine. For example,<\/p>\n
sudo hostname temp.com<\/code><\/pre>\n
If you set the hostname using “hostname<\/code>” command, when you restart the machine, the hostname will change to the name specified in the hostname file ( eg: \/etc\/hostname).<\/p>\n
So if you want to change the hostname permanently, you can use the \/etc\/hosts<\/code> file or relevant hostname file present on the server.<\/p>\n
    \n
  1. For ubuntu machines, you can change it in the \/etc\/hostname<\/code><\/strong> file.<\/li>\n
  2. For RHEL, CentOS and Fedora you can change it in the \/etc\/sysconfig\/network<\/code><\/strong> file.<\/li>\n<\/ol>\n
    2. host<\/h3>\n
    Host command is for the reverse lookup of IP or a DNS name.<\/p>\n
    For example, If you want to find a DNS attached with an IP you can use the host commands as follows.<\/p>\n
    host 8.8.8.8<\/code><\/pre>\n
    You can also do the reverse to find the IP address associated with the domain name. For example,<\/p>\n
    host devopscube.com<\/code><\/pre>\n
    3. ping<\/h3>\n
    The ping networking utility is used to check if the remote server is reachable or not. It is primarily used for checking the connectivity and troubleshooting the network.<\/p>\n
    It provides the following details.<\/p>\n
      \n
    1. Bytes sent and received<\/li>\n
    2. Packets sent, received, and lost<\/li>\n
    3. Approximate round-trip time (in milliseconds)<\/li>\n<\/ol>\n
      Ping command has the following syntax.<\/p>\n
      ping <IP or DNS><\/code><\/pre>\n
      For example,<\/p>\n
      ping devopscube.com<\/code><\/pre>\n
      To ping IP address<\/p>\n
      ping 8.8.8.8<\/code><\/pre>\n
      If you want to limit the ping output without using ctrl+c, then you can use the “-c” flag with a number as shown below.<\/p>\n
      ping -c 1 devopscube.com<\/code><\/pre>\n
      4. curl<\/h3>\n
      Curl utility is primarily used to transfer data from or to a server. However, you can use it for network troubleshooting.<\/p>\n
      For network troubleshooting, curl<\/code> supports protocols such as DICT<\/code>, FILE<\/code>, FTP<\/code>, FTPS<\/code>, GOPHER<\/code>, HTTP<\/code>, HTTPS<\/code>, IMAP<\/code>, IMAPS<\/code>, LDAP<\/code>, LDAPS<\/code>, MQTT<\/code>, POP3<\/code>, POP3S<\/code>, RTMP<\/code>, RTMPS<\/code>, RTSP<\/code>, SCP<\/code>, SFTP<\/code>, SMB<\/code>, SMBS<\/code>, SMTP<\/code>, SMTPS<\/code>, TELNET<\/code> and TFTP<\/code><\/p>\n
      For example, curl<\/code> can check connectivity on port 22 using telnet.<\/p>\n
      curl -v telnet:\/\/192.168.33.10:22<\/code><\/pre>\n
      You can check the FTP connectivity using curl.<\/p>\n
      curl ftp:\/\/ftptest.net <\/code><\/pre>\n
      You can troubleshoot web server connectivity as well.<\/p>\n
      curl http:\/\/devopscube.com -I<\/code><\/pre>\n
      5. wget<\/h3>\n
      The wget<\/code> command is primarily used to fetch web pages.<\/p>\n
      You can use wget<\/code> to troubleshoot network issues as well.<\/p>\n
      For example, you can troubleshoot proxy server<\/a> connections using wget.<\/p>\n
      wget -e use_proxy=yes http_proxy=<proxy_host:port> http:\/\/externalsite.com<\/code><\/pre>\n
      You can check if a website is up by fetching the files.<\/p>\n
      wget www.google.com<\/code><\/pre>\n
      6. ip (ifconfig)<\/h3>\n
      ip<\/code><\/strong> command is used to display and manipulate routes and network interfaces. ip<\/strong> command is the newer version of ifconfig<\/code>.<\/strong> ifconfig works in all the systems, but it is better to use ip command instead of ifconfig.<\/p>\n
      Let’s have a look at a few examples of ip<\/code> command.<\/p>\n
      Display network devices and configuration<\/h4>\n
      ip addr<\/code><\/pre>\n
      You can use this command with pipes and grep to get more granular output like the IP address of the eth0 interface. It is very useful when you work on automation tools<\/a> that require IP to be fetched dynamically.<\/p>\n
      The following command gets the IP address of eth0<\/code> network interface.<\/p>\n
      ip a | grep eth0  | grep \"inet\" | awk -F\" \" '{print $2}'<\/code><\/pre>\n
      Get details of a specific interface<\/p>\n
      ip a show eth0<\/code><\/pre>\n
      You can list the routing tables.<\/p>\n
      ip route\nip route list<\/code><\/pre>\n
      7. arp<\/h3>\n
      ARP (Address Resolution Protocol<\/strong>) shows the cache table of local networks’ IP addresses and MAC addresses that the system interacted with.<\/p>\n
      arp<\/code><\/pre>\n
      Example output,<\/p>\n
      vagrant@dcubelab:~$ arp\nAddress                  HWtype  HWaddress           Flags Mask            Iface\n10.0.2.3                 ether   52:54:00:12:35:03   C                     eth0\n192.168.33.1             ether   0a:00:27:00:00:00   C                     eth1\n10.0.2.2                 ether   52:54:00:12:35:02   C                     eth0<\/code><\/pre>\n
      8. ss (netstat)<\/h3>\n
      The ss<\/code> command is a replacement for netstat<\/code>. You can still use the netstat<\/code> command on all systems.<\/p>\n
      Using ss<\/code> command, you can get more information than netstat<\/code> command. ss command is fast because it gets all the information from the kernel userspace.<\/p>\n
      Now let’s have a look at a few usages of ss<\/code> command.<\/p>\n
      Listing all connections<\/h4>\n
      The “ss<\/code>” command will list all the TCP, UDP, and Unix socket connections on your machine.<\/p>\n
      ubuntu@devopscube:~$ ss\nNetid  State      Recv-Q Send-Q   Local Address:Port       Peer Address:Port\nu_str  ESTAB      0      0                    * 7594                  * 0\nu_str  ESTAB      0      0      @\/com\/ubuntu\/upstart 7605                  * 0  \nu_str  ESTAB      0      0                    * 29701                 * 0\nu_str  ESTAB      0      0      \/var\/run\/dbus\/system_bus_socket 29702                 * 0\ntcp    ESTAB      0      400      172.31.18.184:ssh         1.22.167.31:61808<\/code><\/pre>\n
      The output of the ss<\/code> command will be big so you can use ” ss | less<\/code> ” command to make the output scrollable.<\/p>\n
      Filtering out TCP, UDP and Unix sockets<\/h4>\n
      If you want to filter out TCP , UDP or UNIX socket details, use “-t” “-u” and “-x” flag with the “ss” command. It will show all the established connections to the specific ports. If you want to list both connected and listening ports using “a” with the specific flag as shown below.<\/p>\n
      ss -ta\nss -ua\nss -xa<\/code><\/pre>\n
      List all listening ports<\/h4>\n
      To list all the listening ports, use “-l” flag with ss command. To list specific TCP, UDP or UNIX socket, use “-t”, “-u” and “-x” flag with “-l” as shown below.<\/p>\n
      ubuntu@devopscube:~$ ss -lt\nState      Recv-Q Send-Q      Local Address:Port          Peer Address:Port\nLISTEN     0      128                     *:ssh                      *:*\nLISTEN     0      50                     :::http-alt                 :::*\nLISTEN     0      50                     :::55857                   :::*\nLISTEN     0      128                    :::ssh                     :::*\nLISTEN     0      50                     :::53285                   :::*\nubuntu@devopscube:~$\n<\/code><\/pre>\n
      List all established<\/h4>\n
      To list all the established ports, use the state established<\/code> flag as shown below.<\/p>\n
      ss -t -r state established<\/code><\/pre>\n
      To list all sockets in listening state,<\/p>\n
      ss -t -r state listening<\/code><\/pre>\n
      9. traceroute<\/h3>\n
      If you do not have a traceroute<\/code> utility in your system or server, you can install it from the native repository.<\/p>\n
      traceroute<\/code> is a network troubleshooting utility. Using traceroute you can find the number of hops required for a particular packet to reach the destination. You can essentially trace the path of the packet from your server to the remote host.<\/p>\n
      For example,<\/p>\n
      traceroute google.com<\/code><\/pre>\n
      Here is the output.<\/p>\n
      traceroute to google.com (173.194.33.163), 30 hops max, 60 byte packets\n 1  ec2-50-112-0-84.us-west-2.compute.amazonaws.com (50.112.0.84)  1.974 ms  1.895 ms  1.899 ms\n 2  100.64.1.247 (100.64.1.247)  1.414 ms 100.64.1.137 (100.64.1.137)  1.127 ms 100.64.1.97 (100.64.1.97)  1.313 ms\n 3  100.64.0.198 (100.64.0.198)  1.443 ms 100.64.0.62 (100.64.0.62)  2.160 ms 100.64.0.60 (100.64.0.60)  2.116 ms\n10  66.249.94.214 (66.249.94.214)  6.313 ms  7.104 ms 209.85.249.34 (209.85.249.34)  5.986 ms\n11  209.85.244.65 (209.85.244.65)  6.157 ms  6.341 ms  6.574 m.\n.\n12  sea09s18-in-f3.1e100.net (173.194.33.163)  6.302 ms  6.517 ms  6.071 ms\nubuntu@devopscube:~$<\/code><\/pre>\n
      The above output shows the hop count (12) to reach google.com from devopscube AWS ec2 server.<\/p>\n
      This utiltity comes in handy when you want to troubleshoot issues related to network packets not reaching the host.<\/p>\n
      10. mtr<\/h3>\n
      The mtr<\/code> utility is a network diagnostic tool to troubleshoot the network bottlenecks. It combines the functionality of both ping<\/code> and traceroute<\/code><\/p>\n
      For example, the following command shows the traceroute<\/code> output in real-time.<\/p>\n
      mtr google.com<\/code><\/pre>\n
      Here is the output.<\/p>\n
      \"mtr<\/figure>\n
      mtr report<\/h4>\n
      You can generate a report using the –report flag. When you run the mtr report, it sends 10 packets to the destination and creates the report.<\/p>\n
      mtr -n --report google.com<\/code><\/pre>\n
      \"network<\/figure>\n
      11. dig<\/h3>\n
      If you have any task related to DNS lookup, you can use “dig<\/code>” command to query the DNS name servers.<\/p>\n
      Get all DNS records with dig<\/h4>\n
      The following command returns all the DNS records and TTL information of a twitter.com<\/p>\n
      dig twiter.com ANY<\/code><\/pre>\n
      \"all<\/figure>\n
      Use +short<\/code> to get the output without verbose.<\/p>\n
      dig google.com ANY +short<\/code><\/pre>\n
      Get Specific DNS Record with dig<\/h4>\n
      For example, If you want to get the A record<\/code> for the particular domain name, you can use the dig command.  +short<\/code> will provide the information without verbose<\/p>\n
      dig www.google.com A +short<\/code><\/pre>\n
      Similarly, you can get the other record information separately using the following commands.<\/p>\n
      dig google.com CNAME +short\ndig google.com MX +short\ndig google.com TXT +short\ndig google.com NS +short\n<\/code><\/pre>\n
      Reverse DNS Lookup with dig<\/h4>\n
      You can perform a reverse DNS lookup with dig using the following command. Replace 8.8.8.8<\/code> with the required IP<\/p>\n
      dig -x 8.8.8.8<\/code><\/pre>\n
      12. nslookup<\/h3>\n
      Nslookup <\/strong>(Name Server Lookup) utility is used to check the DNS entries. It is similar to dig command.<\/p>\n
      To check the DNS records of a domain, you can use the following command.<\/p>\n
      nslookup google.com<\/code><\/pre>\n
      You can also do a reverse lookup with the IP address.<\/p>\n
      nslookup 8.8.8.8<\/code><\/pre>\n
      To get all the DNS records of a domain name, you can use the following.<\/p>\n
      nslookup -type=any google.com<\/code><\/pre>\n
      Similarly, you can query for records like mx<\/code>, soa<\/code> etc<\/p>\n
      13. nc (netcat)<\/h3>\n
      The nc<\/code> (netcat) command is known as the swiss army of networking commands.<\/p>\n
      Using nc<\/code>, you can check the connectivity of a service running on a specific port.<\/p>\n
      For example, to check if ssh<\/code> port is open, you can use the following command.<\/p>\n
      nc -v -n 192.168.33.10 22<\/code><\/pre>\n
      netcat<\/code> can also be used for data transfer over TCP\/UDP and port scanning.<\/p>\n
      Port scanning is not recommended in cloud environments. You need to request the cloud provider to perform port scanning operations in your environment.<\/p>\n
      14. telnet<\/h3>\n
      The telnet command is used to troubleshoot the TCP connections on a port.<\/p>\n
      To check port connectivity using telnet, use the following command.<\/p>\n
      telnet 10.4.5.5 22<\/code><\/pre>\n
      15. route<\/h3>\n
      The “route<\/code>” command is used to get the details of the route table for your system and to manipulate it. Let us look at a few examples for the route command.<\/p>\n
      Listing all routes<\/h4>\n
      Execute the “route<\/code>” command without any arguments to list all the existing routes in your system or server.<\/p>\n
      ubuntu@devopscube:~$ route\nKernel IP routing table\nDestination     Gateway         Genmask         Flags Metric Ref    Use Iface\ndefault         ip-172-31-16-1. 0.0.0.0         UG    0      0        0 eth0\n172.17.0.0      *               255.255.0.0     U     0      0        0 docker0\n172.31.16.0     *               255.255.240.0   U     0      0        0 eth0\nubuntu@devopscube:~$<\/code><\/pre>\n
      If you want to get the full output in numerical form without any hostname, you can use “-n” flag with the route  command.<\/p>\n
      ubuntu@devopscube:~$ route -n\nKernel IP routing table\nDestination     Gateway         Genmask         Flags Metric Ref    Use Iface\n0.0.0.0         172.31.16.1     0.0.0.0         UG    0      0        0 eth0\n172.17.0.0      0.0.0.0         255.255.0.0     U     0      0        0 docker0\n172.31.16.0     0.0.0.0         255.255.240.0   U     0      0        0 eth0\nubuntu@devopscube:~$<\/code><\/pre>\n
      16. tcpdump<\/h3>\n
      The tcpdump<\/code> command is primarily used for troubleshooting network traffic.<\/p>\n
      \n
      Note:<\/strong><\/b> To analyze the output of tcpdump<\/code> command requires some learning, so explaining it is out of the scope of this article.<\/div>\n<\/div>\n
      tcpdump<\/code> command works with the network interfaces of the system. So you need to use administrative privileges to execute the command.<\/p>\n
      List all network interfaces<\/h4>\n
      Use the following command to list all the interfaces.<\/p>\n
      sudo  tcpdump --list-interfaces<\/code><\/pre>\n
      Capture Packets on Specific Interface<\/h4>\n
      To get the dump of packets on a specific interface, you can use the following command.<\/p>\n
      \n
      Note:<\/strong><\/b> press ctrl + c <\/code>to stop capturing the packets.<\/div>\n<\/div>\n
      sudo tcpdump -i eth0<\/code><\/pre>\n
      To limit the packet capturing, you can use the -c<\/code> flag with the number.<\/p>\n
      For example,<\/p>\n
      sudo tcpdump -i eth0 -c 10<\/code><\/pre>\n
      Capture Packets on All Interfaces<\/h4>\n
      To capture packets on all the interfaces, use the any<\/code> flag as shown below.<\/p>\n
      sudo tcpdump -i any<\/code><\/pre>\n
      17. lsof<\/h3>\n
      lsof<\/code> is a command that would used in day to day linux troubleshooting. This command is equally important for anyone working with Linux systems.<\/p>\n
      To list all open files, execute the lsof<\/code> command.<\/p>\n
      lsof<\/code><\/pre>\n
      One of the common error face by developers & DevOps engineers is “Bind failed error: Address already in use<\/strong>“. You can find the process ID associated with a port using the following command. The you can kill the process to free up the port.<\/p>\n
      lsof -i :8080<\/code><\/pre>\n
      18. resolvectl<\/h3>\n
      With resolvectl you can checks DNS configuration and status in systems using systemd-resolved<\/code>.<\/p>\n
      $ resolvectl query devopscube.com\n\ndevopscube.com: 151.101.67.7                   -- link: enp1s0\n                151.101.3.7                    -- link: enp1s0\n                151.101.195.7                  -- link: enp1s0\n                151.101.131.7                  -- link: enp1s0\n                2a04:4e42:600::775             -- link: enp1s0\n                2a04:4e42::775                 -- link: enp1s0\n                2a04:4e42:400::775             -- link: enp1s0\n                2a04:4e42:200::775             -- link: enp1s0\n\n-- Information acquired via protocol DNS in 82.9ms.\n-- Data is authenticated: no; Data was acquired via local or encrypted transport: no\n-- Data from: network<\/code><\/pre>\n
      It basically replaces the older \/etc\/resolv.conf   based checks in modern systems<\/p>\n
      Bonus Tools for DevOps\/SRE<\/h2>\n
      There are more networking troubleshooting command-line utilities available from third-party solutions.<\/p>\n
      You need to install them separately and use them for your troubleshooting purposes. Due to security compliance reasons, not every organisation will allow you to do it.<\/p>\n
      However, if you have to option to use third-party tools, you can explore them.<\/p>\n
      We have organized some tool information under different categories in the following table.<\/p>\n
      <\/p>\n\n\n\n\n\n\n\n\n\n\n\n\n\n
      Category<\/th>\nOpen-Source Tools<\/th>\n<\/tr>\n<\/thead>\n
      Network Scanners<\/strong><\/td>\nNmap, Zenmap (GUI for Nmap)<\/td>\n<\/tr>\n
      Packet Analyzers<\/strong><\/td>\nWireshark, Tcpdump<\/td>\n<\/tr>\n
      Bandwidth Monitors<\/strong><\/td>\nBandwidthD, Cacti<\/td>\n<\/tr>\n
      Port Scanners<\/strong><\/td>\nNmap, Masscan<\/td>\n<\/tr>\n
      Ping\/Traceroute Tools<\/strong><\/td>\nMTR (My Traceroute)<\/td>\n<\/tr>\n
      Wireless Network Analyzers<\/strong><\/td>\nWireshark (for wireless), Kismet<\/td>\n<\/tr>\n
      Network Simulators<\/strong><\/td>\nGNS3, Mininet<\/td>\n<\/tr>\n
      DNS Performance<\/strong><\/td>\nDNSperf, dnstop<\/td>\n<\/tr>\n
      Network Performance Testing<\/strong><\/td>\niperf3, netperf<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n
      <\/p>\n
      Conclusion<\/h2>\n
      In this article, we have covered the important Linux command-line utilities for network troubleshooting and configuration.<\/strong><\/p>\n
      If you are getting started with system administration, DevOps, or SRE roles, it is essential to learn about these utilities to support the projects you are working on.<\/p>\n
      Each utility has many functionalities, and you can explore further to meet your requirements.<\/p>\n
      If you think we missed any important commands,  let us know in the comments section.<\/p>\n
      Also, if you want to learn shell scripting, check out our guide on how to learn shell scripting<\/a>. If you are developers, check out my guide on Linux Commands <\/a>every Developer should know.<\/p>\n
      \n
      Ngu\u1ed3n:<\/strong> 17 Best Linux Networking and Troubleshooting Commands \u2014 DevOpsCube<\/a><\/p>\n","protected":false},"excerpt":{"rendered":"
      Source: https:\/\/devopscube.com\/list-linux-networking-troubleshooting-and-commands-beginners\/<\/p>\n","protected":false},"author":1,"featured_media":461,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[1],"tags":[],"class_list":["post-460","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-devops"],"_links":{"self":[{"href":"https:\/\/blog.ngocha.biz\/index.php?rest_route=\/wp\/v2\/posts\/460","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/blog.ngocha.biz\/index.php?rest_route=\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/blog.ngocha.biz\/index.php?rest_route=\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/blog.ngocha.biz\/index.php?rest_route=\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/blog.ngocha.biz\/index.php?rest_route=%2Fwp%2Fv2%2Fcomments&post=460"}],"version-history":[{"count":0,"href":"https:\/\/blog.ngocha.biz\/index.php?rest_route=\/wp\/v2\/posts\/460\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/blog.ngocha.biz\/index.php?rest_route=\/wp\/v2\/media\/461"}],"wp:attachment":[{"href":"https:\/\/blog.ngocha.biz\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=460"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/blog.ngocha.biz\/index.php?rest_route=%2Fwp%2Fv2%2Fcategories&post=460"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/blog.ngocha.biz\/index.php?rest_route=%2Fwp%2Fv2%2Ftags&post=460"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}