0

I am running a remote server a VPS, all was well,

Upgraded to Ubuntu 16.04 and immediately my ssh (putty) stopped allowing me access, it just can't find server, cannot ping... it says

network unreachable

Checked all firewalls and all exactly same as before,

All firewalls open on correct ports, all software runs correctly on reboot, its all working except I cannot connect to server by any means, I cannot SSH,

When running service networking status I get the following error report,

networking failure error report

It is failing to raise networking services and so I cannot access server, it also lists dhclient failure,

My Hosting provider provides a terminal interface so I can run commands luckily,

Please help as I have tried ALL articles on net for this including here and no luck, I now have a server which is working fine except neither I or anyone else can ever contact it,

The contents of my /etc/network/interfaces file are correct,

Loopback interface
auto lo eth0
iface lo inet loopback

Primary Network Interface
auto eth0
iface eth0 inet dhcp

please advise as I am not willing to start from scratch with server and don't know why Ubuntu has not fixed this ongoing bug which many people have reported,

Hope you can help?

edwinksl
  • 23,789
Thomas Branley
  • 1
  • Hi,

    I ran ifconfig results below, then changed /etc/network/interfaces file, firstly to docker0 then to veth1367b5d to try raising them,

    and ran ifup and ifdown exactly as you suggested for each one in turn to test them:

    Test results and error message

    docker is a container running for my discourse forum, and two other Ethernet listed, I tried docker and then one of ethernets but neither produced anything but errors and would not raised network services,

    any help would be appreciated

    thank you

     – Thomas Branley Aug 20 '16 at 05:23

1 Answers1

4

In 16.04, because of persistent naming, your interface is probably no longer eth0. Check:

ifconfig

For example, my ethernet interface is now enp0s25. Correct your /etc/network/interfaces file as needed and then:

sudo ifdown enp0s25 && sudo ifup enp0s25

Of course, substitue your interface name as needed.

Why is enp#s# in stead of eth# ? Whats the meaning of enp#s#?

Community
  • 1
chili555
  • 60,188
  • 1
    chili, +1, but i think it's time to start telling people to use ip as a must :) – heemayl Aug 19 '16 at 19:38
  • 1
    @heemayl Old dogs and new tricks, etc.! – chili555 Aug 19 '16 at 19:40
  • Thank you will report back, appreciate you taking time to help! – Thomas Branley Aug 19 '16 at 22:13
  • I have added result of following the suggested steps above, still no luck getting it working, won't raise network service... – Thomas Branley Aug 19 '16 at 22:37
  • Hi, I ran ifconfig results below, then changed /etc/network/interfaces file, firstly to docker0 then to veth1367b5d to try raising them,

    and ran ifup and ifdown exactly as you suggested for each one in turn to test them:

    Results of your instructions

    docker is a container running for my discourse forum, and two other Ethernet listed, I tried docker0 and then one of ethernets but neither produced anything but errors (see image above) and would not raise network services,

    any help would be appreciated thank you

     – Thomas Branley Aug 20 '16 at 05:56
  • I have also found the following /run/network/ifstate has deleted any mention of Ethernet ,

    problems with ifstate

    On checking this file only lo=lo is in it, suspect that once I identify what Ethernet I should have running will go in this file eg. enp#s# etc

     – Thomas Branley Aug 20 '16 at 09:06
  • I have now run ip addr command and it shows that eth0 is present with an ipv6 address but not UP, so question is how to I get /etc/network/interfaces to recognize eth0 and how do I raise it to state UP successfully?

    result of ip addr

     – Thomas Branley Aug 20 '16 at 09:26
  • I am very sorry. I do not know anything at all about Docker. – chili555 Aug 20 '16 at 12:20
  • thanks its not docker its saying cannot raise eth0 – Thomas Branley Aug 22 '16 at 21:12
  • If an Ubuntu forum can't solve something that lots of people seem to be having problems with (a systemic problem with Ubuntu) there is no chance for the average user to be able to use Ubuntu, I think I will have to go back to Centos as Ubuntu has trashed my server – Thomas Branley Aug 22 '16 at 21:16
  • see link

    https://www.google.co.uk/search?q=cannot+raise+eth0+ubuntu+16+networking+service&ie=&oe=

    will raise it as formal bug on SO and Git

     – Thomas Branley Aug 22 '16 at 21:26