22 Nov
2018
22 Nov
'18
12:03 p.m.
/etc/NetworkManager/:
total 20
drwxr-xr-x 3 root root 4096 Nov 2 2017 .
drwxr-xr-x 108 root root 12288 Nov 22 07:11 ..
drwxr-xr-x 2 root root 4096 Mar 10 2018 dispatcher.d
/etc/systemd/network/:
total 12
drwxr-xr-x 2 root root 4096 Nov 2 2017 .
drwxr-xr-x 5 root root 4096 Nov 3 11:00 ..
-rw-r--r-- 1 root root 382 Nov 2 2017 99-default.link
/lib/systemd/network/:
total 24
drwxr-xr-x 2 root root 4096 Nov 3 11:00 .
drwxr-xr-x 8 root root 4096 Nov 3 11:00 ..
-rw-r--r-- 1 root root 605 Oct 28 17:02 80-container-host0.network
-rw-r--r-- 1 root root 678 Oct 28 17:02 80-container-ve.network
-rw-r--r-- 1 root root 664 Oct 28 17:02 80-container-vz.network
-rw-r--r-- 1 root root 80 Oct 28 17:02 99-default.link
On Thu, 22 Nov 2018 at 17:14, Andy Smith <andy(a)bitfolk.com> wrote:
Hi Keith,
On Thu, Nov 22, 2018 at 12:53:14PM +0800, Keith Williams wrote:
Discovered that in a previous edition I had left
out the auto eth0 line
so
obviously ifupdown was not reading it. ipv4 was
obviously coming from
hobgoblin somehow
I think it will be either systemd-networkd or NetworkManager
managing an interface that isn't claimed by ifupdown (because of the
mistake in the /etc/network/interfaces). It would be interesting to
know which. What is the output of:
$ ls -la /*/systemd/network/ /etc/NetworkManager/
?
There is no DHCP at BitFolk so network interfaces do need some sort
of configuration inside each VPS in order to be set up.
Cheers,
Andy
--
https://bitfolk.com/ -- No-nonsense VPS hosting
_______________________________________________
users mailing list
users(a)lists.bitfolk.com
https://lists.bitfolk.com/mailman/listinfo/users