From mboxrd@z Thu Jan 1 00:00:00 1970 Message-ID: <40F35F74.9020205@baywinds.org> Date: Mon, 12 Jul 2004 21:05:08 -0700 From: Bruce Ferrell MIME-Version: 1.0 Subject: Re: [Bridge] Bridge support unavailable References: In-Reply-To: Content-Type: text/plain; charset="windows-1252"; format="flowed" Content-Transfer-Encoding: quoted-printable List-Id: Linux Ethernet Bridging List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Bert Hubbs Cc: bridge@lists.osdl.org Bert, Some init script that is trying to execute brctl and causing your error.=20 Finding that script can be... interesting. One thing you almost certainly want to check is to see if bridge.o is=20 being loaded. Use lsmod as root to see if it's loaded. If it is=20 loaded, then you almost certainly won't need to rebuild the kernel. If=20 you don't see it loaded, try modprobe bridge and re-check with lsmod.=20 If it loads, again, no kernel rebuild needed. Bert Hubbs wrote: > --> >=20 > So Linux does not have a =93PATH=94 while booting? I have brctl in the /b= in=20 > and the /sbin directory. >=20 > I looked at the /etc/init.d/network script and there is mention of=20 > bridges but no direct call to brctl. >=20 > Do you think I would be better of recompiling the Kernel with bridging=20 > built in? >=20 > =20 >=20 > 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) >=20 > =20 >=20 > 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=20 > the personal and confidential use of the recipient(s) named above. This=20 > message may be an attorney-client communication and/or work product and=20 > 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=20 > the intended recipient, you are hereby notified that you have received=20 > this document in error and that any review, dissemination, distribution, = > or copying of this message is strictly prohibited. If you have received=20 > this communication in error, please notify us immediately by e-mail, and = > delete the original message. >=20 >> >=20 >=20 > The information contained in this e-mail message is intended only for=20 > the personal and confidential use of the recipient(s) named above. This=20 > message may be an attorney-client communication and/or work product and=20 > 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=20 > the intended recipient, you are hereby notified that you have received=20 > this document in error and that any review, dissemination, distribution, = > or copying of this message is strictly prohibited. If you have received=20 > this communication in error, please notify us immediately by e-mail, and = > delete the original message.