From: Thomas Graf <tgraf@suug.ch>
To: Matt Domsch <Matt_Domsch@dell.com>
Cc: David Miller <davem@davemloft.net>,
kaber@trash.net, jengelh@medozas.de, dwmw2@infradead.org,
jchapman@katalix.com, jonathan@jonmasters.org,
rick.jones2@hp.com, auke-jan.h.kok@intel.com,
johnathan@jonmasters.org, netdev@vger.kernel.org
Subject: Re: network interface *name* alias support?
Date: Wed, 28 May 2008 00:11:58 +0200 [thread overview]
Message-ID: <20080527221158.GC20815@postel.suug.ch> (raw)
In-Reply-To: <20080527190352.GE25696@auslistsprd01.us.dell.com>
* Matt Domsch <Matt_Domsch@dell.com> 2008-05-27 14:03
> Network devices have no such thing that I can tell. I get at the
> device names (as presently assigned) by reading /proc/net/dev (I'd be
> happy to be told of a more correct way - this is what net-tools uses.)
> The moment I've finished reading this though, another process can come
> along and change these devices names. Now every ioctl() my code makes
> could fail because the name (in struct ifreq) is the handle used for
> such calls. One could argue it's a rare thing to change device
> names...
Regardless of whether you identify the link by name or slot, you
should translate the name/slot to ifindex and use netlink requests
to manipulate links. The ifindex is not going to change and won't
be reused by new links until the (large) counter overflows. Therefore
the chance of modyfing a wrong link is close to zero.
next prev parent reply other threads:[~2008-05-27 22:11 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
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 [this message]
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=20080527221158.GC20815@postel.suug.ch \
--to=tgraf@suug.ch \
--cc=Matt_Domsch@dell.com \
--cc=auke-jan.h.kok@intel.com \
--cc=davem@davemloft.net \
--cc=dwmw2@infradead.org \
--cc=jchapman@katalix.com \
--cc=jengelh@medozas.de \
--cc=johnathan@jonmasters.org \
--cc=jonathan@jonmasters.org \
--cc=kaber@trash.net \
--cc=netdev@vger.kernel.org \
--cc=rick.jones2@hp.com \
/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).