Question

Arch update breaks network connectivity

I did a pacman -Syu about two weeks ago and rebooted after which I promptly lost my ability to ssh into the droplet. Console access was successful but I was unable to ping 8.8.8.8 (Network is unreachable). Restoring from backup fixed the problem. I can either wait and hope for a future update to fix the problem or I can try downgrading packages one at a time until I figure out what’s causing the problem. But there are 34 packages pacman updated. Among them:

bash-4.3-3 coreutils-8.22-3 cryptsetup-1.6.4-1 device-mapper-2.02.105-2 dhcpcd-6.3.2-1 e2fsprogs-1.42.9-2 file-5.17-2 git-1.9.1-1 glibc-2.19-3 grep-2.18-1 keyutils-1.5.9-1 libarchive-3.1.2-6 libedit-20140213_3.1-1 libnl-3.2.24-1 libseccomp-2.1.1-1 libsystemd-211-1 libtirpc-0.2.4-1 libutil-linux-2.24.1-3 linux-firmware-20140316.dec41bc-1 lvm2-2.02.105-2 man-pages-3.63-1 mkinitcpio-17-1 openssh-6.6p1-1 pkgfile-13-1 ppp-2.4.6-2 python2-2.7.6-3 readline-6.3-3 s-nail-14.6.2-1 sqlite-3.8.4.1-1 sudo-1.8.10.p2-1 systemd-211-1 systemd-sysvcompat-211-1 tzdata-2014a-1 util-linux-2.24.1-3

Has anyone else run into this problem? If not, I could not find this exact issue in google.

Thanks in advance for your guidance. EB


Submit an answer

This textbox defaults to using Markdown to format your answer.

You can type !ref in this text area to quickly search our full set of tutorials, documentation & marketplace offerings and insert the link!

Sign In or Sign Up to Answer

These answers are provided by our Community. If you find them useful, show some love by clicking the heart. If you run into issues leave a comment, or add your own answer to help others.

Want to learn more? Join the DigitalOcean Community!

Join our DigitalOcean community of over a million developers for free! Get help and share knowledge in Q&A, subscribe to topics of interest, and get courses and tools that will help you grow as a developer and scale your project or business.

i had the same problem. <br> <br>after following the arch networking guide: <br> <br>https://wiki.archlinux.org/index.php/Network_configuration#Persistent_configuration_on_boot_using_systemd_and_udev_rules <br> <br>and realizing that my network interface had changed from eth0 to enp0s3, all i had to do was: <br> <br>(within the digitalocean console access) <br> <br># vi /etc/conf.d/netcfg - change ‘eth0’ to ‘enp0s3’ within text <br># mv /etc/conf.d/network@eth0 /etc/conf.d/network@enp0s3 <br># systemctl enable network@enp0s3.service <br># systemctl start network@enp0s3.service <br> <br>and voila, my network came back up.

The upgrade from netcfg to netctl renames the default network device names, so there’s pretty much no way of knowing what the name is AFAIK. The image DO gives is ancient, and it’s pretty difficult to get working. They’ve officially ‘deprecated’ it, what ever that means to them. Quite unfortunate, I wonder if it’s an upstream issue

Thanks for the pointers everyone. I was able to resuscitate my droplet’s network connectivity by doing <br> <br> sudo netcfg -u ethernet-static <br> <br>(Before I did that, I edited /etc/network.d/ethernet-static and replaced all occurences of ‘eth0’ with ‘enp0s3’. I don’t know if that was a required step.) <br> <br>Now I can migrate to netctl directly from the affected droplet.