All of lore.kernel.org
 help / color / mirror / Atom feed
From: Patrick Turley <pturley@rocksteady.com>
To: Jason Opperisano <opie@817west.com>
Cc: netfilter@lists.netfilter.org
Subject: Re: Question about limited primary addresses
Date: Tue, 21 Sep 2004 13:51:01 -0500	[thread overview]
Message-ID: <41507815.8080008@rocksteady.com> (raw)
In-Reply-To: <1095687787.1898.20.camel@wolfpack.ljm.dom>

Jason Opperisano wrote:
 > On Sun, 2004-09-19 at 23:35, Patrick Turley wrote:
 >
 >>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.
.
.
.
 > i'm not aware of any limit.  i believe 2.0/2.2 had an alias limit of 256
 > per interface, but i could be way off base...  there's probably
 > something going on with you particular machine (i.e. memory problem).
 >
 > my test to prove there's not a limit at 4096:
.
.
.
 > contents of "test" are:
 >
 > ----
 > i=1
 > function addIP() {
 >   j=0
 >   while [ $j -le 255 ]; do
 >     sudo ip addr add $1.$j.1.1/24 dev eth0
 >     let "j = $j + 1"
 >   done
 > }
 >
 > while [ $i -le 17 ]; do
 >    addIP $i
 >    let "i = $i + 1"
 > done
 > ----

First of all, thank you very much for the time you spent investigating 
this problem.

Your script works fine on my test computer. I was able to assign all 
4000+ addresses with no problem.

I captured the commands emitted by your script and the commands emitted 
by our software and began the process of making them look more and more 
like each other until the essential difference became clear. I finally 
got to the point where the *only* difference was the IP addresses.

The addresses assigned by your script are (as you said) 
[1-17].[1-255].1.1/24.

The addresses I was assigning were 10.[1-2].[1-255].1/24.

So, the major difference seems to be that all my addresses were confined 
to the 10/8 subnet. It may be important to note that some of the 
addresses generated by your script *did* lie in that range, but the 
majority did not.

I adjusted your script very slightly to put all the addresses in the 
10/8 subnet:


     i=1
     function addIP() {
       j=0
       while [ $j -le 255 ]; do
         sudo ip addr add 10.$1.$j.1/24 dev eth0
         let "j = $j + 1"
       done
     }

     while [ $i -le 2 ]; do
        addIP $i
        let "i = $i + 1"
     done


When I ran this version, I saw the very same failure I've been seeing 
all along.

Would it be possible for you to run the modified version of this script 
on your machine and see if you have any problem?

Thanks again for your time.



  reply	other threads:[~2004-09-21 18:51 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-09-20  3:35 Question about limited primary addresses Patrick Turley
2004-09-20 13:43 ` Jason Opperisano
2004-09-21 18:51   ` Patrick Turley [this message]
2004-09-21 19:21     ` Jason Opperisano
2004-09-21 19:27       ` Patrick Turley
2004-09-21 21:41         ` Patrick Turley

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=41507815.8080008@rocksteady.com \
    --to=pturley@rocksteady.com \
    --cc=netfilter@lists.netfilter.org \
    --cc=opie@817west.com \
    /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.