Linux Advanced Routing and Traffic Control list
 help / color / mirror / Atom feed
From: Arthur van Leeuwen <arthurvl@sci.kun.nl>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] ip_alias??
Date: Wed, 13 Jun 2001 21:13:51 +0000	[thread overview]
Message-ID: <marc-lartc-99246686323392@msgid-missing> (raw)
In-Reply-To: <marc-lartc-99241178429581@msgid-missing>

> What are the benefits of using ip to assign another IP address to an
> existing interface instead of using ifconfig?

Using the ip tool more closely resembles what is actually going on at the
kernel level. ifconfig has been hacked to allow the old syntax to work, but
it adds ip addresses to an interface, supplying the address with an address
identifier. However, it still is just another address on the interface.
ifconfig will get confused if you add more addresses to a single interface
without adding the 'pseudo-interface' address identifiers.

Doei, Arthur. (If this was too cryptic: I'm tired and drinking beer... :))

-- 
  /\    / |      arthurvl@sci.kun.nl      | Work like you don't need the money
 /__\  /  | A friend is someone with whom | Love like you have never been hurt
/    \/__ | you can dare to be yourself   | Dance like there's nobody watching


_______________________________________________
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 21:13 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
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 [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=marc-lartc-99246686323392@msgid-missing \
    --to=arthurvl@sci.kun.nl \
    --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