From: David Ford <david+cert@blue-labs.org>
To: Jim Roland <jroland@roland.net>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Kernel ethernet alias limit
Date: Tue, 19 Feb 2002 13:03:45 -0500 [thread overview]
Message-ID: <3C729381.6050105@blue-labs.org> (raw)
In-Reply-To: <000701c1b929$33a47c60$ab9eef0c@jimws>
[-- Attachment #1: Type: text/plain, Size: 1056 bytes --]
You don't need dummy ethN:N interfaces. Use the iproute2 tools, 'ip'
specifically.
ip link set eth0 down
ip address flush eth0
ip address add 1.2.3.4/24 brd + dev eth0
ip address add 1.2.3.5/25 brd + dev eth0
ip address add ....to your heart's content
ip link set eth0 up
ip route add default via 2.3.8.9 via 5.4.3.2 dev eth0
See the scripts on http://blue-labs.org/ for some examples.
David
Jim Roland wrote:
>I seem to remember back in either Kernel 2.0 or 2.2 there was a limit of 256
>aliases within the ethX aliasing (eg, eth0, then eth0:0 thru eth0:255).
>
>Has the limit on this been expanded with Kernel 2.4, is it stable and/or
>advised? I have a need to bind more than 256 addresses to a single
>interface. Without installing additional network cards.
>
>Thanks,
>Jim Roland, RHCE
>
>
>-
>To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
>the body of a message to majordomo@vger.kernel.org
>More majordomo info at http://vger.kernel.org/majordomo-info.html
>Please read the FAQ at http://www.tux.org/lkml/
>
[-- Attachment #2: S/MIME Cryptographic Signature --]
[-- Type: application/x-pkcs7-signature, Size: 3254 bytes --]
prev parent reply other threads:[~2002-02-19 18:06 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-02-19 9:38 Kernel ethernet alias limit Jim Roland
2002-02-19 10:16 ` Luis Garces
2002-02-19 12:11 ` bert hubert
2002-02-19 18:18 ` David Lang
2002-02-19 18:03 ` David Ford [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=3C729381.6050105@blue-labs.org \
--to=david+cert@blue-labs.org \
--cc=jroland@roland.net \
--cc=linux-kernel@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.