[ Date Index ] [ Thread Index ] [ <= Previous by date / thread ] [ Next by date / thread => ]
On 08/05/17 15:29, Julian Hall wrote: > I'm confused why eth0 isn't listed.. is that due to the method I used to > set it up? > > This is the content of my current /etc/network/interfaces Ah ha, now we approach the heart of the matter. Mint has really done a number on you during an upgrade as it transitions towards a fully systemd managed init. Mint is particularly bad at handling the transition gracefully unfortunately so you now have a system with some remnants of the old init system coexisting entirely inharmoniously with systemd which *really* wants to take over everything itself. No wonder stuff has been going wrong. You are correct that your /etc/network/interfaces file is being completely ignored by the system at the moment, which is to be expected: you'd have to specifically disable certain system services (remnants of old init) *and* whichever systemd unitfiles are currently handling the network before Cerce will fall back to the most basic configuration of honouring the static configuration file. You could modify the interfaces file now but without disabling these conflicting services not only will it fail, but you'll quite probably end up with multiple network configs and IPs simultaneously! The enp*s* naming convention is standard now I'm afraid - without manual intervention, Linux has been renaming network interfaces from the old ethX convention for literally years. Check to see what Cerce is doing with your network names with: dmesg | egrep "eth|enp0" And whilst we're at it, let's have a look at things from the systemd side, which is where ultimately we're going to have to end up doing the config anyway: systemctl status network* Cheers -- The Mailing List for the Devon & Cornwall LUG https://mailman.dclug.org.uk/listinfo/list FAQ: http://www.dcglug.org.uk/listfaq