Hi Henry,
On Fri, Nov 09, 2018 at 08:03:54PM +0000, Andy Smith wrote:
On Fri, Nov 09, 2018 at 06:27:28PM +0000, Henry
Gomersall wrote:
> I agree, I'm going to back off and try to clobber everything with
> sensible configs.
Just going back to this, now I realise that people were right and
netplan does take over if it's installed, we should check what is
configuring your network.
Is there a /run/network/ifstate file present? If so then ifupdown
has been called.
Is there anything in /etc/netplan/ ? If so then netplan may have
done something. The contents of those files would be interesting.
Also if you run:
$ sudo netplan --debug generate --mapping eth0
you should get back something like:
DEBUG:command generate: running ['/lib/netplan/generate', '--mapping',
'eth0']
** (generate:11022): DEBUG: 08:39:59.523: Processing input file
//etc/netplan/01-netcfg.yaml..
** (generate:11022): DEBUG: 08:39:59.523: starting new processing pass
** (generate:11022): DEBUG: 08:39:59.523: eth0: setting default backend to 1
id=eth0, backend=networkd, set_name=(null), match_name=eth0, match_mac=(null),
match_driver=(null)
which shows that netplan is in charge of eth0, using systemd-networkd as a
backend, and the config is coming from /etc/netplan/01-netcfg.yaml.
You can then decide whether to:
- continue with the new Ubuntu way of doing things which is netplan,
in which case I recommend deleting /etc/network/interfaces and
uninstalling ifupdown if it exists as a package as it will be
confusing, or
- revert back to ifupdown in which case you need to write a correct
/etc/network/interfaces and uninstall netplan package.
Cheers,
Andy
--
https://bitfolk.com/ -- No-nonsense VPS hosting