From: Patrick McHardy <kaber@trash.net>
To: Narendra_K@Dell.com
Cc: shemminger@linux-foundation.org, jengelh@medozas.de,
be-mail2009@lina.inka.de, net-tools@lina.inka.de,
netfilter-devel@vger.kernel.org, jgarzik@users.sourceforge.net,
Charles_Rose@Dell.com, Matt_Domsch@Dell.com, Shyam_Iyer@Dell.com,
Jordan_Hargrave@Dell.com, Sandeep_K_Shandilya@Dell.com
Subject: Re: [PROPOSAL]: Alias names for network interfaces
Date: Thu, 14 Jan 2010 09:41:48 +0100 [thread overview]
Message-ID: <4B4ED8CC.5000207@trash.net> (raw)
In-Reply-To: <EDA0A4495861324DA2618B4C45DCB3EE5899C5@blrx3m08.blr.amer.dell.com>
Narendra_K@Dell.com wrote:
> Patrick,
>
> If I understand your point correctly, you are saying that if a rule is
> specified in the command line as below
>
> iptables -A INPUT -i Embedded_NIC_1 -j ACCEPT, then if the rule is saved
> by iptables-save the rule would look like
>
> iptables -A INPUT -i ethN -j ACCEPT and there is no way to know what the
> corresponding Embedded_NIC_1 name is.
>
> If this is correct, then I agree. I suppose that this concern can be
> addressed in one of these ways, if I am not missing
> something -
>
> a) The command line tool I mentioned above (point 2)would tell us the
> ethN -> Embedded_NIC_N mapping
> b) Or the iptables-save needs to be enhanced to save Embedded_NIC_N
> format instead of ethN by making a call to
> libnetdevname to get that mapping ( ethN -> Embedded_NIC_1).
Yeah, that could be done (but optionally please). What you can't
do however is display these two rules
iptables ... -i eth0 ...
iptables ... -i Embedded_NIC_N ...
the same way they were entered since you either map back or you don't.
I guess we can live with that though ...
next prev parent reply other threads:[~2010-01-14 8:41 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <EDA0A4495861324DA2618B4C45DCB3EE5899AC@blrx3m08.blr.amer.dell.com>
2010-01-12 19:49 ` Re:[PROPOSAL]: Alias names for network interfaces Narendra K
2010-01-13 0:11 ` Jan Engelhardt
2010-01-13 6:47 ` [PROPOSAL]: " Narendra_K
2010-01-13 11:04 ` Bernd Eckenfels
2010-01-13 17:22 ` John Haxby
2010-01-13 17:46 ` Domsch, Matt
2010-01-13 18:11 ` Bernd Eckenfels
2010-01-13 18:21 ` Jan Engelhardt
2010-01-14 8:44 ` Patrick McHardy
2010-01-14 9:35 ` Jan Engelhardt
2010-01-15 19:14 ` Narendra_K
2010-01-18 17:07 ` Marco Innocenti
2010-01-19 17:32 ` Narendra_K
2010-01-19 22:31 ` Stephen Hemminger
2010-01-20 1:02 ` Bernd Eckenfels
2010-01-20 16:42 ` Narendra_K
2010-01-13 17:54 ` Stephen Hemminger
2010-01-13 13:24 ` Patrick McHardy
2010-01-13 13:43 ` Jan Engelhardt
2010-01-13 16:27 ` Stephen Hemminger
2010-01-13 17:00 ` Narendra_K
2010-01-14 8:41 ` Patrick McHardy [this message]
2009-12-17 13:54 Narendra_K
2009-12-17 14:48 ` Jan Engelhardt
2009-12-18 2:02 ` Bernd Eckenfels
2009-12-18 13:19 ` Narendra_K
2009-12-18 13:42 ` Jan Engelhardt
2009-12-18 14:02 ` Domsch, Matt
2009-12-18 14:08 ` Domsch, Matt
2009-12-18 14:15 ` Jan Engelhardt
2009-12-20 0:12 ` Jordan_Hargrave
2009-12-18 17:38 ` Stephen Hemminger
2009-12-21 17:28 ` Narendra_K
2009-12-21 17:36 ` Stephen Hemminger
2009-12-23 17:11 ` Narendra_K
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=4B4ED8CC.5000207@trash.net \
--to=kaber@trash.net \
--cc=Charles_Rose@Dell.com \
--cc=Jordan_Hargrave@Dell.com \
--cc=Matt_Domsch@Dell.com \
--cc=Narendra_K@Dell.com \
--cc=Sandeep_K_Shandilya@Dell.com \
--cc=Shyam_Iyer@Dell.com \
--cc=be-mail2009@lina.inka.de \
--cc=jengelh@medozas.de \
--cc=jgarzik@users.sourceforge.net \
--cc=net-tools@lina.inka.de \
--cc=netfilter-devel@vger.kernel.org \
--cc=shemminger@linux-foundation.org \
/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).