Subject: dhclient vs. a preexisting default route - PR#22418
To: None <tech-userlevel@NetBSD.org>
From: Jeff Rizzo <riz@NetBSD.org>
List: tech-userlevel
Date: 10/06/2006 21:46:17
This is an OpenPGP/MIME signed message (RFC 2440 and 3156)
--------------enig06D87F49E54B4E831EC0F709
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
PR#22418 details a problem with dhclient not properly switching default
routes if one already exists; the original submitter had a problem when
he got a short-lived DHCP address on one rfc1918 network, followed by a
longer lease with a public address, dhclient wouldn't properly set up
the default.
Arnaud Lacombe has appended a patch which fixes the issue, but the fix
brings up a couple of questions for me, so I wanted to garner opinions
before changing it.
- do we want a DHCP-supplied default route to override? Most of the
time it's desireable, but I could see an argument against it.
- if DHCP overrides, is it OK to implicitly change the behavior from
"first router is chosen" to "last router is chosen"?
+j
--------------enig06D87F49E54B4E831EC0F709
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (Darwin)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iQCVAwUBRScxHbOuUtxCgar5AQMvgwP9HWI5Ldgib79q8n1eecvWusmCh12o2SIN
nROHIiouaw1LjPI3mdZfwB02yxZr6z4kAEs8kAzzwMZPQ5aan0SZgsmIye67ikzY
nRcCQsL3B/i0cHxY0AfhC9/CgnSlB4SvPbYXH+q67t8M161RV7YCIAxvz+Ky9Wq8
AigQ6Yi27lU=
=HnfN
-----END PGP SIGNATURE-----
--------------enig06D87F49E54B4E831EC0F709--