No default gateway obtained over DHCP

Bug #236099 reported by Obi1Kenobi on 2008-05-30
Affects Status Importance Assigned to Milestone
linux (Ubuntu)

Bug Description

KUbuntu 8.04


I am running KUbuntu 8.04 inside VMWare. Now everything was running smoothly until yesterday when I have applied the latest patches which included a kernel update, if I am not mistaken. I do get an IP address over DHCP but since then I am no longer getting the default gateway. Entering it through System Settings | Network Settings ... makes NO difference. So I added it manually with "route add default gw"... The weird thing is that even after adding it with the afore mentioned command, System Settings | Network Settings still shows a blank text box for "Default Gateway" field. Needless to say, if I reboot the machine it's gone ... have to add it again. The gateway is on the same subnet.

I thought it was my VMWare installation but now it happens to my "normal" installation too also after applying the latest updates.

Again it was working fine until yesterday and it broke after updating the system with latest patches.

Any idea ?

Thanks and regards.

Dereck Wonnacott (dereck) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. Unfortunately we can't fix it, because your description does not yet have enough information.

Please include the following additional information, if you have not already done so (pay attention to lspci's additional options), as required by the Ubuntu Kernel Team:
1. Please include the output of the command "uname -a" in your next response. It should be one, long line of text which includes the exact kernel version you're running, as well as the CPU architecture.
2. Please run the command "dmesg > dmesg.log" after a fresh boot and attach the resulting file "dmesg.log" to this bug report.
3. Please run the command "sudo lspci -vvnn > lspci-vvnn.log" and attach the resulting file "lspci-vvnn.log" to this bug report.

For your reference, the full description of procedures for kernel-related bug reports is available at [WWW] Thanks in advance!

Jonathan Thomas (echidnaman) wrote :

We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to "New". Thanks again!

Changed in linux:
status: Incomplete → Invalid
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers