From owner-freebsd-isp@FreeBSD.ORG  Thu Apr 10 01:26:13 2003
Return-Path: <owner-freebsd-isp@FreeBSD.ORG>
Delivered-To: freebsd-isp@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id B085237B401
	for <freebsd-isp@freebsd.org>; Thu, 10 Apr 2003 01:26:13 -0700 (PDT)
Received: from ksemat.co.ug (ping.mtn.co.ug [212.88.97.58])
	by mx1.FreeBSD.org (Postfix) with ESMTP id 8021143F3F
	for <freebsd-isp@freebsd.org>; Thu, 10 Apr 2003 01:26:08 -0700 (PDT)
	(envelope-from ksemat@ksemat.co.ug)
Received: from sematin.mtn.co.ug (localhost.mtn.co.ug [127.0.0.1])
	by sematin.mtn.co.ug (8.12.9/8.12.3) with ESMTP id h39EAVik011862;
	Wed, 9 Apr 2003 17:10:33 +0300 (EAT)
	(envelope-from ksemat@ksemat.co.ug)
Received: from localhost (ksemat@localhost)h39EASd0011859;
	Wed, 9 Apr 2003 17:10:31 +0300 (EAT)
X-Authentication-Warning: sematin.mtn.co.ug: ksemat owned process doing -bs
Date: Wed, 9 Apr 2003 17:10:28 +0300 (EAT)
From: Noah K Sematimba <ksemat@ksemat.co.ug>
X-X-Sender: ksemat@sematin.mtn.co.ug
To: "D.Pageau" <dpageau@infodev.ca>
In-Reply-To: <3E942710.9020908@infodev.ca>
Message-ID: <20030409170443.T11815@sematin.mtn.co.ug>
References: <3E92D313.5080108@infodev.ca>
	<20030409131417.A531@sematin.mtn.co.ug> <3E942710.9020908@infodev.ca>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
cc: freebsd-isp@freebsd.org
Subject: Re: Can't bind IP to my bridge at boot time
X-BeenThere: freebsd-isp@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
List-Id: Internet Services Providers <freebsd-isp.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-isp>,
	<mailto:freebsd-isp-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-isp>
List-Post: <mailto:freebsd-isp@freebsd.org>
List-Help: <mailto:freebsd-isp-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-isp>,
	<mailto:freebsd-isp-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Thu, 10 Apr 2003 08:26:14 -0000


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