23 Nov
2018
23 Nov
'18
2:01 p.m.
Thanks for all the time you spent on this, Andy. I have no idea, but then I
wouldn't expect to. I guess we just have to put it down to some sort of
fluky one-off, or something weird that I had done at sometime
Keith
On Fri, 23 Nov 2018 at 20:13, Andy Smith <andy(a)bitfolk.com> wrote:
Hi Keith,
Well, unless there is anything interesting in
/etc/systemd/network/99-default.link, I am stumped as to how it
managed to get a working IPv4 configuration when ifupdown wasn't
managing eth0.
Cheers,
Andy
On Thu, Nov 22, 2018 at 08:03:08PM +0800, Keith Williams wrote:
/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
--
https://bitfolk.com/ -- No-nonsense VPS hosting
_______________________________________________
users mailing list
users(a)lists.bitfolk.com
https://lists.bitfolk.com/mailman/listinfo/users