OK Stephen,
I will stipulate the code fragment you've provided is supposed to load
the bridge.o module... BUT from the previous statements, it doesn't work
that way for Bert. As I mentioned my compile of the module has all
those nasty undefined symbol errors so until I get that right all I can
do is talk about the way other modules work.
Is that fragment from brctl BTW?
Stephen Hemminger wrote:
> On Tue, 13 Jul 2004 13:15:57 -0700
> bferrell@xxxxxxxxxxxx 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.
>
