netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Patrick McHardy <kaber@trash.net>
To: David Woodhouse <dwmw2@infradead.org>
Cc: James Chapman <jchapman@katalix.com>,
	Matt Domsch <Matt_Domsch@dell.com>,
	Jan Engelhardt <jengelh@medozas.de>,
	Jon Masters <jonathan@jonmasters.org>,
	Thomas Graf <tgraf@suug.ch>, Rick Jones <rick.jones2@hp.com>,
	"Kok, Auke" <auke-jan.h.kok@intel.com>,
	johnathan@jonmasters.org, netdev@vger.kernel.org
Subject: Re: network interface *name* alias support?
Date: Sat, 24 May 2008 22:31:20 +0200	[thread overview]
Message-ID: <48387B18.2090300@trash.net> (raw)
In-Reply-To: <1211621632.31212.73.camel@shinybook.infradead.org>

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;
...

  parent reply	other threads:[~2008-05-24 20:31 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-05-23 16:31 network interface *name* alias support? Jan Engelhardt
2008-05-23 17:14 ` Kok, Auke
2008-05-23 17:44   ` Rick Jones
2008-05-23 19:06     ` Jon Masters
2008-05-23 19:11       ` Jon Masters
2008-05-23 20:46       ` Jan Engelhardt
2008-05-23 20:55         ` Jon Masters
2008-05-23 22:54       ` Thomas Graf
2008-05-24  4:25         ` Jon Masters
2008-05-24  4:53           ` Jan Engelhardt
2008-05-24  5:16             ` Matt Domsch
2008-05-24  9:15               ` James Chapman
2008-05-24  9:33                 ` David Woodhouse
2008-05-24 10:37                   ` James Chapman
2008-05-24 20:31                   ` Patrick McHardy [this message]
2008-05-24 20:54                     ` Jan Engelhardt
2008-05-25  3:07                       ` Patrick McHardy
2008-05-25 12:17                         ` David Miller
2008-05-27 19:03                           ` Matt Domsch
2008-05-27 21:49                             ` Jan Engelhardt
2008-05-27 22:11                             ` Thomas Graf
2008-05-24 18:12           ` Stephen Hemminger
  -- strict thread matches above, loose matches on Subject: below --
2008-05-21 22:47 Jon Masters
2008-05-23 13:07 ` David Woodhouse
2008-05-23 14:50   ` Jon Masters

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=48387B18.2090300@trash.net \
    --to=kaber@trash.net \
    --cc=Matt_Domsch@dell.com \
    --cc=auke-jan.h.kok@intel.com \
    --cc=dwmw2@infradead.org \
    --cc=jchapman@katalix.com \
    --cc=jengelh@medozas.de \
    --cc=johnathan@jonmasters.org \
    --cc=jonathan@jonmasters.org \
    --cc=netdev@vger.kernel.org \
    --cc=rick.jones2@hp.com \
    --cc=tgraf@suug.ch \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).