All of lore.kernel.org
 help / color / mirror / Atom feed
From: Patrick Turley <pturley@rocksteady.com>
To: lartc@vger.kernel.org
Subject: [LARTC] Limit on Primary Addresses
Date: Fri, 17 Sep 2004 16:00:30 +0000	[thread overview]
Message-ID: <414B0A1E.9080904@rocksteady.com> (raw)

I am trying to configure a Linux box with all possible VLANs (4094 of 
them), and a subnet on each VLAN. Creating the VLANs isn't a problem. 
But, when I try to use "ip addr add ..." commands to assign an IP 
address to each VLAN interface, I get to do about 280 of them before all 
the interfaces on the box become unresponsive. I've also tried to assign 
the same IP addresses all to eth0, and I get the same result.

The problem seems to hinge on the distinction between primary and 
secondary addresses.

If you're reading the LARTC list, then you've probably had the need 
(e.g., load testing) to assign thousands of IP addresses to a single 
interface. However, it's usually the case that one is assigning multiple 
addresses that all belong to the same subnet. In that case, the first 
such IP address is "primary" and all the additional addresses that 
belong to the same subnet are "secondary". My investigations tell me 
that "secondary" addresses are much lighter-weight. On the other hand, I 
don't seem to be able to assign more than about 280 "primary" addresses 
in the entire system before all the interfaces become unresponsive.

For additional information about "primary" vs. "secondary" addresses, 
take a look at:

http://www.linux-ip.net/html/linux-ip.html#tools-ip-address-add
http://www.linux-ip.net/gl/ip-cref/node33.html

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

                 reply	other threads:[~2004-09-17 16:00 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=414B0A1E.9080904@rocksteady.com \
    --to=pturley@rocksteady.com \
    --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 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.