Activity log for bug #177767

Date Who What changed Old value New value Message
2007-12-20 22:17:01 tpkuester bug added bug
2007-12-20 22:21:29 tpkuester description From a fresh install of 7.10 server (x86)... Selected to Configure network later. Selected LAMP, OpenSSH, Samba for optional software. Booted--no issuses. Edited /etc/network/interfaces to contain --- auto eth0 iface eth0 inet static address 192.168.1.50 netmask 255.255.255.0 gateway 192.168.1.1 --- ran /etc/init.d/networking restart to cycle the interfaces. eth0 came up and appeared to be configured correctly. Pinged google.com, no response. Pinged 192.168.1.1 -- received a response. Used dhclient for DHCP services to make sure I didn't configure something incorrectly, and it said something about /etc/resolv.conf -- which I don't remember. I pinged google.com again, with no success. ls /etc | grep resolv # apparently, /etc/resolv.conf didn't exist touch /etc/resolv.conf # lets make it dhclient eth0 Now I can ping google.com and other various sites. This seems like a bug to me. Did I do something wrong? From a fresh install of 7.10 server (x86)... Selected to Configure network later. Selected LAMP, OpenSSH, Samba for optional software. Booted--no issuses. Edited /etc/network/interfaces to contain --- auto eth0 iface eth0 inet static address 192.168.1.50 netmask 255.255.255.0 gateway 192.168.1.1 --- ran /etc/init.d/networking restart to cycle the interfaces. eth0 came up and appeared to be configured correctly. Pinged google.com, no response. Pinged 192.168.1.1 -- received a response. Used dhclient for DHCP services to make sure I didn't configure something incorrectly, and it said something about /etc/resolv.conf -- which I don't remember. I pinged google.com again, with no success. ls /etc | grep resolv # apparently, /etc/resolv.conf didn't exist touch /etc/resolv.conf # lets make it dhclient eth0 Now I can ping google.com and other various sites. Update: It was also noted here with Dapper Drake http://ubuntuforums.org/archive/index.php/t-282042.html Reading that article, I can assure that the cause was a missing resolv.conf file -- not a firewall or any other issues.
2008-11-20 00:14:03 Daniel T Chen resolvconf: status New Confirmed
2008-11-20 00:14:03 Daniel T Chen resolvconf: importance Undecided Wishlist
2010-03-26 21:26:38 Simon Huerlimann resolvconf (Ubuntu): status Confirmed Invalid