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]

Date:	Sat, 24 May 2008 22:31:20 +0200
From:	Patrick McHardy <kaber@...sh.net>
To:	David Woodhouse <dwmw2@...radead.org>
CC:	James Chapman <jchapman@...alix.com>,
	Matt Domsch <Matt_Domsch@...l.com>,
	Jan Engelhardt <jengelh@...ozas.de>,
	Jon Masters <jonathan@...masters.org>,
	Thomas Graf <tgraf@...g.ch>, Rick Jones <rick.jones2@...com>,
	"Kok, Auke" <auke-jan.h.kok@...el.com>, johnathan@...masters.org,
	netdev@...r.kernel.org
Subject: Re: network interface *name* alias support?

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:

char ifaces[][6] =
     { "lo", "eth", "sl", "ppp", "ippp", "plip", "fddi", "isdn", "dvb",
     "pvc", "hdlc", "ipsec", "sbni", "tr", "wvlan", "wlan", "sm2", "sm3",
     "pent", "lec", "brg", "tun", "tap", "cipcb", "tunl", "vlan", "ath",
     "ra"
};

and

         if (strncmp(ifname, "eth", 3) == 0)
             result = LINK_ETHERNET;
         else if (strncmp(ifname, "ath", 3) == 0)
             result = LINK_ETHERNET;
         else if (strncmp(ifname, "plip", 4) == 0)
             result = LINK_PLIP;
...
--
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