From: Antony Stone <Antony@Soft-Solutions.co.uk>
To: netfilter@lists.netfilter.org
Subject: Re: Help with alias interfaces
Date: Wed, 23 Jun 2004 21:47:29 +0100 [thread overview]
Message-ID: <200406232147.29298.Antony@Soft-Solutions.co.uk> (raw)
In-Reply-To: <16601.59510.845588.723249@saint.heaven.net>
On Wednesday 23 June 2004 9:30 pm, Dick St.Peters wrote:
> Antony Stone writes:
> > >
> > > > The deprecated way to get multiple IPs results in pseudo-interface
> > > > names such as eth1:0, eth1:1 etc as you discussed.
> > >
> > > Deprecated by whom?
> >
> > http://mirrors.bieringer.de/Linux+IPv6-HOWTO/conf-ipv6-in-ipv4-point-to-p
> >oint-tunnels.html (Section headings 9.3.1.1 & 9.3.1.2)
> > http://seclists.org/lists/honeypots/2004/Jan-Mar/0209.html
> > http://www.uwsg.iu.edu/hypermail/linux/kernel/0108.2/0485.html
>
> These are deprecating the use of "ifconfig", not the use of
> pseudo-interface names.
That is precisely what I was saying is deprecated - the use of ifconfig.
One of the results of using it is that you automatically and non-optionally
get the pseudo-interface names (which are optional if you use ip addr).
Sorry if my wording was unclear - I didn't mean to suggest that multiple names
for interfaces are inherently a bad idea or deprecated.
> However, most people aren't dealing with ipv6-in-ipv4 tunnels,
> honeypots, or thousands of IPs per interface, as are the references
> you cite. "ifconfig" will handle the vast majority of cases and is
> simpler to use when the power of "ip" is not needed.
I simply looked up references to support my assertion that "ifconfig eth0:0"
etc is deprecated. The particular reasons why these people are using
multiple IPs on one interface are irrelevant.
I agree with you that ifconfig will handle the majority of cases.
I don't agree that it's simpler to use, but I think that's just a matter of
opinion.
However, as I said in my earlier posting, it doesn't matter to netfilter which
method you use to get the multiple IPs, so by all means choose whichever you
prefer. I don't regard it as a big deal - I was simply surprised that you
hadn't come across this use of ifconfig as being deprecated, so I gave some
examples.
Regards,
Antony.
--
This email was created using 100% recycled electrons.
Please reply to the list;
please don't CC me.
prev parent reply other threads:[~2004-06-23 20:47 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-21 9:14 DNAT problem / question (nfcan: addressed to exclusive sender for this address) Arnauts, Bert
2004-06-21 16:45 ` Help with alias interfaces Erick Sanz
2004-06-21 17:11 ` Paweł Staszewski
2004-06-21 18:22 ` mlody
2004-06-21 18:44 ` Paweł Staszewski
2004-06-21 19:15 ` mlody
2004-06-23 15:31 ` Erick Sanz
2004-06-23 14:53 ` Antony Stone
2004-06-23 19:01 ` Dick St.Peters
2004-06-23 19:22 ` Antony Stone
2004-06-23 20:30 ` Dick St.Peters
2004-06-23 20:47 ` Antony Stone [this message]
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=200406232147.29298.Antony@Soft-Solutions.co.uk \
--to=antony@soft-solutions.co.uk \
--cc=netfilter@lists.netfilter.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