Date: Mon, 30 Jan 2006 17:22:15 -0800 From: Brooks Davis <brooks@one-eyed-alien.net> To: Phillip Neumann <pneumann@gmail.com> Cc: freebsd-mobile@freebsd.org Subject: Re: devd.conf Message-ID: <20060131012215.GA18380@odin.ac.hmc.edu> In-Reply-To: <1138662167.1708.2.camel@localhost> References: <1138582561.1895.4.camel@localhost> <20060130211422.GB14402@odin.ac.hmc.edu> <1138662167.1708.2.camel@localhost>
next in thread | previous in thread | raw e-mail | index | archive | help
--3MwIy2ne0vdjdPXF
Content-Type: text/plain; charset=iso-8859-1
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable
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=F3:
> > On Mon, Jan 30, 2006 at 12:56:01AM +0000, Phillip Neumann wrote:
> > > Im trying to understand devd.conf.
> > >=20
> > > there is a text, wich is:
> > > # Try to start dhclient on Ethernet like interfaces when the link com=
es
> > > # 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.
> > >=20
> > > when i unplug the rj45, i dont see dhclient quitting. i have to ifcon=
fig
> > > the interface down. only so, dhclient will exit.=20
> > >=20
> > > 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";
> > > };
> > >=20
> > > 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.
> >=20
> > Your network card's driver has a broken if_media configuration. What
> > kind of nic is it?
> >=20
>=20
> bfe0: flags=3D8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1500
>=20
> 02:00.0 Ethernet controller: Broadcom Corporation BCM4401-B0 100Base-TX
> (rev 02)
>=20
> broken where do you mean?..=20
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.
> > > whats the correct way to configure the ethernet cards?
> > >=20
> > > 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 i=
t?
> > >=20
> > > i have run devd -dD, but it does not seems to get any event from the
> > > wifi card. its an intel 2200.
> >=20
> > If your card is running wpa_supplicant, this is exactly what should
> > happen.
>=20
> 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.
-- Brooks
--=20
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
--3MwIy2ne0vdjdPXF
Content-Type: application/pgp-signature
Content-Disposition: inline
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.1 (GNU/Linux)
iD8DBQFD3rvGXY6L6fI4GtQRAvbbAKDgWF0TXcpJku56Y3gS8USmsllqOgCg5BnW
aIP0zaO1EM5nARExMgh/1O4=
=pDb7
-----END PGP SIGNATURE-----
--3MwIy2ne0vdjdPXF--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20060131012215.GA18380>