Cox now insists on DHCP protocol

[tim cutler]

I think I got it with the simple fix below. I did the following:

. Added DHCP_HOSTNAME="CX-..." per instruction to
   /etc/sysconfig/network-scripts/ifcg-eth0

. Via netcfg GUI (blech), changed eth0 to have dhcp protocol.
   Netcfg (or somebody) complained that the operation failed. I ignored 
its complaint. Felt the regular amount of danger.

. Did a "service network restart".
   Twice, since I'm blind and the white cane must be banged around 
repeatedly to detect reality.

All seemed to work. The IP address of eth0 stayed the same. There's a 
dhcpcd daemon running in that background. Only time, with a few reboots 
and power cycles, will tell.

Thanks all for your help and interest.

	T

Carl Parrish wrote:

> 
>>
>> I recently got this same piece of email from @home and adding the
>> DHCP_HOSTNAME line fixed it so that it was dhcp'd properly.  Then I
>> went and read the man page on how to use non @home nameservers  :-)
>>
>> I hope it makes them happy...my IP hasn't changed.  :-)
>>
>> FWIW, they claimed there was "work going on in my neighborhood"; I'm
>> curious if they spammed all of cox@home, or just the fortunate few in
>> the Mesa area.
>>
>> David
> 
> 
> Well I got it (haven't changed over yet). But then I'm in mesa to.
> 
> Carl P.
> 
> ________________________________________________
> See http://PLUG.phoenix.az.us/navigator-mail.shtml if your mail doesn't 
> post to the list quickly and you use Netscape to write mail.
> 
> PLUG-discuss mailing list  -  PLUG-discuss@lists.PLUG.phoenix.az.us
> http://lists.PLUG.phoenix.az.us/mailman/listinfo/plug-discuss
>