Anton,
Did you reboot after adding the supersede comand? It does not take effect
until the network is restarted or the system is rebooted. I found a reboot
was easier... In your case the suersede command should be: supersede
nameserver 192.168.0.1 (Do not put quotes around the IP
I think maybe you and Anton have a different problem. I am using a wired
connection and my server never crashed it just did not connect to the
network. The supersede nameserver definately fixed the problem. I tried it
with and without it several times and it always worked with it and never
Anton,
You are 100% correct I apologize. However, I think you may have
discovered something. Below is my original dhclient.conf file. Everything
except the send host-name and the request is commented out. I put the
erroneous supersede command before the send host-name which I think would
Anton,
I don't know if switching the Kernel is a good idea or not. (I would
guess not.) It would be very interesting to check the /var/log/daemon.log
file to see if you have the same before and after differences I found.
(Search the file for the word namerserver.) If you do, you might try
This happened to me when I upgraded a completely patched and working 8.04
installation to 8.10 I had no problem with 8.04 and have installed it on
three different machines. I also installed 8.10 from scratch and had the
same problem. I am using a wired network through a Belkin router to a
Colin,
Thanks for moving it to network-manager. I tried to do that myself a
couple times and couldn't figure out how to do it. This is the first bug I
have logged and I was pretty sure I did it wrong. I will read more
Launchpad documentation before submitting more.
Thanks,
Jerry
-
Public bug reported:
Binary package hint: choose-mirror
I upgraded from 8.04.1 to 8.10 I have an old stupid Belkin firewall
router
This was from /var/log/daemon.log using 8.04.1
Jan 21 10:31:27 JANES-LINUX NetworkManager: info DHCP daemon state is now 4
(reboot) for interface eth0
Jan 21
