networking

When your Debian server throws network issues, especially after a restart, it can bring operations to a halt. A common error that many administrators face, after commands ifup eth0 or /etc/init.d/networking restart  is:

failed to open statefile /var/run/ network/ifstate: No such file or directory

This issue, while common, can be quite vexing as it directly affects the server's connectivity. But there's hope! I've grappled with this error and have found the way out. Here's a detailed guide to restoring your network and putting this problem behind you.

Setting up a network in Ubuntu is not a tricky business, but for beginners it can be difficult, today I'll show you how to configure the network on a freshly installed Ubuntu.

I've collide here with an incomprehensible situation in Ubuntu, if you turn on the bridge for KVM, if you get an IPv6 address, this IPv6 hangs fast, about once every 5-10 minutes, when the interface is restarted, everything starts to work for 5-10 minutes, then hangs again. In this case, IPv4 continues to work. Routes like IPv6 and IPv4 remain. Because of what many resources stop working, google, yandex, update the application database (apt-get update). In general, all that can work on IPv6 safely stops working when the bridge hangs. In the logs, there are no errors, where to dig is not clear. It is exactly known that this is happening on Ubuntu 15.10, at 14.04 it works like a clock.

In short, I was tired of restarting the network interface every 10 minutes, and I decided to just disable IPv6.