Upgraded my server's software from Ubuntu 12.04 to Ubuntu 14.04 and now the server cannot access the internet.

I can ping devices on my LAN, including my modem. When I try to ping any site on the internet ( for example), I get 100% packet loss. I feel like this may be a DNS issue from what I've been reading. I've added the following line to /etc/network/interfaces :


with no success.

Relevant outupt of ifconfig :

eth0     Link encap:Ethernet  HWaddr 64:31:50:1f:88:72
          inet addr:  Bcast:  Mask:
          inet6 addr: fe80::6631:50ff:fe1f:8872/64 Scope:Link
          RX packets:575229 errors:0 dropped:55 overruns:0 frame:0
          TX packets:10313 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          RX bytes:35490659 (35.4 MB)  TX bytes:898607 (898.6 KB)

output of route -n:

Kernel IP routing table
Destination     Gateway         Genmask         Flags Metric Ref    Use Iface         UG    0      0        0 eth0   U     0      0        0 eth0

Content of /etc/network/interfaces file :

auto lo
iface lo inet loopback

auto eth0
iface eth0 inet static


output of tracepath :

1?: [LOCALHOST]                                         pmtu 1500
1:                                           0.446ms
1:                                           0.444ms
2:  no reply`  
3:  no reply`    
//continues with no reply until interrupted
  • 2
    If you can't ping external hosts even by numeric IP (such as then it is more than a DNS issue. Can you add the result of route -n to your post please? – steeldriver Aug 15 '14 at 17:56
  • 2
    What is Is it a router or the address of your modem? (It must be a router to work but may be a modem with an operating integrated router). Another idea: Might there be another device using – John S Gruber Aug 15 '14 at 18:49
  • 2
    In your position I'd do several things. First I'd try to ping the address of the ISP router your router talks to. Second I'd do the same tests from another device on your network. Third, if the other device works and your new OS fails I'd double check the working devices IP related confiration with the non-working one. It's easy to miss a single character. You don't need DNS to work to ping IP addresses. – John S Gruber Aug 15 '14 at 19:11
  • 1
    Are any other devices on your LAN able to ping anything external? And is your internet connection actually up? – Joe Sniderman Aug 22 '14 at 3:32
  • 1
    @JoeSniderman all other devices on LAN are able to ping externally. Internet connection is working fine on all other devices. – user259743 Aug 22 '14 at 3:42

Looks like an unusual one this...

Firstly I sincerely doubt that DNS is involved, though if you are using et al for your DNS then DNS will fail because you can't reach those servers.

Firstly it can't be your LAN configuration because you can ping your local gateway, so traffic to and from it works.

The biggest hint is the double listing of your gateway in the trace. Your gateway should only be shown once, and this hints at a loop at your gateway - but all your other systems work fine, and according to what you write, it's only the local system that changed.

The only thing that I can remotely think of is if you had an iptables rule roughly like this:

iptables -t nat -D POSTROUTING ! -d -j SNAT --to-source

Where is some bogus or possibly previously valid IP address that no longer works.

This would let local traffic work but anything going out beyond the local network would break because replies would go to the wrong place. Your gateway may block traffic like that because it is in essence 'spoofed' traffic.

I think you would get a good hint to the issue with some traffic inspection at your gateway if it is at all possible.

If you can't do that - quite understandable - then maybe set up another Linux box on your network and make it the default gateway for this faulty system, and then you can inspect the traffic it is generating. This is assuming that the fault is on the upgraded system. If you configured that 2nd Linux box to ip_forward and make it's gateway the device you might also see more useful info to help nail down the cause.

Will be interesting to see what it was when you finally get it sorted.

  • the double listing of the gateway is common on the use of home routers as its "routing" between the switch and the "external interface" lol. I have the same results at my own place. Although you are right on discarding gateway issues if other devices can communicate ok, and server can ping gateway... this is pretty strange as you say.. – Manco1911 Oct 12 '14 at 2:15

Try to go into "/etc/resolv.conf" and below the lines starting with #'s add these lines: "nameserver" "nameserver" See if you can connect after doing this. Do not reboot after changing the file, just save it and test your connection. If this works then it was a DNS problem. The changes made to the file will be undone after a reboot.


I had exactly the same situation - no internet connection, no ping to outside, no ping from router to the box. But a working SSH connection from another workstation in the same LAN. The cause was the router who was blocking the new box as it had the same IP as the replaced old box, but a different MAC address. As soon as I changed the IP everything worked.

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.