This is a multi-part message in MIME format.
------=_NextPart_000_001E_01C24099.EE8283E0
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Tim-
I was mistaken in my original statement. Further poking around shows =
that dhcpcd is not receiving anything back from Cox at all. The IP =
address et al.. which I thought were from Cox were cached settings from =
another DHCP
experiment. dhcpcd does not have a verbose option, and returns without =
writing anying to /etc/dhcpc, /etc/dhcpcd, or resolv.conf. I am going =
to do some more reading. If you have any thoughts, I would appreciate =
hearing them.
John.
------=_NextPart_000_001E_01C24099.EE8283E0
Content-Type: text/html;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; =
charset=3Diso-8859-1">
<META content=3D"MSHTML 6.00.2716.2200" name=3DGENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=3D#f0e8d8>
<DIV>Tim-<BR><BR>I was mistaken in my original statement. Further =
poking=20
around shows that dhcpcd is not receiving anything back from Cox at =
all. =20
The IP address et al.. which I thought were from Cox were cached =
settings from=20
another DHCP<BR>experiment. dhcpcd does not have a verbose option, and =
returns=20
without writing anying to /etc/dhcpc, /etc/dhcpcd, or resolv.conf. =
I am=20
going to do some more reading. If you have any thoughts, I would=20
appreciate hearing them.<BR><BR>John.</DIV></BODY></HTML>
------=_NextPart_000_001E_01C24099.EE8283E0--
