{"id":5056,"date":"2018-06-20T18:34:52","date_gmt":"2018-06-20T14:34:52","guid":{"rendered":"https:\/\/www.howtoforge.com\/linux-netstat-command\/"},"modified":"2018-06-20T18:34:52","modified_gmt":"2018-06-20T14:34:52","slug":"linux-netstat-command-tutorial-for-beginners-8-examples","status":"publish","type":"post","link":"https:\/\/afaghhosting.net\/blog\/linux-netstat-command-tutorial-for-beginners-8-examples\/","title":{"rendered":"Linux netstat Command Tutorial for Beginners (8 Examples)"},"content":{"rendered":"<p>If you are new to Linux command line, and are interested in learning networking stuff, there are many command line utilities that you should be aware of. One such tool is <strong>netstat<\/strong>. In this article, we will discuss this command using some easy to understand examples.<\/p>\n<p>But before we do that, it&#8217;s worth mentioning that all these examples have been tested on an Ubuntu 16.04 LTS machine.<\/p>\n<h2 id=\"linux-netstat-command\">Linux netstat command<\/h2>\n<p>The netstat command lets you print network connections, routing tables, interface statistics, masquerade connections, and multicast memberships. Following is its syntax:<\/p>\n<p class=\"command\">netstat [OPTIONS]\n<p>Here&#8217;s how the man page explains it:<\/p>\n<pre readability=\"25\"> Netstat\u00a0 prints\u00a0 information about the Linux networking subsystem.\u00a0 The<br\/>\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 type of information printed is controlled by\u00a0 the\u00a0 first\u00a0 argument,\u00a0 as<br\/>\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 follows:<p>\u00a0\u00a0 (none)<br\/>\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 By\u00a0 default,\u00a0 netstat\u00a0 displays\u00a0 a\u00a0 list of open sockets.\u00a0 If you don't<br\/>\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 specify any address families, then the active sockets of all configured<br\/>\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 address families will be printed.<\/p><p>\u00a0\u00a0 --route , -r<br\/>\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 Display\u00a0 the kernel routing tables. See the description in route(8) for<br\/>\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 details.\u00a0 netstat -r and route -e produce the same output.<\/p><p>\u00a0\u00a0 --groups , -g<br\/>\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 Display multicast group membership information for IPv4 and IPv6.<\/p><p>\u00a0\u00a0 --interfaces, -i<br\/>\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 Display a table of all network interfaces.<\/p><p>\u00a0\u00a0 --masquerade , -M<br\/>\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 Display a list of masqueraded connections.<\/p><p>\u00a0\u00a0 --statistics , -s<br\/>\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 Display summary statistics for each protocol.<\/p><\/pre>\n<p>Following are some Q&amp;A-styled examples that should give you a good idea on how the netstat command works.<\/p>\n<h2 id=\"q-how-to-use-netstat-command\">Q1. How to use netstat command?<\/h2>\n<p>Basic usage is fairly simple &#8211; just run the netstat command without any options.<\/p>\n<p class=\"command\">netstat<\/p>\n<p>For example, in my case, the following output was produced:<\/p>\n<pre>Active Internet connections (w\/o servers)<br\/>Proto Recv-Q Send-Q Local Address\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 Foreign Address\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 State\u00a0\u00a0\u00a0\u00a0 \u00a0<br\/>tcp\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 0\u00a0\u00a0\u00a0\u00a0\u00a0 0 192.168.1.7:59510\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 mails11.telegram.:https ESTABLISHED<br\/>tcp\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 0\u00a0\u00a0\u00a0\u00a0\u00a0 0 192.168.1.7:57318\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 13.70.5.200:https\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 ESTABLISHED<br\/>tcp\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 0\u00a0\u00a0\u00a0\u00a0\u00a0 1 192.168.1.7:51238\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 52.114.32.7:https\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 SYN_SENT\u00a0 \u00a0<br\/>tcp\u00a0\u00a0\u00a0\u00a0\u00a0 390\u00a0\u00a0\u00a0\u00a0\u00a0 0 192.168.1.7:60392\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 del03s09-in-f10.1:https ESTABLISHED<br\/>tcp\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 0\u00a0\u00a0\u00a0\u00a0\u00a0 1 192.168.1.7:51240\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 52.114.32.7:https\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 SYN_SENT\u00a0 \u00a0<br\/>tcp\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 0\u00a0\u00a0\u00a0\u00a0\u00a0 0 192.168.1.7:50196\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 del03s10-in-f10.1:https TIME_WAIT \u00a0<br\/>tcp\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 0\u00a0\u00a0\u00a0\u00a0\u00a0 0 192.168.1.7:41996\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 maa05s05-in-f4.1e:https TIME_WAIT \u00a0<br\/>tcp\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 0\u00a0\u00a0\u00a0\u00a0\u00a0 0 192.168.1.7:56680\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 wa-in-f94.1e100.n:https ESTABLISHED<br\/>tcp\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 0\u00a0\u00a0\u00a0\u00a0\u00a0 0 192.168.1.7:54578\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 del03s10-in-f14.1:https TIME_WAIT \u00a0<br\/>tcp\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 0\u00a0\u00a0\u00a0\u00a0\u00a0 0 192.168.1.7:51310\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 del03s10-in-f2.1e:https TIME_WAIT<\/pre>\n<p>So by default, the command displays a list of all open sockets.<\/p>\n<h2 id=\"q-how-to-make-netstat-show-numerical-addresses\">Q2. How to make netstat show numerical addresses?<\/h2>\n<p>By default, the netstat command tries to determine symbolic host, port, or user names. This may slow down the tool. However, if you&#8217;re fine with numerical values, you can make the tool output numeric values using the -n command line option.<\/p>\n<p class=\"command\">netstat -n<\/p>\n<p>For example in my case, the following output was produced:<\/p>\n<pre>Active Internet connections (w\/o servers)<br\/>Proto Recv-Q Send-Q Local Address\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 Foreign Address\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 State\u00a0\u00a0\u00a0\u00a0 \u00a0<br\/>tcp\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 0\u00a0\u00a0\u00a0\u00a0\u00a0 0 192.168.1.7:59510\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 149.154.171.22:443\u00a0\u00a0\u00a0\u00a0\u00a0 ESTABLISHED<br\/>tcp\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 0\u00a0\u00a0\u00a0\u00a0\u00a0 0 192.168.1.7:57318\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 13.70.5.200:443\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 ESTABLISHED<br\/>tcp\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 0\u00a0\u00a0\u00a0\u00a0\u00a0 0 192.168.1.7:51682\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 52.114.32.7:443\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 TIME_WAIT \u00a0<br\/>tcp\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 0\u00a0\u00a0\u00a0\u00a0\u00a0 0 192.168.1.7:54884\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 172.217.161.14:443\u00a0\u00a0\u00a0\u00a0\u00a0 TIME_WAIT \u00a0<br\/>tcp\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 0\u00a0\u00a0\u00a0\u00a0\u00a0 0 192.168.1.7:35112\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 172.217.161.5:443\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 ESTABLISHED<br\/>tcp\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 0\u00a0\u00a0\u00a0\u00a0\u00a0 0 192.168.2.97:45662\u00a0\u00a0\u00a0\u00a0\u00a0 148.251.237.53:21\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 ESTABLISHED<br\/>tcp\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 0\u00a0\u00a0\u00a0\u00a0\u00a0 0 192.168.1.7:50892\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 149.154.164.224:443\u00a0\u00a0\u00a0\u00a0 ESTABLISHED<br\/>tcp\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 0\u00a0\u00a0\u00a0\u00a0\u00a0 0 192.168.1.7:58772\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 172.217.194.189:443\u00a0\u00a0\u00a0\u00a0 TIME_WAIT \u00a0<br\/>tcp\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 0\u00a0\u00a0\u00a0\u00a0\u00a0 1 192.168.1.7:47728\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 144.76.158.93:443\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 SYN_SENT\u00a0 \u00a0<br\/>tcp\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 0\u00a0\u00a0\u00a0\u00a0\u00a0 1 192.168.1.7:47730\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 144.76.158.93:443\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 SYN_SENT\u00a0 \u00a0<br\/>tcp\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 0\u00a0\u00a0\u00a0\u00a0\u00a0 0 192.168.1.7:59548\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 149.154.171.22:443\u00a0\u00a0\u00a0\u00a0\u00a0 ESTABLISHED<br\/>tcp\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 0\u00a0\u00a0\u00a0\u00a0\u00a0 0 192.168.1.7:35818\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 169.55.74.50:443\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 ESTABLISHED<br\/>tcp\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 0\u00a0\u00a0\u00a0\u00a0\u00a0 0 192.168.1.7:50888\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 149.154.164.224:443\u00a0\u00a0\u00a0\u00a0 ESTABLISHED<br\/>tcp\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 0\u00a0\u00a0\u00a0\u00a0\u00a0 0 192.168.1.7:44156\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 152.195.11.6:443\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 ESTABLISHED<br\/>tcp\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 0\u00a0\u00a0\u00a0\u00a0\u00a0 0 192.168.1.7:58478\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 52.229.174.94:443\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 ESTABLISHED<br\/>tcp\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 52\u00a0\u00a0\u00a0\u00a0\u00a0 0 127.0.0.1:60342\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 127.0.1.1:139\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 ESTABLISHED<br\/>tcp\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 0\u00a0\u00a0\u00a0\u00a0\u00a0 0 192.168.1.7:58820\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 172.217.161.3:443\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 ESTABLISHED<br\/>tcp\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 0\u00a0\u00a0\u00a0\u00a0\u00a0 0 192.168.1.7:45588\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 52.175.17.224:443\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 TIME_WAIT \u00a0<br\/>tcp\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 0\u00a0\u00a0\u00a0\u00a0\u00a0 0 192.168.1.7:50890\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 149.154.164.224:443\u00a0\u00a0\u00a0\u00a0 ESTABLISHED<br\/>tcp\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 0\u00a0\u00a0\u00a0\u00a0\u00a0 0 192.168.1.7:58192\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 52.77.195.144:443\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 ESTABLISHED<br\/>tcp\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 0\u00a0\u00a0\u00a0\u00a0\u00a0 0 192.168.1.7:54224\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 172.217.31.2:443\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 ESTABLISHED<br\/>tcp\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 0\u00a0\u00a0\u00a0\u00a0\u00a0 0 127.0.1.1:139\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 127.0.0.1:60342\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 ESTABLISHED<br\/>tcp\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 0\u00a0\u00a0\u00a0\u00a0\u00a0 0 192.168.1.7:34500\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 192.241.190.153:443\u00a0\u00a0\u00a0\u00a0 ESTABLISHED<br\/>tcp\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 0\u00a0\u00a0\u00a0\u00a0\u00a0 0 192.168.1.7:54888\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 172.217.161.14:443\u00a0\u00a0\u00a0\u00a0\u00a0 ESTABLISHED<\/pre>\n<p>So you can see only numeric values were produced in output (in Foreign Adress column) this time.<\/p>\n<h2 id=\"q-how-to-make-netstat-display-only-tcp-connections\">Q3. How to make netstat display only tcp connections?<\/h2>\n<p>This you can do using the -t command line option.<\/p>\n<p class=\"command\">netstat -t<\/p>\n<p>For example, in my case, the following output was produced:<\/p>\n<pre>Active Internet connections (w\/o servers)<br\/>Proto Recv-Q Send-Q Local Address\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 Foreign Address\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 State\u00a0\u00a0\u00a0\u00a0 \u00a0<br\/>tcp\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 0\u00a0\u00a0\u00a0\u00a0\u00a0 0 192.168.1.7:44236\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 152.195.11.6:https\u00a0\u00a0\u00a0\u00a0\u00a0 ESTABLISHED<br\/>tcp\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 0\u00a0\u00a0\u00a0\u00a0\u00a0 0 192.168.1.7:59510\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 mails11.telegram.:https ESTABLISHED<br\/>tcp\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 0\u00a0\u00a0\u00a0\u00a0\u00a0 0 192.168.1.7:57318\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 13.70.5.200:https\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 ESTABLISHED<br\/>tcp\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 0\u00a0\u00a0\u00a0\u00a0\u00a0 0 192.168.1.7:42706\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 maa05s05-in-f4.1e:https ESTABLISHED<br\/>tcp\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 0\u00a0\u00a0\u00a0\u00a0\u00a0 0 192.168.1.7:51984\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 del03s10-in-f2.1e:https ESTABLISHED<br\/>tcp\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 0\u00a0\u00a0\u00a0\u00a0\u00a0 0 192.168.1.7:51786\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 52.114.32.7:https\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 ESTABLISHED<br\/>tcp\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 0\u00a0\u00a0\u00a0\u00a0\u00a0 0 192.168.1.7:52294\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 xx-fbcdn-shv-01-m:https ESTABLISHED<br\/>tcp\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 0\u00a0\u00a0\u00a0\u00a0\u00a0 0 192.168.1.7:54372\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 del03s01-in-f2.1e:https ESTABLISHED<br\/>tcp\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 0\u00a0\u00a0\u00a0\u00a0\u00a0 1 192.168.1.7:47788\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 hyperserver.semse:https SYN_SENT\u00a0 \u00a0<br\/>tcp\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 0\u00a0\u00a0\u00a0\u00a0\u00a0 0 192.168.1.7:52298\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 xx-fbcdn-shv-01-m:https ESTABLISHED<br\/>tcp\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 0\u00a0\u00a0\u00a0\u00a0\u00a0 0 192.168.1.7:51840\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 149.154.164.224:https\u00a0\u00a0 TIME_WAIT \u00a0<br\/>tcp\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 0\u00a0\u00a0\u00a0\u00a0\u00a0 0 192.168.1.7:35258\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 del03s10-in-f1.1e:https ESTABLISHED<br\/>tcp\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 0\u00a0\u00a0\u00a0\u00a0\u00a0 0 192.168.2.97:45662\u00a0\u00a0\u00a0\u00a0\u00a0 blog.gsmarena.com:ftp\u00a0\u00a0 ESTABLISHED<br\/>tcp\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 0\u00a0\u00a0\u00a0\u00a0\u00a0 0 192.168.1.7:50728\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 del03s10-in-f10.1:https TIME_WAIT \u00a0<br\/>tcp\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 0\u00a0\u00a0\u00a0\u00a0\u00a0 0 192.168.1.7:56468\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 del03s09-in-f3.1e:https ESTABLISHED<br\/>tcp\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 0\u00a0\u00a0\u00a0\u00a0\u00a0 0 192.168.1.7:50892\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 149.154.164.224:https\u00a0\u00a0 ESTABLISHED<br\/>tcp\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 0\u00a0\u00a0\u00a0\u00a0\u00a0 0 192.168.1.7:45670\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 52.175.17.224:https\u00a0\u00a0\u00a0\u00a0 ESTABLISHED<br\/>tcp\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 0\u00a0\u00a0\u00a0\u00a0\u00a0 0 192.168.1.7:55180\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 del03s10-in-f14.1:https TIME_WAIT \u00a0<br\/>tcp\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 0\u00a0\u00a0\u00a0\u00a0\u00a0 1 192.168.1.7:47790\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 hyperserver.semse:https SYN_SENT\u00a0 \u00a0<br\/>tcp\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 0\u00a0\u00a0\u00a0\u00a0\u00a0 0 192.168.1.7:59548\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 mails11.telegram.:https ESTABLISHED<br\/>tcp\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 0\u00a0\u00a0\u00a0\u00a0\u00a0 0 192.168.1.7:35818\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 32.4a.37a9.ip4.st:https ESTABLISHED<br\/>tcp\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 0\u00a0\u00a0\u00a0\u00a0\u00a0 0 192.168.1.7:50888\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 149.154.164.224:https\u00a0\u00a0 ESTABLISHED<br\/>tcp\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 0\u00a0\u00a0\u00a0\u00a0\u00a0 0 192.168.1.7:33360\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 del03s10-in-f13.1:https TIME_WAIT \u00a0<br\/>tcp\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 0\u00a0\u00a0\u00a0\u00a0\u00a0 0 192.168.1.7:52332\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 207.46.140.70:https\u00a0\u00a0\u00a0\u00a0 ESTABLISHED<br\/>tcp\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 0\u00a0\u00a0\u00a0\u00a0\u00a0 0 192.168.1.7:58478\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 52.229.174.94:https\u00a0\u00a0\u00a0\u00a0 ESTABLISHED<br\/>tcp\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 0\u00a0\u00a0\u00a0\u00a0\u00a0 0 192.168.1.7:54374\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 del03s01-in-f2.1e:https TIME_WAIT \u00a0<br\/>tcp\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 0\u00a0\u00a0\u00a0\u00a0\u00a0 0 192.168.1.7:50216\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 104.24.1.68:https\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 TIME_WAIT \u00a0<br\/>tcp\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 52\u00a0\u00a0\u00a0\u00a0\u00a0 0 localhost:60342\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 ansh:netbios-ssn\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 ESTABLISHED<br\/>tcp\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 0\u00a0\u00a0\u00a0\u00a0\u00a0 0 192.168.1.7:50890\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 149.154.164.224:https\u00a0\u00a0 ESTABLISHED<br\/>tcp\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 0\u00a0\u00a0\u00a0\u00a0\u00a0 0 192.168.1.7:55200\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 del03s10-in-f14.1:https TIME_WAIT \u00a0<br\/>tcp\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 0\u00a0\u00a0\u00a0\u00a0\u00a0 0 192.168.1.7:54224\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 del03s01-in-f2.1e:https ESTABLISHED<br\/>tcp\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 0\u00a0\u00a0\u00a0\u00a0\u00a0 0 ansh:netbios-ssn\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 localhost:60342\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 ESTABLISHED<br\/>tcp\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 0\u00a0\u00a0\u00a0\u00a0\u00a0 0 192.168.1.7:55212\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 del03s10-in-f14.1:https TIME_WAIT \u00a0<br\/>tcp\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 0\u00a0\u00a0\u00a0\u00a0\u00a0 1 192.168.1.7:47800\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 hyperserver.semse:https SYN_SENT\u00a0 \u00a0<br\/>tcp\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 0\u00a0\u00a0\u00a0\u00a0\u00a0 0 192.168.1.7:45668\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 52.175.17.224:https\u00a0\u00a0\u00a0\u00a0 ESTABLISHED<br\/>tcp\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 0\u00a0\u00a0\u00a0\u00a0\u00a0 0 192.168.1.7:58878\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 del03s10-in-f3.1e:https TIME_WAIT \u00a0<br\/>tcp\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 0\u00a0\u00a0\u00a0\u00a0\u00a0 0 192.168.1.7:34500\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 do-11.lastpass.co:https ESTABLISHED<br\/>tcp\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 0\u00a0\u00a0\u00a0\u00a0\u00a0 0 192.168.1.7:41844\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 a23-35-40-198.dep:https ESTABLISHED<\/pre>\n<h2 id=\"q-how-to-make-netstat-display-only-udp-connections\">Q4. How to make netstat display only udp connections<\/h2>\n<p>This you can do using the -u command line option.<\/p>\n<p class=\"command\">netstat -u<\/p>\n<h2 id=\"q-how-to-make-netstat-show-only-listening-sockets\">Q5. How to make netstat show only listening sockets?<\/h2>\n<p>This is possible by using the -l command line option.<\/p>\n<p class=\"command\">netstat -l<\/p>\n<p>For example, the following output was produced in my case:<\/p>\n<pre>Active Internet connections (only servers)<br\/>Proto Recv-Q Send-Q Local Address\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 Foreign Address\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 State\u00a0\u00a0\u00a0\u00a0 \u00a0<br\/>tcp\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 0\u00a0\u00a0\u00a0\u00a0\u00a0 0 ansh:domain\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 *:*\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 LISTEN\u00a0\u00a0\u00a0 \u00a0<br\/>tcp\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 0\u00a0\u00a0\u00a0\u00a0\u00a0 0 localhost:ipp\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 *:*\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 LISTEN\u00a0\u00a0\u00a0 \u00a0<br\/>tcp\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 0\u00a0\u00a0\u00a0\u00a0\u00a0 0 *:microsoft-ds\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 *:*\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 LISTEN\u00a0\u00a0\u00a0 \u00a0<br\/>tcp\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 0\u00a0\u00a0\u00a0\u00a0\u00a0 0 *:netbios-ssn\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 *:*\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 LISTEN\u00a0\u00a0\u00a0 \u00a0<br\/>tcp6\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 0\u00a0\u00a0\u00a0\u00a0\u00a0 0 ip6-localhost:ipp\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 [::]:*\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 LISTEN\u00a0\u00a0\u00a0 \u00a0<br\/>tcp6\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 0\u00a0\u00a0\u00a0\u00a0\u00a0 0 [::]:microsoft-ds\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 [::]:*\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 LISTEN\u00a0\u00a0\u00a0 \u00a0<br\/>tcp6\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 0\u00a0\u00a0\u00a0\u00a0\u00a0 0 [::]:netbios-ssn\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 [::]:*\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 LISTEN\u00a0\u00a0\u00a0 \u00a0<br\/>...<br\/>...<br\/>...<\/pre>\n<h2 id=\"q-how-to-make-netstat-show-name-and-pid-of-programs\">Q6. How to make netstat show name and PID of programs?<\/h2>\n<p>In case you want netstat to show name of process IDs of processes to which each socket belongs, use the -p command line option.<\/p>\n<p class=\"command\">netstat -p<\/p>\n<p>For example:<\/p>\n<pre>Active Internet connections (w\/o servers)<br\/>Proto Recv-Q Send-Q Local Address\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 Foreign Address\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 State\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 PID\/Program name<br\/>tcp\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 0\u00a0\u00a0\u00a0\u00a0\u00a0 0 192.168.1.7:57318\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 13.70.5.200:https\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 ESTABLISHED 3247\/firefox\u00a0\u00a0 \u00a0<br\/>tcp\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 0\u00a0\u00a0\u00a0\u00a0\u00a0 0 192.168.1.7:36732\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 13.76.170.95:https\u00a0\u00a0\u00a0\u00a0\u00a0 ESTABLISHED 3247\/firefox\u00a0\u00a0 \u00a0<br\/>tcp\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 0\u00a0\u00a0\u00a0\u00a0\u00a0 0 192.168.1.7:52050\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 149.154.164.224:https\u00a0\u00a0 ESTABLISHED 3247\/firefox\u00a0\u00a0 \u00a0<br\/>tcp\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 0\u00a0\u00a0\u00a0\u00a0\u00a0 0 192.168.1.7:55974\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 del03s10-in-f14.1:https ESTABLISHED 3247\/firefox\u00a0\u00a0 \u00a0<br\/>tcp\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 0\u00a0\u00a0\u00a0\u00a0\u00a0 0 192.168.1.7:52074\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 149.154.164.224:https\u00a0\u00a0 ESTABLISHED 3247\/firefox\u00a0\u00a0 \u00a0<br\/>tcp\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 0\u00a0\u00a0\u00a0\u00a0\u00a0 0 192.168.1.7:60590\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 mails11.telegram.:https ESTABLISHED 3247\/firefox\u00a0\u00a0 \u00a0<br\/>tcp\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 0\u00a0\u00a0\u00a0\u00a0\u00a0 0 192.168.1.7:52254\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 149.154.164.224:https\u00a0\u00a0 ESTABLISHED 3247\/firefox\u00a0\u00a0 \u00a0<br\/>tcp\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 0\u00a0\u00a0\u00a0\u00a0\u00a0 0 192.168.2.97:45662\u00a0\u00a0\u00a0\u00a0\u00a0 blog.gsmarena.com:ftp\u00a0\u00a0 ESTABLISHED 3160\/filezilla \u00a0<br\/>tcp\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 0\u00a0\u00a0\u00a0\u00a0\u00a0 0 192.168.1.7:35818\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 32.4a.37a9.ip4.st:https ESTABLISHED 3247\/firefox\u00a0\u00a0 \u00a0<br\/>tcp\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 0\u00a0\u00a0\u00a0\u00a0\u00a0 0 192.168.1.7:52528\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 52.114.32.7:https\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 ESTABLISHED 3247\/firefox\u00a0\u00a0 \u00a0<br\/>tcp\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 0\u00a0\u00a0\u00a0\u00a0\u00a0 0 192.168.1.7:55950\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 del03s10-in-f14.1:https ESTABLISHED 3247\/firefox\u00a0\u00a0 \u00a0<br\/>tcp\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 68\u00a0\u00a0\u00a0\u00a0\u00a0 0 localhost:60342\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 ansh:netbios-ssn\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 ESTABLISHED 2625\/gvfsd-smb-brow<br\/>tcp\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 0\u00a0\u00a0\u00a0\u00a0\u00a0 0 192.168.1.7:44974\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 152.195.11.6:https\u00a0\u00a0\u00a0\u00a0\u00a0 ESTABLISHED 3247\/firefox\u00a0\u00a0 \u00a0<br\/>tcp\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 0\u00a0\u00a0\u00a0\u00a0\u00a0 0 192.168.1.7:36730\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 13.76.170.95:https\u00a0\u00a0\u00a0\u00a0\u00a0 ESTABLISHED 3247\/firefox\u00a0\u00a0 \u00a0<br\/>tcp\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 0\u00a0\u00a0\u00a0\u00a0\u00a0 0 ansh:netbios-ssn\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 localhost:60342\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 ESTABLISHED -\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 \u00a0<br\/>tcp\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 0\u00a0\u00a0\u00a0\u00a0\u00a0 0 192.168.1.7:52732\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 del03s10-in-f2.1e:https ESTABLISHED 3247\/firefox\u00a0\u00a0 \u00a0<br\/>tcp\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 0\u00a0\u00a0\u00a0\u00a0\u00a0 0 192.168.1.7:60314\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 52.229.174.94:https\u00a0\u00a0\u00a0\u00a0 ESTABLISHED 3247\/firefox\u00a0\u00a0 \u00a0<br\/>tcp\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 0\u00a0\u00a0\u00a0\u00a0\u00a0 0 192.168.1.7:53072\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 207.46.140.70:https\u00a0\u00a0\u00a0\u00a0 ESTABLISHED 3247\/firefox\u00a0\u00a0 \u00a0<br\/>tcp\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 0\u00a0\u00a0\u00a0\u00a0\u00a0 0 192.168.1.7:34500\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 do-11.lastpass.co:https ESTABLISHED 3247\/firefox<\/pre>\n<p>See the last column for PID\/program name info.<\/p>\n<h2 id=\"q-how-to-make-netstat-print-network-statistics\">Q7. How to make netstat print network statistics?<\/h2>\n<p>This can be done using the -s command line option.<\/p>\n<p class=\"command\">netstat -s<\/p>\n<p>In this case, the tool produces information like total packets received, discarded, delivered, and much more. Following is an example output when the -s command line option was used.<\/p>\n<pre>Ip:<br\/>\u00a0\u00a0\u00a0 592215 total packets received<br\/>\u00a0\u00a0\u00a0 41 with invalid addresses<br\/>\u00a0\u00a0\u00a0 0 forwarded<br\/>\u00a0\u00a0\u00a0 0 incoming packets discarded<br\/>\u00a0\u00a0\u00a0 580699 incoming packets delivered<br\/>\u00a0\u00a0\u00a0 539118 requests sent out<br\/>\u00a0\u00a0\u00a0 627 outgoing packets dropped<br\/>\u00a0\u00a0\u00a0 482 dropped because of missing route<br\/>\u00a0\u00a0\u00a0 2 fragments failed<br\/>Icmp:<br\/>\u00a0\u00a0\u00a0 2337 ICMP messages received<br\/>\u00a0\u00a0\u00a0 6 input ICMP message failed.<br\/>\u00a0\u00a0\u00a0 ICMP input histogram:<br\/>\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 destination unreachable: 2337<br\/>\u00a0\u00a0\u00a0 3917 ICMP messages sent<br\/>\u00a0\u00a0\u00a0 0 ICMP messages failed<br\/>\u00a0\u00a0\u00a0 ICMP output histogram:<br\/>\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 destination unreachable: 3917<br\/>IcmpMsg:<br\/>\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 InType3: 2337<br\/>\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 OutType3: 3917<br\/>Tcp:<br\/>\u00a0\u00a0\u00a0 10943 active connections openings<br\/>\u00a0\u00a0\u00a0 127 passive connection openings<br\/>\u00a0\u00a0\u00a0 38 failed connection attempts<br\/>\u00a0\u00a0\u00a0 467 connection resets received<br\/>\u00a0\u00a0\u00a0 34 connections established<br\/>\u00a0\u00a0\u00a0 443643 segments received<br\/>\u00a0\u00a0\u00a0 414589 segments send out<br\/>\u00a0\u00a0\u00a0 6929 segments retransmited<br\/>\u00a0\u00a0\u00a0 428 bad segments received.<br\/>\u00a0\u00a0\u00a0 11713 resets sent<p>...<br\/>...<br\/>...<\/p><\/pre>\n<h2 id=\"q-how-to-make-netstat-display-kernel-routing-table\">Q8. How to make netstat display kernel routing table?<\/h2>\n<p>This can be done using the -r command line option.<\/p>\n<p class=\"command\">netstat -r<\/p>\n<p>Following is the output produced in my case:<\/p>\n<pre>Kernel IP routing table<br\/>Destination\u00a0\u00a0\u00a0\u00a0 Gateway\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 Genmask\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 Flags\u00a0\u00a0 MSS Window\u00a0 irtt Iface<br\/>default\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 192.168.1.1\u00a0\u00a0\u00a0\u00a0 0.0.0.0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 UG\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 0 0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 0 wlx18a6f713679b<br\/>link-local\u00a0\u00a0\u00a0\u00a0\u00a0 *\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 255.255.0.0\u00a0\u00a0\u00a0\u00a0 U\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 0 0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 0 wlx18a6f713679b<br\/>192.168.1.0\u00a0\u00a0\u00a0\u00a0 *\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 255.255.255.0\u00a0\u00a0 U\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 0 0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 0 wlx18a6f713679b<\/pre>\n<p>Note that <em>netstat -r<\/em> and <em>route -e<\/em> produce the same output.<\/p>\n<h2 id=\"conclusion\">Conclusion<\/h2>\n<p>So as you would have understood by now, the netstat command is a very important tool. It provides a lot of features &#8211; we&#8217;ve just scratched the surface here. Once you are done practicing what all we&#8217;ve discussed in this tutorial, head to the tool&#8217;s\u00a0<a href=\"https:\/\/linux.die.net\/man\/8\/netstat\" target=\"_blank\" rel=\"noopener noreferrer\">man page<\/a> for more info.<\/p>\n<div>\n<p><b>Share this page:<\/b><\/p>\n<p>\n<a href=\"https:\/\/www.facebook.com\/sharer.php?u=https%3A%2F%2Fwww.howtoforge.com%2Flinux-netstat-command%2F\" target=\"_blank\" rel=\"nofollow noopener noreferrer\"><img decoding=\"async\" src=\"https:\/\/afaghhosting.net\/blog\/wp-content\/uploads\/2018\/06\/linux-netstat-command-tutorial-for-beginners-8-examples.png\" height=\"20\" alt=\"\" title=\"\"><\/a><br \/>\n<a href=\"https:\/\/twitter.com\/intent\/tweet?url=https%3A%2F%2Fwww.howtoforge.com%2Flinux-netstat-command%2F&amp;text=Linux+netstat+Command+Tutorial+for+Beginners+%288+Examples%29&amp;via=howtoforgecom&amp;related=howtoforgecom\" target=\"_blank\" rel=\"nofollow noopener noreferrer\"><img decoding=\"async\" src=\"https:\/\/afaghhosting.net\/blog\/wp-content\/uploads\/2018\/06\/linux-netstat-command-tutorial-for-beginners-8-examples-1.png\" height=\"20\" alt=\"\" title=\"\"><\/a><br \/>\n<a href=\"https:\/\/twitter.com\/howtoforgecom\/\" target=\"_blank\" rel=\"nofollow noopener noreferrer\"><img decoding=\"async\" src=\"https:\/\/afaghhosting.net\/blog\/wp-content\/uploads\/2018\/06\/linux-netstat-command-tutorial-for-beginners-8-examples-2.png\" height=\"20\" alt=\"\" title=\"\"><\/a><br \/>\n<a href=\"https:\/\/plus.google.com\/share?url=https%3A%2F%2Fwww.howtoforge.com%2Flinux-netstat-command%2F\" target=\"_blank\" rel=\"nofollow noopener noreferrer\"><img decoding=\"async\" src=\"https:\/\/afaghhosting.net\/blog\/wp-content\/uploads\/2018\/06\/linux-netstat-command-tutorial-for-beginners-8-examples-3.png\" height=\"20\" alt=\"\" title=\"\"><\/a>\n<\/p>\n<\/div>\n","protected":false},"excerpt":{"rendered":"<p>If you are new to Linux command line, and are interested in learning networking stuff, there are many command line utilities that you should be aware of. One such tool is netstat. In this article, we will discuss this command using some easy to understand examples. But before we do that, it&#8217;s worth mentioning that &hellip;<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[36],"tags":[],"class_list":["post-5056","post","type-post","status-publish","format-standard","hentry","category-36"],"_links":{"self":[{"href":"https:\/\/afaghhosting.net\/blog\/wp-json\/wp\/v2\/posts\/5056","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/afaghhosting.net\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/afaghhosting.net\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/afaghhosting.net\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/afaghhosting.net\/blog\/wp-json\/wp\/v2\/comments?post=5056"}],"version-history":[{"count":0,"href":"https:\/\/afaghhosting.net\/blog\/wp-json\/wp\/v2\/posts\/5056\/revisions"}],"wp:attachment":[{"href":"https:\/\/afaghhosting.net\/blog\/wp-json\/wp\/v2\/media?parent=5056"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/afaghhosting.net\/blog\/wp-json\/wp\/v2\/categories?post=5056"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/afaghhosting.net\/blog\/wp-json\/wp\/v2\/tags?post=5056"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}