From: Stephen Hemminger <shemminger@osdl.org>
To: bferrell@baywinds.org
Cc: Bert Hubbs <bhubbs@mbgdocs.com>, bridge@lists.osdl.org
Subject: Re: [Bridge] Bridge support unavailable
Date: Tue, 13 Jul 2004 13:43:34 -0700 [thread overview]
Message-ID: <20040713134334.03c62ab8@dell_ss3.pdx.osdl.net> (raw)
In-Reply-To: <1089749757.31365@baywinds.org>
On Tue, 13 Jul 2004 13:15:57 -0700
bferrell@baywinds.org wrote:
> Stephen,
>
> The module will only autoload if /etc/modules.conf is setup for it. Checking redhat 7.3, redhat 9.0, WhiteBox EL3, Suse 8.0 and Suse 9.0 systems, none have anything to cause bridge.o to alias to br0. Those are the only systems I have to look at. I don't know what other distros like debian or mandrake do for bridge.o. They might have it in the modules.conf file... Dunno.
>
Wrong! It gets done by:
static int sock_ioctl(struct inode *inode, struct file *file, unsigned int cmd,
unsigned long arg)
{
...
switch(cmd) {
...
case SIOCGIFBR:
case SIOCSIFBR:
case SIOCBRADDBR:
case SIOCBRDELBR:
err = -ENOPKG;
if (!br_ioctl_hook)
request_module("bridge");
> So, Bert, you'll need to add something like this to /etc/modules.conf:
>
> alias br0 bridge
Don't do that. It will autoload the bridge, but br0 will not be created automatically!
I.e. if the configuration script does:
ifconfig br0 up
Then it will load the bridge module, but since the bridge hasn't been created you will
get "no such device" error.
next prev parent reply other threads:[~2004-07-13 20:43 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-13 20:15 [Bridge] Bridge support unavailable bferrell
2004-07-13 20:43 ` Stephen Hemminger [this message]
2004-07-14 5:57 ` Bruce Ferrell
-- strict thread matches above, loose matches on Subject: below --
2004-07-14 22:37 Bert Hubbs
2004-07-13 16:17 Bert Hubbs
2004-07-13 16:54 ` Stephen Hemminger
2004-07-12 19:18 Bert Hubbs
2004-07-13 4:05 ` Bruce Ferrell
2004-07-07 15:51 Bert Hubbs
2004-07-06 15:07 Bert Hubbs
2004-07-09 13:45 ` Bruce Ferrell
2004-07-02 17:17 Bert Hubbs
2004-07-06 2:40 ` Bruce Ferrell
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=20040713134334.03c62ab8@dell_ss3.pdx.osdl.net \
--to=shemminger@osdl.org \
--cc=bferrell@baywinds.org \
--cc=bhubbs@mbgdocs.com \
--cc=bridge@lists.osdl.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.