Date: Wed, 9 Apr 2003 17:10:28 +0300 (EAT) From: Noah K Sematimba <ksemat@ksemat.co.ug> To: "D.Pageau" <dpageau@infodev.ca> Cc: freebsd-isp@freebsd.org Subject: Re: Can't bind IP to my bridge at boot time Message-ID: <20030409170443.T11815@sematin.mtn.co.ug> In-Reply-To: <3E942710.9020908@infodev.ca> References: <3E92D313.5080108@infodev.ca> <20030409131417.A531@sematin.mtn.co.ug> <3E942710.9020908@infodev.ca>
next in thread | previous in thread | raw e-mail | index | archive | help
My guess is that the sysctl file gets called sometime by /etc/rc and thus if you can place the section that calls /etc/rc.sysctl at another section in that file then you would be ok. According to http://www.freebsd.org/send-pr.html you can use the send-pr program to submit a bug report. Noah. On Wed, 9 Apr 2003, D.Pageau wrote: > Yes it make sense. In fact it's my workaround for now. But it's a > workaround not a fix. Where should I report that "bug"? > > #!/bin/sh > > case $1 in > > start) > /sbin/sysctl net.link.ether.bridge=1 > exit 0 > ;; > > stop) > /sbin/sysctl net.link.ether.bridge=0 > exit 0 > ;; > > *) > echo "usage: `basename $0` {start|stop}" >&2 > exit 64 > ;; > esac > > > Noah K Sematimba wrote: > > probably sysctl gets initialised too early pn in the boot process. How > > about simply writing a small shell script call it sysctl.sh and it has > > this command in it. Put it in /usr/local/etc/rc.d and see if it works. > > > > I do not have 5.0 but I hope what i am saying actually makes sense. > > > > Noah. > > > > On Tue, 8 Apr 2003, D.Pageau wrote: > > > -- > Dominic Pageau > > >
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20030409170443.T11815>