Date: Thu, 1 Sep 2005 18:52:42 -0700 From: Brooks Davis <brooks@one-eyed-alien.net> To: Jochen Gensch <incmc@gmx.de> Cc: freebsd-current@freebsd.org Subject: Re: freebsd-current Digest, Vol 112, Issue 11 Message-ID: <20050902015242.GJ4108@odin.ac.hmc.edu> In-Reply-To: <200509020126.45337.incmc@gmx.de> References: <20050901225346.0923E16A41F@hub.freebsd.org> <200509020126.45337.incmc@gmx.de>
next in thread | previous in thread | raw e-mail | index | archive | help
--BOmey7/79ja+7F5w
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable
On Fri, Sep 02, 2005 at 01:26:45AM +0200, Jochen Gensch wrote:
> Am Freitag 02 September 2005 00:53 schrieb=20
>=20
> > Right now, we refuse to modify the default route if another interface
> > has it, but the expected behavior is probably to modify it even if it's
> > on another interface if that interface is down.
>=20
> Something else: does that mean, once a non removable nic got the default =
route=20
> it cannot be changed again? At least it seems like I'm experiencing that =
here=20
> (Even though I tried so many different ways now, that I'm not too sure ab=
out=20
> that any more, lol).
No. Just that dhclient won't do it.
> > If the start_if.ath0 script isn't running, you should check that you ha=
ve
> > removable_interfaces=3D"ath0" in rc.conf. Though, I saw some traffic t=
hat
> > say this was going away.
> >
> > Anyway, quoting Brooks in "HEADSUP: OpenBSD dhclient incoming"
> > "Second the pccard_ifconfig variable is only used as a default value for
> > interfaces that are on the removable_interfaces list, but do not have an
> > ifconfig_<if> variable. Third, interfaces must be on the
> > removable_interfaces list for pccard_ether to work."
>=20
> Yes, rc.conf looks as follows:
> --------------------------------
> background_dhclient=3D"YES"
> ifconfig_fxp0=3D"DHCP"
> ifconfig_ath0=3D"WPA DHCP"
> removable_interfaces=3D"ath0"
>=20
> However, as I'm not too familiar with things like "pccard_ifconfig variab=
le"=20
> it is difficult to follow you szenario. But it seems, that start_if.ath0=
=20
> shouldn't run since ath0 has an ifconfig_ath0 entry here for wpa_supplica=
nt.
>
> > There should not be a need to modify devd.conf as there is already this
> > line:
> >
> > attach 0 {
> > device-name "$ethernet-nic-regex";
> > action "/etc/pccard_ether $device-name start";
> > }
>=20
> Yep, I saw that right after your first reply.
>=20
>=20
> > I also saw some traffic from Brooks where he explicitly stated that
> > the new dhclient does not touch the default route if one is already
> > configured. afaik, this should not actually be a problem because start=
_if
> > is always run before dhclient has a change to start. Also I agree, it
> > would rather dangerous if dhclient just started flushing the routing
> > table.
>=20
> But it needs to be configurable somewhere. As I understand it now I canno=
t use=20
> start_if.ath0 since it has a (mandatory) ifconfig_if entry in rc.conf rel=
ated=20
> to wpa_supplicant. Therefore one needs to hack it in somewhere by hand.
This is not the issue. I have no idea where you got the idea that
having an ifconfig_<ifn> entry has anyting to do with start_if.ath0
running. The issue is that start_if.ath0 always runs at boot or when
you insert the card, but not when you get a lease. If you want to take
an action when you get a lease, you need to do it in the dhclient hooks.
-- 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
--BOmey7/79ja+7F5w
Content-Type: application/pgp-signature
Content-Disposition: inline
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.1 (GNU/Linux)
iD8DBQFDF7BpXY6L6fI4GtQRAnR6AJ0djNg8obt2yenRlxC00STo3x7u2wCgoc4g
AWQjgQBVJC4INee/mqKH+zk=
=H/67
-----END PGP SIGNATURE-----
--BOmey7/79ja+7F5w--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20050902015242.GJ4108>