8.2-PRERELESE ifconfig_bridge has no members unless run from rc.local

John Baldwin jhb at freebsd.org
Wed Dec 8 18:29:30 UTC 2010


On Wednesday, December 08, 2010 11:29:49 am Kim Culhan wrote:
> On Wed, Dec 8, 2010 at 9:23 AM, John Baldwin <jhb at freebsd.org> wrote:
> 
> >  On Tuesday, December 07, 2010 5:17:30 pm Kim Culhan wrote:
> > > Had been running a wireless bridge for some months in rc.conf:
> > >
> > > ifconfig_bridge0="addm wlan0 addm re1 up"
> > >
> > > Updated to 8.2-PRERELEASE 2 days ago and when the machine boots
> > > the bridge has no members.
> > >
> > > Reversing the order of the members results in the bridge having just
> > > the re1 member.
> > >
> > > Running the above command from a shell works and running from
> > > an rc.local file also works.
> > >
> > > FWIW, running from a shell there is about a 3 second delay after hit
> > enter
> > > before it returns the shell prompt, members are then present.
> > >
> > > The lines in rc.conf:
> > >
> > > cloned_interfaces="bridge0"
> > > ifconfig_wlan0="inet 192.168.1.50/24 channel 11"
> > > wlans_rum0="wlan0"
> > > create_args_wlan0="wlanmode hostap mode 11g"
> > > ifconfig_bridge0="addm wlan0 addm re1 up"
> > >
> > > Tried replacing the re device with em, no change.
> > >
> > > Any help is very greatly appreciated.
> >
> > Most likely the bridge0 device is created by /etc/rc.d/netif before the
> > wlan0
> > device is created, so when the system startup tries to configure bridge0,
> > the
> > ifconfig statement fails.
> >
> > What does 'ifconfig -l' show after you have booted?
> >
> It shows:
> 
> re0 em0 plip0 lo0 bridge0
> 
> On the console at boot there is, after the file partition status and setting
> the hostname:
> ifconfig: BRDGADD wlan0: No such file or directory
> 
> Following this is:
> 
> Starting Network: lo0 re0 em0 bridge0
> 
> Which is followed by output the same as from ifconfig -a including bridge0
> which
> has no members.
> 
> Next is:
> 
> Starting Network: rum0
> rum0: flags=8843<UP, BROADCAST  etc

Hmm, I wonder why rum0 shows up so late.  Do you not plug it in until after
boot, or does it depend on devd loading firmware into the device, etc.?

-- 
John Baldwin


More information about the freebsd-net mailing list