From: Antony Stone <Antony@Soft-Solutions.co.uk>
To: netfilter@lists.netfilter.org
Subject: Re: Help with alias interfaces
Date: Wed, 23 Jun 2004 20:22:46 +0100 [thread overview]
Message-ID: <200406232022.46362.Antony@Soft-Solutions.co.uk> (raw)
In-Reply-To: <16601.54137.766533.681609@saint.heaven.net>
On Wednesday 23 June 2004 8:01 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-point-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
> I use secondary IPs a lot, and I've never before
> heard anyone call the standard way of doing them "deprecated". Plus
> I, for one, prefer having pseduo-interface labels for manipulating
> them. Labels are handy, especially if you use names instead of
> numbers. (eth0:bob is as valid as eth0:1.)
That's what the "ip link set <device> name <name>" is for now :)
> > The recommended way to assign
> > multiple IPs on one interface (ip addr add a.b.c.d dev eth1) simply
> > results in multiple IPs on the interface - no strange new names appear,
> > therefore I think it is a much more obvious and clear way of doing it.
>
> This is probably a case where context and background determine what is
> more "obvious" and "clear".
Agreed.
Antony.
--
Ramdisk is not an installation procedure.
Please reply to the list;
please don't CC me.
next prev parent reply other threads:[~2004-06-23 19:22 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 [this message]
2004-06-23 20:30 ` Dick St.Peters
2004-06-23 20:47 ` Antony Stone
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=200406232022.46362.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