Since I upgraded my HP Proliant Server from Ubuntu 10.04 to 12.04, I am unable to:
- ping google.com
- ping 126.96.36.199
- browse the internet with Firefox
- git fetch origin
- cap deploy from a remote machine
I can however see my Rails application running on this server when I access it via its ip address within our corporate network.
I see the Networking icon in the GUI but "Wired Network" is greyed out.
Here is some other relevant info, based on the numerous similar but non-resolving threads I've browsed here at AU:
eth0 Link encap:Ethernet HWaddr 1c:c1:de:fa:cd:9f inet addr:10.24.5.50 Bcast:10.24.5.255 Mask:255.255.255.0 inet6 addr: fe80::1ec1:deff:fefa:cd9f/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:40735 errors:0 dropped:0 overruns:0 frame:0 TX packets:77215 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:2806140 (2.8 MB) TX bytes:113945803 (113.9 MB) Interrupt:19 lo Link encap:Local Loopback inet addr:127.0.0.1 Mask:255.0.0.0 inet6 addr: ::1/128 Scope:Host UP LOOPBACK RUNNING MTU:16436 Metric:1 RX packets:22 errors:0 dropped:0 overruns:0 frame:0 TX packets:22 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:1872 (1.8 KB) TX bytes:1872 (1.8 KB)
dean@dgwjasonfried:~$ lspci -nn | grep Ethernet
1e:00.0 Ethernet controller : Broadcom Corporation NetXtreme BCM5723 Gigabit Ethernet PCIe [14e4:165b] (rev 10)
# This file describes the network interfaces available on your system # and how to activate them. For more information, see interfaces(5). # The loopback network interface auto lo iface lo inet loopback # The primary network interface auto eth0 iface eth0 inet dhcp
domain dgw.ame.molex.com search dgw.ame.molex.com nameserver 10.24.2.171 nameserver 10.45.2.171
**Updated 3/19/13, after trying to follow some of the advice give in responses below and elsewhere:
dean@dgwjasonfried:~$ cat /etc/resolv.conf # Dynamic resolv.conf(5) file for glibc resolver(3) generated by resolvconf(8) # DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES WILL BE OVERWRITTEN nameserver 127.0.0.1 search dgw.ame.molex.com domain dgw.ame.molex.com search dgw.ame.molex.com nameserver 10.24.2.171 nameserver 10.45.2.171
**end of update
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface 0.0.0.0 10.24.5.1 0.0.0.0 UG 0 0 0 eth0 10.24.5.0 0.0.0.0 255.255.255.0 U 1 0 0 eth0 169.254.0.0 0.0.0.0 255.255.0.0 U 1000 0 0 eth0
**Updated to show NetworkManager.conf and evidence that the resolv.conf symlink is working for me
dean@dgwjasonfried:~$ cat /etc/NetworkManager/NetworkManager.conf [main] plugins=ifupdown,keyfile dns=dnsmasq [ifupdown] managed=true dean@dgwjasonfried:~$ ls -l /etc/resolv.conf lrwxrwxrwx 1 root root 29 Mar 18 09:33 /etc/resolv.conf -> ../run/resolvconf/resolv.conf
**Updated to show latest resolv.conf after I deleted original in /etc/resolvconf/resolv.conf.d and cleared out the copy of original that was sitting in tail, then rebooted:
dean@dgwjasonfried:/etc/resolvconf/resolv.conf.d$ cat /etc/resolv.conf # Dynamic resolv.conf(5) file for glibc resolver(3) generated by resolvconf(8) # DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES WILL BE OVERWRITTEN nameserver 127.0.0.1 search dgw.ame.molex.com
Note that the nameserver entries listed in an earlier resolv.conf version above are now gone. Also note that whereas I was briefly able to get ping google.com to resolve the ip address for google.com (but still not receive any packets back) I'm now back to my original situation where I get 'unknown host google.com'.
**end of update
I'd be grateful for any help you could supply or suggestions you might have.