> Problems:
> the red hat scripts move the file /etc/dhcpc/resolv.conf to
> /etc/resolve.conf this means that the file get's overwritten so any
> modifications to the origional will be lost.
Right. Don't ever put the `master' copies of information in
/etc/resolv.conf when you're using dhclient.
> I mannaged this by editing the file: /etc/sysconfig/network-scripts/
>
> ifdhcpc-done: echo "nameserver 204.174.64.1" >> /etc/resolv.conf
> ifdhcpc-done: echo "nameserver 204.174.65.1" >> /etc/resolv.conf
Ouch! Why not just put something like the following in your
/etc/dhclient.conf?
supersede domain-name-servers 127.0.0.1;
supersede domain-name "mydomain.com";
And just a warning in advance: some versions of dhclient will
attempt to configure all interfaces, even if you only ask them to
configure one. This can play hell with your LAN, if you're using
your machine as a router doing NAT. I added the following to the
top of /etc/dhclient-script:
if ! grep -q $interface /etc/dhclient.interfaces; then
exit 1;
fi
and then I put just the name of the interface I wanted configured
into /etc/dhclient.interfaces. This causes all other interfaces to
fail the PREINIT.
> Another thing. For some reason dhcp only worked 1/10 times until I
> installed the packegs: bootp, and dhcpserver. Don't ask me why but
> it seems to work fine now. Again I'm too busy to figure out why it works.
I've never had this problem, but I've heard from some people that
they won't get connectivity to the outside world until they
authenticate with bconnect's authentication server (ssm.bconnect.net)
or have a ping directed to their address from the outside.
BTW, can you please keep your lines around 70 chars? Taking them
straight out to 80 means that they wrap as soon as someone quotes
them.
cjs
Curt Sampson cjs@portal.ca Info at http://www.portal.ca/
Internet Portal Services, Inc. Through infinite mist, software reverberates
Vancouver, BC (604) 257-9400 In code possess'd of invisible folly.