From: lsorense@csclub.uwaterloo.ca (Lennart Sorensen)
To: Mike Schmidt <mike@intello.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.6 kernel: Cannot make multiple dummy network interfaces
Date: Fri, 8 Jun 2007 13:50:58 -0400 [thread overview]
Message-ID: <20070608175058.GG10008@csclub.uwaterloo.ca> (raw)
In-Reply-To: <46699318.3060209@intello.com>
On Fri, Jun 08, 2007 at 01:34:16PM -0400, Mike Schmidt wrote:
> (please cc me directly with any responses - I am not (yet) a member of
> this mailing list.
>
> *2.6 kernel: Cannot make multiple dummy network interfaces*
> ------------------------------------------------------------------------
> I'm trying to set up a number of dummy interfaces but FC6 (Centos4, even
> RHEL4) won't make more than 1. a modprobe -c lists two default dummy
> interfaces, dumm0 and dummy1, just as it did even back to rh8. On my
> rh8/rh9 systems, there is no problem, I can generate as many dummy n as
> I want by adding alias and options lines in modules.conf. On
> FC6/Centos/RHEL (I assume as of kernel 2.6, but I don't have any early
> FC systems running) I can only create 1 dummy. I am trying to build a
> network simulator for testing purposes - a bridge with 100+ network
> interfaces. They have to be dummy (not just an alias) because they need
> separate MAC addresses. I have tried the same thing on Knoppix, running
> 2.6.17, with the same results. Centos4 and RHEL4 use kernel 2.6.9
# modinfo dummy
filename: /lib/modules/2.6.18-4-gx1/kernel/drivers/net/dummy.ko
license: GPL
vermagic: 2.6.18-4-gx1 preempt mod_unload GEODEGX1 gcc-3.3
depends:
parm: numdummies:Number of dummy pseudo devices (int)
Perhaps you want to pass that numdummies aregument with some value. The
default may be pretty low.
--
Len Sorensen
next prev parent reply other threads:[~2007-06-08 17:51 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-08 17:34 Mike Schmidt
2007-06-08 17:50 ` Lennart Sorensen [this message]
2007-06-08 18:29 ` Mike Schmidt
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=20070608175058.GG10008@csclub.uwaterloo.ca \
--to=lsorense@csclub.uwaterloo.ca \
--cc=linux-kernel@vger.kernel.org \
--cc=mike@intello.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®