[Bridge] Bridge support unavailable

[Bridge] Bridge support unavailable

[Bert Hubbs]

When I start Linux I get an error:

"Bridge support unavailable: brctl not found". 

And then eth0 - 2 load with no problems. After system is up I can build
the bridge but it does not survive a reboot. Do I need a startup script
or should it build from the:

/etc/init.d/bridge
/etc/sysconfig/network-scripts/ifcfg-bro
/etc/sysconfig/network-scripts/ifcfg-eth0
/etc/sysconfig/network-scripts/ifcfg-eth1
/etc/sysconfig/network-scripts/ifcfg-eth2



I am using Core2 



Bert Hubbs
McGlinchey Stafford and
Youngblood & Bendalin, PLLC
2711 N. Haskell Ave.
Suite 2700, LB 25
Dallas, TX 75204
214-257-1817 (direct dial)
469-235-1817 (mobile)
214-257-1881 (fax)



The information contained in this e-mail message is intended only for the personal and confidential use of the recipient(s) named above. This message may be an attorney-client communication and/or work product and as such is privileged and confidential. If the reader of this message is not the intended recipient or an agent responsible for delivering it to the intended recipient, you are hereby notified that you have received this document in error and that any review, dissemination, distribution, or copying of this message is strictly prohibited. If you have received this communication in error, please notify us immediately by e-mail, and delete the original message. 

Re: [Bridge] Bridge support unavailable

[Bruce Ferrell]

That sounds like you need the full path to brctl in your script.

Which leads me to MY question for the list.  I'm having problem getting 
bridge.o to build correctly on 2.4.25 (linus).  Is this a case where I'd 
be better off with it built static?

Bert Hubbs wrote:
> When I start Linux I get an error:
> 
> "Bridge support unavailable: brctl not found". 
> 
> And then eth0 - 2 load with no problems. After system is up I can build
> the bridge but it does not survive a reboot. Do I need a startup script
> or should it build from the:
> 
> /etc/init.d/bridge
> /etc/sysconfig/network-scripts/ifcfg-bro
> /etc/sysconfig/network-scripts/ifcfg-eth0
> /etc/sysconfig/network-scripts/ifcfg-eth1
> /etc/sysconfig/network-scripts/ifcfg-eth2
> 
> 
> 
> I am using Core2 
> 
> 
> 
> Bert Hubbs
> McGlinchey Stafford and
> Youngblood & Bendalin, PLLC
> 2711 N. Haskell Ave.
> Suite 2700, LB 25
> Dallas, TX 75204
> 214-257-1817 (direct dial)
> 469-235-1817 (mobile)
> 214-257-1881 (fax)
> 
> 
> 
> The information contained in this e-mail message is intended only for the personal and confidential use of the recipient(s) named above. This message may be an attorney-client communication and/or work product and as such is privileged and confidential. If the reader of this message is not the intended recipient or an agent responsible for delivering it to the intended recipient, you are hereby notified that you have received this document in error and that any review, dissemination, distribution, or copying of this message is strictly prohibited. If you have received this communication in error, please notify us immediately by e-mail, and delete the original message. 
> 
> 
> 
> ------------------------------------------------------------------------
> 
> _______________________________________________
> Bridge mailing list
> Bridge@lists.osdl.org
> http://lists.osdl.org/mailman/listinfo/bridge

RE: [Bridge] Bridge support unavailable

[Bert Hubbs]

" That sounds like you need the full path to brctl in your script."

What script?



Bert Hubbs
McGlinchey Stafford and
Youngblood & Bendalin, PLLC
2711 N. Haskell Ave.
Suite 2700, LB 25
Dallas, TX 75204
214-257-1817 (direct dial)
469-235-1817 (mobile)
214-257-1881 (fax)


-----Original Message-----
From: Bruce Ferrell [mailto:bferrell@baywinds.org] 
Sent: Monday, July 05, 2004 9:41 PM
To: Bert Hubbs
Cc: bridge@lists.osdl.org
Subject: Re: [Bridge] Bridge support unavailable

That sounds like you need the full path to brctl in your script.

Which leads me to MY question for the list.  I'm having problem getting 
bridge.o to build correctly on 2.4.25 (linus).  Is this a case where I'd

be better off with it built static?

Bert Hubbs wrote:
> When I start Linux I get an error:
> 
> "Bridge support unavailable: brctl not found". 
> 
> And then eth0 - 2 load with no problems. After system is up I can
build
> the bridge but it does not survive a reboot. Do I need a startup
script
> or should it build from the:
> 
> /etc/init.d/bridge
> /etc/sysconfig/network-scripts/ifcfg-bro
> /etc/sysconfig/network-scripts/ifcfg-eth0
> /etc/sysconfig/network-scripts/ifcfg-eth1
> /etc/sysconfig/network-scripts/ifcfg-eth2
> 
> 
> 
> I am using Core2 
> 
> 
> 
> Bert Hubbs
> McGlinchey Stafford and
> Youngblood & Bendalin, PLLC
> 2711 N. Haskell Ave.
> Suite 2700, LB 25
> Dallas, TX 75204
> 214-257-1817 (direct dial)
> 469-235-1817 (mobile)
> 214-257-1881 (fax)
> 
> 
> 
> The information contained in this e-mail message is intended only for
the personal and confidential use of the recipient(s) named above. This
message may be an attorney-client communication and/or work product and
as such is privileged and confidential. If the reader of this message is
not the intended recipient or an agent responsible for delivering it to
the intended recipient, you are hereby notified that you have received
this document in error and that any review, dissemination, distribution,
or copying of this message is strictly prohibited. If you have received
this communication in error, please notify us immediately by e-mail, and
delete the original message. 
> 
> 
> 
>
------------------------------------------------------------------------
> 
> _______________________________________________
> Bridge mailing list
> Bridge@lists.osdl.org
> http://lists.osdl.org/mailman/listinfo/bridge


The information contained in this e-mail message is intended only for the personal and confidential use of the recipient(s) named above. This message may be an attorney-client communication and/or work product and as such is privileged and confidential. If the reader of this message is not the intended recipient or an agent responsible for delivering it to the intended recipient, you are hereby notified that you have received this document in error and that any review, dissemination, distribution, or copying of this message is strictly prohibited. If you have received this communication in error, please notify us immediately by e-mail, and delete the original message. 

[Bridge] Bridge support unavailable

[Bert Hubbs]

When I start Linux I get an error:
 
"Bridge support unavailable: brctl not found".

And then eth0 - 2 load with no problems. After system is up I can 
build the bridge but it does not survive a reboot. Do I need a startup 
script or should the bridge build from the:

/etc/init.d/bridge
/etc/sysconfig/network-scripts/ifcfg-bro
/etc/sysconfig/network-scripts/ifcfg-eth0
/etc/sysconfig/network-scripts/ifcfg-eth1
/etc/sysconfig/network-scripts/ifcfg-eth2

I am using Core2



The information contained in this e-mail message is intended only for the personal and confidential use of the recipient(s) named above. This message may be an attorney-client communication and/or work product and as such is privileged and confidential. If the reader of this message is not the intended recipient or an agent responsible for delivering it to the intended recipient, you are hereby notified that you have received this document in error and that any review, dissemination, distribution, or copying of this message is strictly prohibited. If you have received this communication in error, please notify us immediately by e-mail, and delete the original message. 

Re: [Bridge] Bridge support unavailable

[Bruce Ferrell]

Well... You need to determine what script the error is coming from... 
Probably /etc/rc.d/init.d/network (or it could be /etc/init.d/network)


Bert Hubbs wrote:
> " That sounds like you need the full path to brctl in your script."
> 
> What script?
> 
> 
> 
> Bert Hubbs
> McGlinchey Stafford and
> Youngblood & Bendalin, PLLC
> 2711 N. Haskell Ave.
> Suite 2700, LB 25
> Dallas, TX 75204
> 214-257-1817 (direct dial)
> 469-235-1817 (mobile)
> 214-257-1881 (fax)
> 
> 
> -----Original Message-----
> From: Bruce Ferrell [mailto:bferrell@baywinds.org] 
> Sent: Monday, July 05, 2004 9:41 PM
> To: Bert Hubbs
> Cc: bridge@lists.osdl.org
> Subject: Re: [Bridge] Bridge support unavailable
> 
> That sounds like you need the full path to brctl in your script.
> 
> Which leads me to MY question for the list.  I'm having problem getting 
> bridge.o to build correctly on 2.4.25 (linus).  Is this a case where I'd
> 
> be better off with it built static?
> 
> Bert Hubbs wrote:
> 
>>When I start Linux I get an error:
>>
>>"Bridge support unavailable: brctl not found". 
>>
>>And then eth0 - 2 load with no problems. After system is up I can
> 
> build
> 
>>the bridge but it does not survive a reboot. Do I need a startup
> 
> script
> 
>>or should it build from the:
>>
>>/etc/init.d/bridge
>>/etc/sysconfig/network-scripts/ifcfg-bro
>>/etc/sysconfig/network-scripts/ifcfg-eth0
>>/etc/sysconfig/network-scripts/ifcfg-eth1
>>/etc/sysconfig/network-scripts/ifcfg-eth2
>>
>>
>>
>>I am using Core2 
>>
>>
>>
>>Bert Hubbs
>>McGlinchey Stafford and
>>Youngblood & Bendalin, PLLC
>>2711 N. Haskell Ave.
>>Suite 2700, LB 25
>>Dallas, TX 75204
>>214-257-1817 (direct dial)
>>469-235-1817 (mobile)
>>214-257-1881 (fax)
>>
>>
>>
>>The information contained in this e-mail message is intended only for
> 
> the personal and confidential use of the recipient(s) named above. This
> message may be an attorney-client communication and/or work product and
> as such is privileged and confidential. If the reader of this message is
> not the intended recipient or an agent responsible for delivering it to
> the intended recipient, you are hereby notified that you have received
> this document in error and that any review, dissemination, distribution,
> or copying of this message is strictly prohibited. If you have received
> this communication in error, please notify us immediately by e-mail, and
> delete the original message. 
> 
>>
>>
>>
> ------------------------------------------------------------------------
> 
>>_______________________________________________
>>Bridge mailing list
>>Bridge@lists.osdl.org
>>http://lists.osdl.org/mailman/listinfo/bridge
> 
> 
> 
> The information contained in this e-mail message is intended only for the personal and confidential use of the recipient(s) named above. This message may be an attorney-client communication and/or work product and as such is privileged and confidential. If the reader of this message is not the intended recipient or an agent responsible for delivering it to the intended recipient, you are hereby notified that you have received this document in error and that any review, dissemination, distribution, or copying of this message is strictly prohibited. If you have received this communication in error, please notify us immediately by e-mail, and delete the original message. 
> 

RE: [Bridge] Bridge support unavailable

[Bert Hubbs]

[-- Attachment #1: Type: text/plain, Size: 4525 bytes --]

So Linux does not have a "PATH" while booting? I have brctl in the /bin
and the /sbin directory.

I looked at the /etc/init.d/network  script and there is mention of
bridges but no direct call to brctl.

Do you think I would be better of recompiling the Kernel with bridging
built in?

 

Well... You need to determine what script the error is coming from... 
Probably /etc/rc.d/init.d/network (or it could be /etc/init.d/network) 

 

Bert Hubbs wrote: 
> " That sounds like you need the full path to brctl in your script." 
> 
> What script? 
> 
> 
> 
> Bert Hubbs 
> McGlinchey Stafford and 
> Youngblood & Bendalin, PLLC 
> 2711 N. Haskell Ave. 
> Suite 2700, LB 25 
> Dallas, TX 75204 
> 214-257-1817 (direct dial) 
> 469-235-1817 (mobile) 
> 214-257-1881 (fax) 
> 
> 
> -----Original Message----- 
> From: Bruce Ferrell [mailto:bferrell@baywinds.org] 
> Sent: Monday, July 05, 2004 9:41 PM 
> To: Bert Hubbs 
> Cc: bridge@lists.osdl.org 
> Subject: Re: [Bridge] Bridge support unavailable 
> 
> That sounds like you need the full path to brctl in your script. 
> 
> Which leads me to MY question for the list.  I'm having problem
getting 
> bridge.o to build correctly on 2.4.25 (linus).  Is this a case where
I'd 
> 
> be better off with it built static? 
> 
> Bert Hubbs wrote: 
> 
>>When I start Linux I get an error: 
>> 
>>"Bridge support unavailable: brctl not found". 
>> 
>>And then eth0 - 2 load with no problems. After system is up I can 
> 
> build 
> 
>>the bridge but it does not survive a reboot. Do I need a startup 
> 
> script 
> 
>>or should it build from the: 
>> 
>>/etc/init.d/bridge 
>>/etc/sysconfig/network-scripts/ifcfg-bro 
>>/etc/sysconfig/network-scripts/ifcfg-eth0 
>>/etc/sysconfig/network-scripts/ifcfg-eth1 
>>/etc/sysconfig/network-scripts/ifcfg-eth2 
>> 
>> 
>> 
>>I am using Core2 
>> 
>> 
>> 
>>Bert Hubbs 
>>McGlinchey Stafford and 
>>Youngblood & Bendalin, PLLC 
>>2711 N. Haskell Ave. 
>>Suite 2700, LB 25 
>>Dallas, TX 75204 
>>214-257-1817 (direct dial) 
>>469-235-1817 (mobile) 
>>214-257-1881 (fax) 
>> 
>> 
>> 
>>The information contained in this e-mail message is intended only for 
> 
> the personal and confidential use of the recipient(s) named above.
This 
> message may be an attorney-client communication and/or work product
and 
> as such is privileged and confidential. If the reader of this message
is 
> not the intended recipient or an agent responsible for delivering it
to 
> the intended recipient, you are hereby notified that you have received

> this document in error and that any review, dissemination,
distribution, 
> or copying of this message is strictly prohibited. If you have
received 
> this communication in error, please notify us immediately by e-mail,
and 
> delete the original message. 
> 
>> 
>> 
>> 
>
------------------------------------------------------------------------

> 
>>_______________________________________________ 
>>Bridge mailing list 
>>Bridge@lists.osdl.org 
>>http://lists.osdl.org/mailman/listinfo/bridge 
> 
> 
> 
> The information contained in this e-mail message is intended only for
the personal and confidential use of the recipient(s) named above. This
message may be an attorney-client communication and/or work product and
as such is privileged and confidential. If the reader of this message is
not the intended recipient or an agent responsible for delivering it to
the intended recipient, you are hereby notified that you have received
this document in error and that any review, dissemination, distribution,
or copying of this message is strictly prohibited. If you have received
this communication in error, please notify us immediately by e-mail, and
delete the original message. 

> 


The information contained in this e-mail message is intended only for the personal and confidential use of the recipient(s) named above. This message may be an attorney-client communication and/or work product and as such is privileged and confidential. If the reader of this message is not the intended recipient or an agent responsible for delivering it to the intended recipient, you are hereby notified that you have received this document in error and that any review, dissemination, distribution, or copying of this message is strictly prohibited. If you have received this communication in error, please notify us immediately by e-mail, and delete the original message. 

[-- Attachment #2: Type: text/html, Size: 14700 bytes --]

Re: [Bridge] Bridge support unavailable

[Bruce Ferrell]

Bert,

Some init script that is trying to execute brctl and causing your error. 
  Finding that script can be... interesting.

One thing you almost certainly want to check is to see if bridge.o is 
being loaded.  Use lsmod as root to see if it's loaded.  If it is 
loaded, then you almost certainly won't need to rebuild the kernel.  If 
you don't see it loaded, try modprobe bridge and re-check with lsmod. 
If it loads, again, no kernel rebuild needed.



Bert Hubbs wrote:
> -->
> 
> So Linux does not have a “PATH” while booting? I have brctl in the /bin 
> and the /sbin directory.
> 
> I looked at the /etc/init.d/network  script and there is mention of 
> bridges but no direct call to brctl.
> 
> Do you think I would be better of recompiling the Kernel with bridging 
> built in?
> 
>  
> 
> Well... You need to determine what script the error is coming from...
> Probably /etc/rc.d/init.d/network (or it could be /etc/init.d/network)
> 
>  
> 
> Bert Hubbs wrote:
>>  " That sounds like you need the full path to brctl in your script."
>>
>>  What script?
>>
>>
>>
>>  Bert Hubbs
>>  McGlinchey Stafford and
>>  Youngblood & Bendalin, PLLC
>>  2711 N. Haskell Ave.
>>  Suite 2700, LB 25
>>  Dallas, TX 75204
>>  214-257-1817 (direct dial)
>>  469-235-1817 (mobile)
>>  214-257-1881 (fax)
>>
>>
>>  -----Original Message-----
>>  From: Bruce Ferrell [mailto:bferrell@baywinds.org]
>>  Sent: Monday, July 05, 2004 9:41 PM
>>  To: Bert Hubbs
>>  Cc: bridge@lists.osdl.org
>>  Subject: Re: [Bridge] Bridge support unavailable
>>
>>  That sounds like you need the full path to brctl in your script.
>>
>>  Which leads me to MY question for the list.  I'm having problem getting
>>  bridge.o to build correctly on 2.4.25 (linus).  Is this a case where I'd
>>
>>  be better off with it built static?
>>
>>  Bert Hubbs wrote:
>>
>> >When I start Linux I get an error:
>> >
>> >"Bridge support unavailable: brctl not found".
>> >
>> >And then eth0 - 2 load with no problems. After system is up I can
>>
>>  build
>>
>> >the bridge but it does not survive a reboot. Do I need a startup
>>
>>  script
>>
>> >or should it build from the:
>> >
>> >/etc/init.d/bridge
>> >/etc/sysconfig/network-scripts/ifcfg-bro
>> >/etc/sysconfig/network-scripts/ifcfg-eth0
>> >/etc/sysconfig/network-scripts/ifcfg-eth1
>> >/etc/sysconfig/network-scripts/ifcfg-eth2
>> >
>> >
>> >
>> >I am using Core2
>> >
>> >
>> >
>> >Bert Hubbs
>> >McGlinchey Stafford and
>> >Youngblood & Bendalin, PLLC
>> >2711 N. Haskell Ave.
>> >Suite 2700, LB 25
>> >Dallas, TX 75204
>> >214-257-1817 (direct dial)
>> >469-235-1817 (mobile)
>> >214-257-1881 (fax)
>> >
>> >
>> >
>> >The information contained in this e-mail message is intended only for
>>
>>  the personal and confidential use of the recipient(s) named above. This
>>  message may be an attorney-client communication and/or work product and
>>  as such is privileged and confidential. If the reader of this message is
>>  not the intended recipient or an agent responsible for delivering it to
>>  the intended recipient, you are hereby notified that you have received
>>  this document in error and that any review, dissemination, distribution,
>>  or copying of this message is strictly prohibited. If you have received
>>  this communication in error, please notify us immediately by e-mail, and
>>  delete the original message.
>>
>> >
>> >
>> >
>>  ------------------------------------------------------------------------
>>
>> >_______________________________________________
>> >Bridge mailing list
>> >Bridge@lists.osdl.org
>> >http://lists.osdl.org/mailman/listinfo/bridge
>>
>>
>>
>>  The information contained in this e-mail message is intended only for 
> the personal and confidential use of the recipient(s) named above. This 
> message may be an attorney-client communication and/or work product and 
> as such is privileged and confidential. If the reader of this message is 
> not the intended recipient or an agent responsible for delivering it to 
> the intended recipient, you are hereby notified that you have received 
> this document in error and that any review, dissemination, distribution, 
> or copying of this message is strictly prohibited. If you have received 
> this communication in error, please notify us immediately by e-mail, and 
> delete the original message.
> 
>>
> 
> 
> The information contained in this e-mail message is intended only for 
> the personal and confidential use of the recipient(s) named above. This 
> message may be an attorney-client communication and/or work product and 
> as such is privileged and confidential. If the reader of this message is 
> not the intended recipient or an agent responsible for delivering it to 
> the intended recipient, you are hereby notified that you have received 
> this document in error and that any review, dissemination, distribution, 
> or copying of this message is strictly prohibited. If you have received 
> this communication in error, please notify us immediately by e-mail, and 
> delete the original message.

RE: [Bridge] Bridge support unavailable

[Bert Hubbs]

Yep!
First lsmod I got no bridge. Second lsmod after modprobe bridge I got
bridge listed. So here comes the $35 question. How do you make the
module load at boot?
After Googleing modprobe, lsmod, insmod there seems to be know way to
use modprobe to load modules at boot. I came across discussion to add it
to modprobe.conf but others said this would not cause it to load at
boot. Another mentioned rc.local but I'm not sure that rc.local will
load at the right time. On the other had that may not matter but I'm in
to cleanliness.

Any suggestions?



Bert Hubbs
McGlinchey Stafford and
Youngblood & Bendalin, PLLC
2711 N. Haskell Ave.
Suite 2700, LB 25
Dallas, TX 75204
214-257-1817 (direct dial)
469-235-1817 (mobile)
214-257-1881 (fax)


-----Original Message-----
From: Bruce Ferrell [mailto:bferrell@baywinds.org] 
Sent: Monday, July 12, 2004 11:05 PM
To: Bert Hubbs
Cc: bridge@lists.osdl.org
Subject: Re: [Bridge] Bridge support unavailable

Bert,

Some init script that is trying to execute brctl and causing your error.

  Finding that script can be... interesting.

One thing you almost certainly want to check is to see if bridge.o is 
being loaded.  Use lsmod as root to see if it's loaded.  If it is 
loaded, then you almost certainly won't need to rebuild the kernel.  If 
you don't see it loaded, try modprobe bridge and re-check with lsmod. 
If it loads, again, no kernel rebuild needed.



Bert Hubbs wrote:
> -->
> 
> So Linux does not have a "PATH" while booting? I have brctl in the
/bin 
> and the /sbin directory.
> 
> I looked at the /etc/init.d/network  script and there is mention of 
> bridges but no direct call to brctl.
> 
> Do you think I would be better of recompiling the Kernel with bridging

> built in?
> 
>  
> 
> Well... You need to determine what script the error is coming from...
> Probably /etc/rc.d/init.d/network (or it could be /etc/init.d/network)
> 
>  
> 
> Bert Hubbs wrote:
>>  " That sounds like you need the full path to brctl in your script."
>>
>>  What script?
>>
>>
>>
>>  Bert Hubbs
>>  McGlinchey Stafford and
>>  Youngblood & Bendalin, PLLC
>>  2711 N. Haskell Ave.
>>  Suite 2700, LB 25
>>  Dallas, TX 75204
>>  214-257-1817 (direct dial)
>>  469-235-1817 (mobile)
>>  214-257-1881 (fax)
>>
>>
>>  -----Original Message-----
>>  From: Bruce Ferrell [mailto:bferrell@baywinds.org]
>>  Sent: Monday, July 05, 2004 9:41 PM
>>  To: Bert Hubbs
>>  Cc: bridge@lists.osdl.org
>>  Subject: Re: [Bridge] Bridge support unavailable
>>
>>  That sounds like you need the full path to brctl in your script.
>>
>>  Which leads me to MY question for the list.  I'm having problem
getting
>>  bridge.o to build correctly on 2.4.25 (linus).  Is this a case where
I'd
>>
>>  be better off with it built static?
>>
>>  Bert Hubbs wrote:
>>
>> >When I start Linux I get an error:
>> >
>> >"Bridge support unavailable: brctl not found".
>> >
>> >And then eth0 - 2 load with no problems. After system is up I can
>>
>>  build
>>
>> >the bridge but it does not survive a reboot. Do I need a startup
>>
>>  script
>>
>> >or should it build from the:
>> >
>> >/etc/init.d/bridge
>> >/etc/sysconfig/network-scripts/ifcfg-bro
>> >/etc/sysconfig/network-scripts/ifcfg-eth0
>> >/etc/sysconfig/network-scripts/ifcfg-eth1
>> >/etc/sysconfig/network-scripts/ifcfg-eth2
>> >
>> >
>> >
>> >I am using Core2
>> >
>> >
>> >
>> >Bert Hubbs
>> >McGlinchey Stafford and
>> >Youngblood & Bendalin, PLLC
>> >2711 N. Haskell Ave.
>> >Suite 2700, LB 25
>> >Dallas, TX 75204
>> >214-257-1817 (direct dial)
>> >469-235-1817 (mobile)
>> >214-257-1881 (fax)
>> >
>> >
>> >
>> >The information contained in this e-mail message is intended only
for
>>
>>  the personal and confidential use of the recipient(s) named above.
This
>>  message may be an attorney-client communication and/or work product
and
>>  as such is privileged and confidential. If the reader of this
message is
>>  not the intended recipient or an agent responsible for delivering it
to
>>  the intended recipient, you are hereby notified that you have
received
>>  this document in error and that any review, dissemination,
distribution,
>>  or copying of this message is strictly prohibited. If you have
received
>>  this communication in error, please notify us immediately by e-mail,
and
>>  delete the original message.
>>
>> >
>> >
>> >
>>
------------------------------------------------------------------------
>>
>> >_______________________________________________
>> >Bridge mailing list
>> >Bridge@lists.osdl.org
>> >http://lists.osdl.org/mailman/listinfo/bridge
>>
>>
>>
>>  The information contained in this e-mail message is intended only
for 
> the personal and confidential use of the recipient(s) named above.
This 
> message may be an attorney-client communication and/or work product
and 
> as such is privileged and confidential. If the reader of this message
is 
> not the intended recipient or an agent responsible for delivering it
to 
> the intended recipient, you are hereby notified that you have received

> this document in error and that any review, dissemination,
distribution, 
> or copying of this message is strictly prohibited. If you have
received 
> this communication in error, please notify us immediately by e-mail,
and 
> delete the original message.
> 
>>
> 
> 
> The information contained in this e-mail message is intended only for 
> the personal and confidential use of the recipient(s) named above.
This 
> message may be an attorney-client communication and/or work product
and 
> as such is privileged and confidential. If the reader of this message
is 
> not the intended recipient or an agent responsible for delivering it
to 
> the intended recipient, you are hereby notified that you have received

> this document in error and that any review, dissemination,
distribution, 
> or copying of this message is strictly prohibited. If you have
received 
> this communication in error, please notify us immediately by e-mail,
and 
> delete the original message.


The information contained in this e-mail message is intended only for the personal and confidential use of the recipient(s) named above. This message may be an attorney-client communication and/or work product and as such is privileged and confidential. If the reader of this message is not the intended recipient or an agent responsible for delivering it to the intended recipient, you are hereby notified that you have received this document in error and that any review, dissemination, distribution, or copying of this message is strictly prohibited. If you have received this communication in error, please notify us immediately by e-mail, and delete the original message. 

Re: [Bridge] Bridge support unavailable

[Stephen Hemminger]

On Tue, 13 Jul 2004 11:17:51 -0500
"Bert Hubbs" <bhubbs@mbgdocs.com> wrote:

> Yep!
> First lsmod I got no bridge. Second lsmod after modprobe bridge I got
> bridge listed. So here comes the $35 question. How do you make the
> module load at boot?
> After Googleing modprobe, lsmod, insmod there seems to be know way to
> use modprobe to load modules at boot. I came across discussion to add it
> to modprobe.conf but others said this would not cause it to load at
> boot. Another mentioned rc.local but I'm not sure that rc.local will
> load at the right time. On the other had that may not matter but I'm in
> to cleanliness.
> 
> Any suggestions?

Your working too hard at getting it loaded.  The kernel will automatically load the bridge module when the first bridge is created with brctl.  Since brctl has to do an ioctl() to create a bridge, the kernel will load the module if needed.  You can't build the bridge module seperate from the kernel. The kernel needs to know the bridge
module is coming to have the necessary hooks.

Just doing:
	brctl addbr br0
should create bridge br0 and load the bridge module.

Re: [Bridge] Bridge support unavailable

[bferrell]

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.

So, Bert, you'll need to add something like this to /etc/modules.conf:

alias br0 bridge

The stuff I sent before was in the nature of diagnostics and debugging

I'm still trying to get my beridge.o to build cleanly :(


> On Tue, 13 Jul 2004 11:17:51 -0500
> Stephen Hemminger <shemminger@osdl.org> wrote ..
> On Tue, 13 Jul 2004 11:17:51 -0500
> "Bert Hubbs" <bhubbs@mbgdocs.com> wrote:
> 
> > Yep!
> > First lsmod I got no bridge. Second lsmod after modprobe bridge I got
> > bridge listed. So here comes the $35 question. How do you make the
> > module load at boot?
> > After Googleing modprobe, lsmod, insmod there seems to be know way to
> > use modprobe to load modules at boot. I came across discussion to add
> it
> > to modprobe.conf but others said this would not cause it to load at
> > boot. Another mentioned rc.local but I'm not sure that rc.local will
> > load at the right time. On the other had that may not matter but I'm
> in
> > to cleanliness.
> > 
> > Any suggestions?
> 
> Your working too hard at getting it loaded.  The kernel will automatically
> load the bridge module when the first bridge is created with brctl.  Since
> brctl has to do an ioctl() to create a bridge, the kernel will load the
> module if needed.  You can't build the bridge module seperate from the
> kernel. The kernel needs to know the bridge
> module is coming to have the necessary hooks.
> 
> Just doing:
> 	brctl addbr br0
> should create bridge br0 and load the bridge module.

Re: [Bridge] Bridge support unavailable

[Stephen Hemminger]

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.

Re: [Bridge] Bridge support unavailable

[Bruce Ferrell]

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@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.
> 

RE: [Bridge] Bridge support unavailable

[Bert Hubbs]

I don't have a modules.conf. I have modprobe.conf and it has alias
entries for network adapter/driver. I added "alias br0 bridge" but no
change.
During boot something is trying to call the bridge up but it can't find
brctl. Loopback loads then bridge then the three network cards.
This may come as no surprise but I just discovered that even though I
was able to build the bridge, when I performed a ifup br0 I got the same
message I get at boot time.

I'm wondering now if I didn't get brctl installed properly. I never
found definitive installation instruction so I wondering if anyone knows
the installation procedure. Do I do a "configure" then a "make" and then
a "make install" or just "install"?


Bert Hubbs
McGlinchey Stafford and
Youngblood & Bendalin, PLLC
2711 N. Haskell Ave.
Suite 2700, LB 25
Dallas, TX 75204
214-257-1817 (direct dial)
469-235-1817 (mobile)
214-257-1881 (fax)


-----Original Message-----
From: Bruce Ferrell [mailto:bferrell@baywinds.org] 
Sent: Wednesday, July 14, 2004 12:58 AM
To: Stephen Hemminger
Cc: Bert Hubbs; bridge@lists.osdl.org
Subject: Re: [Bridge] Bridge support unavailable

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@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.
> 


The information contained in this e-mail message is intended only for the personal and confidential use of the recipient(s) named above. This message may be an attorney-client communication and/or work product and as such is privileged and confidential. If the reader of this message is not the intended recipient or an agent responsible for delivering it to the intended recipient, you are hereby notified that you have received this document in error and that any review, dissemination, distribution, or copying of this message is strictly prohibited. If you have received this communication in error, please notify us immediately by e-mail, and delete the original message.