Red Hat Bugzilla – Bug 62855
Using neat to configure eth0 via dhcp puts PEERDNS=no into ifcfg-eth0, which is BAD!
Last modified: 2008-05-01 11:38:01 EDT
From Bugzilla Helper:
User-Agent: Mozilla/4.79 [en] (X11; U; Linux 2.4.18-0.13 i686)
Description of problem:
Configuring an ethernet device using redhat-config-network and selecting 'dhcp'
a line 'PEERDNS=no' into the corresponding
file. This is especially bad, since it stops pump (or dhcpcd) from generating a
/etc/resolv.conf file based on the information received from the DHCP server.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
2.Configure ethernet device using dhcp
Actual Results: The generated file contains named line, while it shouldn't.
Expected Results: No such line should be generated, at least not until the user
is able to choose himself, if /etc/resolv.conf should be generated or not, ie.
PEERDNS=no|yes should be emitted.
This is bad for mostly laptop users who are connecting to different DHCP
While the first boot after an installation will most likely succeed, any further
using a *different* DHCP server will fail, because it's unlikely that the
whose address had been emitted into /etc/resolv.conf during the first boot, is
already fixed in CVS. Wait for 0.9.23.
*** Bug 62946 has been marked as a duplicate of this bug. ***
Is this stil a problem with version 0.9.24 at http://people.redhat.com/teg/neat/ ?
Works perfectly now!