<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	
	>
<channel>
	<title>
	Comments on: Deprecated Linux Networking Commands and Their Replacements	</title>
	<atom:link href="https://www.tecmint.com/deprecated-linux-networking-commands-and-their-replacements/feed/" rel="self" type="application/rss+xml" />
	<link>https://www.tecmint.com/deprecated-linux-networking-commands-and-their-replacements/</link>
	<description>Tecmint - Linux Howtos, Tutorials, Guides, News, Tips and Tricks.</description>
	<lastBuildDate>Thu, 13 Jul 2023 19:08:18 +0000</lastBuildDate>
	<sy:updatePeriod>
	hourly	</sy:updatePeriod>
	<sy:updateFrequency>
	1	</sy:updateFrequency>
	
	<item>
		<title>
		By: Aaron Kili		</title>
		<link>https://www.tecmint.com/deprecated-linux-networking-commands-and-their-replacements/comment-page-1/#comment-1366298</link>

		<dc:creator><![CDATA[Aaron Kili]]></dc:creator>
		<pubDate>Tue, 22 Sep 2020 05:06:50 +0000</pubDate>
		<guid isPermaLink="false">https://www.tecmint.com/?p=30076#comment-1366298</guid>

					<description><![CDATA[In reply to &lt;a href=&quot;https://www.tecmint.com/deprecated-linux-networking-commands-and-their-replacements/comment-page-1/#comment-1365225&quot;&gt;Jeremy H.&lt;/a&gt;.

@Jeremy

Many thanks for the useful feedback.]]></description>
			<content:encoded><![CDATA[<p>In reply to <a target="_blank" href="https://www.tecmint.com/deprecated-linux-networking-commands-and-their-replacements/comment-page-1/#comment-1365225">Jeremy H.</a>.</p>
<p>@Jeremy</p>
<p>Many thanks for the useful feedback.</p>
]]></content:encoded>
		
			</item>
		<item>
		<title>
		By: Jeremy H.		</title>
		<link>https://www.tecmint.com/deprecated-linux-networking-commands-and-their-replacements/comment-page-1/#comment-1365225</link>

		<dc:creator><![CDATA[Jeremy H.]]></dc:creator>
		<pubDate>Fri, 18 Sep 2020 19:01:52 +0000</pubDate>
		<guid isPermaLink="false">https://www.tecmint.com/?p=30076#comment-1365225</guid>

					<description><![CDATA[In reply to &lt;a href=&quot;https://www.tecmint.com/deprecated-linux-networking-commands-and-their-replacements/comment-page-1/#comment-1016952&quot;&gt;Aaron Kili&lt;/a&gt;.

Yay, necro.  
  
Not maintained means &quot;not maintained&quot; and nothing more, it is a probably net state of something that has worked fine for years, or decades, and doesn&#039;t have any known bugs. That doesn&#039;t make it automatically insecure or dangerous as the article author suggests, merely an unknown and potential risk at worst.  
  
Honestly, I&#039;m not sure why unmaintained software should necessarily lead to a whole new suite and renaming/removing a bunch of standard commands forcing everybody under the sun to relearn things they already know. They could have chosen to become the maintainers of net-tools and updated them OR they could at least have retained the syntax and a rough similarity in the naming.]]></description>
			<content:encoded><![CDATA[<p>In reply to <a target="_blank" href="https://www.tecmint.com/deprecated-linux-networking-commands-and-their-replacements/comment-page-1/#comment-1016952">Aaron Kili</a>.</p>
<p>Yay, necro.  </p>
<p>Not maintained means &#8220;not maintained&#8221; and nothing more, it is a probably net state of something that has worked fine for years, or decades, and doesn&#8217;t have any known bugs. That doesn&#8217;t make it automatically insecure or dangerous as the article author suggests, merely an unknown and potential risk at worst.  </p>
<p>Honestly, I&#8217;m not sure why unmaintained software should necessarily lead to a whole new suite and renaming/removing a bunch of standard commands forcing everybody under the sun to relearn things they already know. They could have chosen to become the maintainers of net-tools and updated them OR they could at least have retained the syntax and a rough similarity in the naming.</p>
]]></content:encoded>
		
			</item>
		<item>
		<title>
		By: Aaron Kili		</title>
		<link>https://www.tecmint.com/deprecated-linux-networking-commands-and-their-replacements/comment-page-1/#comment-1018466</link>

		<dc:creator><![CDATA[Aaron Kili]]></dc:creator>
		<pubDate>Wed, 25 Jul 2018 15:16:20 +0000</pubDate>
		<guid isPermaLink="false">https://www.tecmint.com/?p=30076#comment-1018466</guid>

					<description><![CDATA[In reply to &lt;a href=&quot;https://www.tecmint.com/deprecated-linux-networking-commands-and-their-replacements/comment-page-1/#comment-1017711&quot;&gt;Dave S.&lt;/a&gt;.

@Daves

You have shared the same sentiment as the other readers below, but from an experienced and well explained view. Many thanks for the feedback.]]></description>
			<content:encoded><![CDATA[<p>In reply to <a target="_blank" href="https://www.tecmint.com/deprecated-linux-networking-commands-and-their-replacements/comment-page-1/#comment-1017711">Dave S.</a>.</p>
<p>@Daves</p>
<p>You have shared the same sentiment as the other readers below, but from an experienced and well explained view. Many thanks for the feedback.</p>
]]></content:encoded>
		
			</item>
		<item>
		<title>
		By: Dave S.		</title>
		<link>https://www.tecmint.com/deprecated-linux-networking-commands-and-their-replacements/comment-page-1/#comment-1017711</link>

		<dc:creator><![CDATA[Dave S.]]></dc:creator>
		<pubDate>Sat, 21 Jul 2018 15:08:34 +0000</pubDate>
		<guid isPermaLink="false">https://www.tecmint.com/?p=30076#comment-1017711</guid>

					<description><![CDATA[They are not obsolete - they are standard UNIX commands and are present in every BSD and UNIX distribution all the way back to the implementation of ARCNET and Ethernet in the early 1980&#039;s. These new &quot;&lt;strong&gt;ip&lt;/strong&gt;&quot; commands are just another package to do what we already do. Eliminating &lt;strong&gt;netstat&lt;/strong&gt;, &lt;strong&gt;route&lt;/strong&gt;, &lt;strong&gt;ifconfig&lt;/strong&gt;, &lt;strong&gt;arp&lt;/strong&gt;, and others to replace them with a new package is ludicrous. If the &lt;strong&gt;net-tools&lt;/strong&gt; package on Linux is not maintained, then the clue phone is ringing and someone needs to wake up and pull it into the network core distribution.

I was at a UNIX developers conference in 1995. Most of the folks there were BSD UNIX folks, but there were a few early Linux folks there too. One of the guys was giving an overview of Linux when he showed the &quot;&lt;strong&gt;routes&lt;/strong&gt;&quot; command, which essentially did that &quot;&lt;strong&gt;netstat -rn&lt;/strong&gt;&quot; does. 

When one of the folks at the conference asked why he did not use &lt;strong&gt;netstat&lt;/strong&gt; to do that, the Linux guy asked what &lt;strong&gt;netstat&lt;/strong&gt; was. The whole room broke up laughing. Needless to say, it did not help Linux&#039;s reputation on that day. 

Five years later, the &quot;&lt;strong&gt;routes&lt;/strong&gt;&quot; command was gone from Linux and &lt;strong&gt;netstat&lt;/strong&gt; was everywhere. I predict that this &quot;&lt;strong&gt;ip&lt;/strong&gt;&quot; command they are pushing is going to meet the same ugly fate that the &quot;&lt;strong&gt;routes&lt;/strong&gt;&quot; command met in the late 90&#039;s. Change for change sake serves no practical purpose.

The issue is that you do not have a maintainer for net-tools. What makes you think you will have a maintainer for these new ip tools down the road? The problem is with maintaining a set of tools. Solve that, and you fix the problem. Why &lt;strong&gt;netstat&lt;/strong&gt;, &lt;strong&gt;route&lt;/strong&gt;, &lt;strong&gt;ifconfig&lt;/strong&gt;, &lt;strong&gt;arp&lt;/strong&gt;, &lt;strong&gt;ping&lt;/strong&gt;, &lt;strong&gt;traceroute&lt;/strong&gt;, and others are not currently a standard part of the Linux network kernel is baffling.]]></description>
			<content:encoded><![CDATA[<p>They are not obsolete &#8211; they are standard UNIX commands and are present in every BSD and UNIX distribution all the way back to the implementation of ARCNET and Ethernet in the early 1980&#8217;s. These new &#8220;<strong>ip</strong>&#8221; commands are just another package to do what we already do. Eliminating <strong>netstat</strong>, <strong>route</strong>, <strong>ifconfig</strong>, <strong>arp</strong>, and others to replace them with a new package is ludicrous. If the <strong>net-tools</strong> package on Linux is not maintained, then the clue phone is ringing and someone needs to wake up and pull it into the network core distribution.</p>
<p>I was at a UNIX developers conference in 1995. Most of the folks there were BSD UNIX folks, but there were a few early Linux folks there too. One of the guys was giving an overview of Linux when he showed the &#8220;<strong>routes</strong>&#8221; command, which essentially did that &#8220;<strong>netstat -rn</strong>&#8221; does. </p>
<p>When one of the folks at the conference asked why he did not use <strong>netstat</strong> to do that, the Linux guy asked what <strong>netstat</strong> was. The whole room broke up laughing. Needless to say, it did not help Linux&#8217;s reputation on that day. </p>
<p>Five years later, the &#8220;<strong>routes</strong>&#8221; command was gone from Linux and <strong>netstat</strong> was everywhere. I predict that this &#8220;<strong>ip</strong>&#8221; command they are pushing is going to meet the same ugly fate that the &#8220;<strong>routes</strong>&#8221; command met in the late 90&#8217;s. Change for change sake serves no practical purpose.</p>
<p>The issue is that you do not have a maintainer for net-tools. What makes you think you will have a maintainer for these new ip tools down the road? The problem is with maintaining a set of tools. Solve that, and you fix the problem. Why <strong>netstat</strong>, <strong>route</strong>, <strong>ifconfig</strong>, <strong>arp</strong>, <strong>ping</strong>, <strong>traceroute</strong>, and others are not currently a standard part of the Linux network kernel is baffling.</p>
]]></content:encoded>
		
			</item>
		<item>
		<title>
		By: Aaron Kili		</title>
		<link>https://www.tecmint.com/deprecated-linux-networking-commands-and-their-replacements/comment-page-1/#comment-1016952</link>

		<dc:creator><![CDATA[Aaron Kili]]></dc:creator>
		<pubDate>Wed, 18 Jul 2018 11:15:14 +0000</pubDate>
		<guid isPermaLink="false">https://www.tecmint.com/?p=30076#comment-1016952</guid>

					<description><![CDATA[In reply to &lt;a href=&quot;https://www.tecmint.com/deprecated-linux-networking-commands-and-their-replacements/comment-page-1/#comment-1016453&quot;&gt;C. R. Zamana&lt;/a&gt;.

@Zamana

These tools are just considered obsolete, because the net-tools package has not been maintained for a so many years.]]></description>
			<content:encoded><![CDATA[<p>In reply to <a target="_blank" href="https://www.tecmint.com/deprecated-linux-networking-commands-and-their-replacements/comment-page-1/#comment-1016453">C. R. Zamana</a>.</p>
<p>@Zamana</p>
<p>These tools are just considered obsolete, because the net-tools package has not been maintained for a so many years.</p>
]]></content:encoded>
		
			</item>
	</channel>
</rss>
