Date: Fri, 03 Feb 2006 10:46:01 +0000 From: Phillip Neumann <pneumann@gmail.com> To: Brooks Davis <brooks@one-eyed-alien.net> Cc: freebsd-mobile@freebsd.org Subject: Re: devd.conf Message-ID: <1138963561.839.1.camel@localhost> In-Reply-To: <20060131012215.GA18380@odin.ac.hmc.edu> References: <1138582561.1895.4.camel@localhost> <20060130211422.GB14402@odin.ac.hmc.edu> <1138662167.1708.2.camel@localhost> <20060131012215.GA18380@odin.ac.hmc.edu>
next in thread | previous in thread | raw e-mail | index | archive | help
sorry for the delay.
El lun, 30-01-2006 a las 17:22 -0800, Brooks Davis escribió:
> On Mon, Jan 30, 2006 at 11:02:47PM +0000, Phillip Neumann wrote:
> > El lun, 30-01-2006 a las 13:14 -0800, Brooks Davis escribió:
> > > On Mon, Jan 30, 2006 at 12:56:01AM +0000, Phillip Neumann wrote:
> > > > Im trying to understand devd.conf.
> > > >
> > > > there is a text, wich is:
> > > > # Try to start dhclient on Ethernet like interfaces when the link comes
> > > > # up. Only devices that are configured to support DHCP will actually
> > > > # run it. No link down rule exists because dhclient automaticly exits
> > > > # when the link goes down.
> > > >
> > > > when i unplug the rj45, i dont see dhclient quitting. i have to ifconfig
> > > > the interface down. only so, dhclient will exit.
> > > >
> > > > base in this, if i modify devd.conf and add this line:
> > > > notify 0 {
> > > > match "system" "IFNET";
> > > > match "type" "LINK_DOWN";
> > > > media-type "ethernet";
> > > > action "/etc/rc.d/dhclient stop $subsystem";
> > > > };
> > > >
> > > > when i unplug the cable it will stop dhclient, but, when i plug the
> > > > cable in again, devd sees 2 events, the LINK_UP and inmedialy it see a
> > > > LINK_DOWN, so dhclient is stopped.
> > >
> > > Your network card's driver has a broken if_media configuration. What
> > > kind of nic is it?
> > >
> >
> > bfe0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1500
> >
> > 02:00.0 Ethernet controller: Broadcom Corporation BCM4401-B0 100Base-TX
> > (rev 02)
> >
> > broken where do you mean?..
>
> If a message isn't being sent when you unplug the cable that's a bug,
> and it's either the driver or the hardware. Most likely the driver,
> particularly in the case of bfe(4) which isn't all that common. I'd
> suggest filing a bug report against the nic driver.
>
ok.
> > > > whats the correct way to configure the ethernet cards?
> > > >
> > > > is there a way to make something similar work to wifi card? i.e. when
> > > > its assisiated with a ssid, run dhclient, and when no carrier, stop it?
> > > >
> > > > i have run devd -dD, but it does not seems to get any event from the
> > > > wifi card. its an intel 2200.
> > >
> > > If your card is running wpa_supplicant, this is exactly what should
> > > happen.
> >
> > well actually not. im just running dhcp. no wpa. at least ive not
> > configured so. and i guess its not enabled by default...
>
> So your ifconfig_<wireless> variable is set to "DHCP" and dhclient isn't
> appearing and disappearing as it should? I'll have to look into that.
> Are you running with the iwi driver? My laptop has one of those so I
> can test it.
>
well it does work. But when i ifconfig iwi0 down, dhclient should quit
right?. and when ifconfig iwi0 up it should run ?
saludos,
> -- Brooks
>
--
Phillip Neumann <pneumann@gmail.com>
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1138963561.839.1.camel>