netdev - Re: network interface *name* alias support?

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-Id: <20080525.051713.124717485.davem@davemloft.net>
Date:	Sun, 25 May 2008 05:17:13 -0700 (PDT)
From:	David Miller <davem@...emloft.net>
To:	kaber@...sh.net
Cc:	jengelh@...ozas.de, dwmw2@...radead.org, jchapman@...alix.com,
	Matt_Domsch@...l.com, jonathan@...masters.org, tgraf@...g.ch,
	rick.jones2@...com, auke-jan.h.kok@...el.com,
	johnathan@...masters.org, netdev@...r.kernel.org
Subject: Re: network interface *name* alias support?

From: Patrick McHardy <kaber@...sh.net>
Date: Sun, 25 May 2008 05:07:16 +0200

> Jan Engelhardt wrote:
> > On Saturday 2008-05-24 22:31, Patrick McHardy wrote:
> >> David Woodhouse wrote:
> >>> On Sat, 2008-05-24 at 10:15 +0100, James Chapman wrote:
> >>>> Wouldn't it be better to fix any applications that can't handle
> >>>> renamed devices?
> >>> _Are_ there any such applications? Other than NetworkManager crapping
> >>> itself when the device name is too long, I'm not aware of any.
> >> iptraf uses device names to determine the device type:
> > 
> > Run `iptraf -u`, and it works with any name.
> 
> Thanks for the hint. Its stupid nevertheless.

I think it's stupid too.

Physical geography information for a device is available
to userspace already.  If tools want to present that to
the user in a suitable interface, fine.  But what is
being proposed here is not necessary to implement that.
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html