net-tools must die

[Xose Vazquez Perez]

hi,

net-tools ( http://net-tools.berlios.de/ ) is deprecated since time ago.
iproute is the way to go.

 net-tools future http://lists.debian.org/debian-devel/2009/03/thrd2.html#00780
 ================

-------- Original Message --------
Subject: net-tools future
Date: Sun, 15 Mar 2009 17:30:18
From: Martín Ferrari <tincho(a)debian.org&gt;
To: debian-devel@(a)lists.debian.org

Hi,

Luk Claes and me, as the current maintainers of net-tools, we've been
thinking about it's future. Net-tools has been a core part of Debian and
any other linux based distro for many years, but it's showing its age.

It doesnt support many of the modern features of the linux kernel, the
interface is far from optimal and difficult to use in automatisation,
and also, it hasn't got much love in the last years.

On the other side, the iproute suite, introduced around the 2.2 kernel
line, has both a much better and consistent interface, is more powerful,
and is almost ten years old, so nobody would say it's untested.

Hence, our plans are to replace net-tools completely with iproute, maybe
leading the route for other distributions to follow. Of course, most
people and tools use and remember the venerable old interface, so the
first step would be to write wrappers, trying to be compatible with
net-tools.

At the same time, we believe that most packages using net-tools should
be patched to use iproute instead, while others can continue using the
wrappers for some time. The ifupdown package is obviously the first
candidate, but it seems that a version using iproute has been available
in experimental since 2007.

So, the roadmap would be:
- Send patches to net-tools using packages to use iproute instead
- Development of the wrapper scripts
- Uploading to experimental a net-tools-compat package, to allow wider
testing.
- Upload to unstable

About the wrapper scripts:
 * ipconfig, route: the most difficult ones, both can be replaced by
calls to "ip", maybe except for some obscure options.
 * netstat : sstat provides almost the same information, just some
formatting changes and parsing the command line
 * rarp should be dropped, as the linux kernel doesn't support it
anymore, since the 2.3 series. The replacement, arpd, is already
included in iproute.
 * ipmaddr works exactly as "ip maddr", in fact, the code is from the
iproute sources. Same for iptunnel and "ip tunnel". In both cases,
they're just replaced by a symlinkm, as the ip command recognises that.
 * nameif: can be replaced by "ip link", not sure if it's worth the
effort (does anybody actually use it?)

Problematic tools:
 * mii-tool: it could be dropped and replaced by a pointer to ethtool as
it's not meant to be used automatically by scripts. On the other hand,
it's distributed as a stand-alone tool [0] and we could do the same.
 * plipsetup, slattach: we don't know of any replacement for those, but
could be distributed separately too. Also, it's dubious if anyone still
uses them.

0: http://freshmeat.net/projects/mii-tool/

-- 
Martí­n Ferrari <tincho(a)debian.org&gt;

--
To UNSUBSCRIBE, email to debian-devel-REQUEST(a)lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster(a)lists.debian.org
---end---


It's still required by:

bontmia
bwm-ng
dracut
egd
firehol
globus-common
initscripts
libguestfs
netdump-server
nmbscan
ocfs2-tools
ocsinventory-agent
olpc-netutils
openvpn
openwsman
rkhunter
smokeping
wicd
wifi-radar
wlassistant

https://bugzilla.redhat.com/show_bug.cgi?id=687920

-- 
«Allá muevan feroz guerra, ciegos reyes por un palmo más de tierra;
que yo aquí tengo por mío cuanto abarca el mar bravío, a quien nadie
impuso leyes. Y no hay playa, sea cualquiera, ni bandera de esplendor,
que no sienta mi derecho y dé pecho a mi valor.»

[Ben Boeckel]

Xose Vazquez Perez <xose.vazquez(a)gmail.com&gt; wrote:
>  At the same time, we believe that most packages using net-tools
> should
>  be patched to use iproute instead, while others can continue using the
>  wrappers for some time. The ifupdown package is obviously the first
>  candidate, but it seems that a version using iproute has been available
>  in experimental since 2007. 
Maybe this is the wrong place, but is iproute going to honor
USERCTL="yes" in the ifcfg scripts? It seems it currently doesn't
whereas ifup/ifdown do:

% grep USERCTL /etc/sysconfig/network-scripts/ifcfg-em2
USERCTL="yes"
% ip link set em2 down
RTNETLINK answers: Operation not permitted

--Ben

[Chuck Anderson]

On Fri, Apr 01, 2011 at 09:33:52PM +0000, Ben Boeckel wrote:
>  Xose Vazquez Perez <xose.vazquez(a)gmail.com&gt; wrote:
>  > At the same time, we believe that most packages using net-tools should
>  > be patched to use iproute instead, while others can continue using the
>  > wrappers for some time. The ifupdown package is obviously the first
>  > candidate, but it seems that a version using iproute has been available
>  > in experimental since 2007.
>  
>  Maybe this is the wrong place, but is iproute going to honor
>  USERCTL="yes" in the ifcfg scripts? It seems it currently doesn't
>  whereas ifup/ifdown do:
>  
>  % grep USERCTL /etc/sysconfig/network-scripts/ifcfg-em2
>  USERCTL="yes"
>  % ip link set em2 down
>  RTNETLINK answers: Operation not permitted 
iproute has no way to honor such things.  It is a low level tool that 
doesn't read configuration files, do privilege escalation to be able 
to perform system level tasks as a normal user, etc.  iproute compares 
to ifconfig and route, not ifup/ifdown.