Linux Advanced Routing and Traffic Control list
 help / color / mirror / Atom feed
From: Juri Haberland <haberland@altus.de>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] ip_alias??
Date: Wed, 13 Jun 2001 08:20:41 +0000	[thread overview]
Message-ID: <marc-lartc-99242048717867@msgid-missing> (raw)
In-Reply-To: <marc-lartc-99241178429581@msgid-missing>

Jasper Spaans wrote:
> 
> On Tue, Jun 12, 2001 at 10:57:36PM -0700, streeterk wrote:
> 
> > What happened to ip_alias.  I found some reference to it being replaced in
> > 2.4 Kernels, but replaced with what?  Anyone know of some good
> > documentation on this subject??
> 
> It has disappeared, however, its functionality hasn't (at least, partially).

[--snip--]

> (Well, some pitfalls do exist, you cannot firewall on these interfaces
> anymore, however, you'll have to rewrite your rules anyway because of the
> transition to iptables, so that shouldn't be a problem)

Guys, excuse my ignorance, but can you point me to the original source
of that information? It's the very first time I heard of this and
actually I am still able to use something like 'ifconfig eth0:0 x.x.x.x
up'. And AFAIK it was never possible to use alias interfaces in
firewalling.

Maybe I missed some important information for years? (not impossible IMO
;-)

Juri

_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://ds9a.nl/2.4Routing/

  parent reply	other threads:[~2001-06-13  8:20 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-06-13  5:57 [LARTC] ip_alias?? streeterk
2001-06-13  7:29 ` Jasper Spaans
2001-06-13  8:20 ` Juri Haberland [this message]
2001-06-13  8:24 ` Daniel Bergqvist
2001-06-13  8:28 ` Daniel Bergqvist
2001-06-13  8:56 ` Juri Haberland
2001-06-13 12:45 ` David Talbot
2001-06-13 16:58 ` Juri Haberland
2001-06-13 21:13 ` Arthur van Leeuwen

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=marc-lartc-99242048717867@msgid-missing \
    --to=haberland@altus.de \
    --cc=lartc@vger.kernel.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