devd.conf

[Brooks Davis]

On Fri, Feb 03, 2006 at 10:46:01AM +0000, Phillip Neumann wrote:
> 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 ?

Yes to the first, maybe to the second.  If you aren't using
wpa_supplicant, bringing the interface up should result in it finding a
network if one exists which should trigger a media link up event which
in turn will start dhclient.  Why that isn't working, I couldn't say.

-- Brooks

-- 
Any statement of the form "X is the one, true Y" is FALSE.
PGP fingerprint 655D 519C 26A7 82E7 2529  9BF0 5D8E 8BE9 F238 1AD4
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
Url : http://lists.freebsd.org/pipermail/freebsd-mobile/attachments/20060206/bd47c652/attachment.bin