13 Nov
2018
13 Nov
'18
5 p.m.
Hi Andreas,
On Tue, Nov 13, 2018 at 05:02:25PM +0100, Andreas Olsson wrote:
tis 2018-11-13 klockan 14:27 +0000 skrev Andy Smith:
Hmm, there is no DHCP server at BitFolk so either:
1. netplan has limited understanding of /etc/network/interfaces, or
2. netplan writes a default config file based on its network
settings in the installer phase, and ignores
/etc/network/interfaces totally
...
All I can say is that we've provisioned plenty of new Ubuntu 18.04
VPSes using /etc/network/interfaces and ifupdown and haven't heard
of any problems.
For my Bitfolk Ubuntu 18.04 netinstall /etc/network/interfaces either
wasn't read at all, or only partially read. Without being able to go
back and double check I think that the file wasn't read at all, and
that the VPS got basic IPv4 by way of DHCP. No matter what I had to create a custom netplan config
to get IPv6
working, as well as getting multiple IPv4 addresses setup. At least
that is the way I remember it.
I just did a self-install of Ubuntu 18.04 and to my surprise it has
ended up without the ifupdown package and *with* netplan. It does
seem to reliably configure its main IP address and default route,
but indeed it has not configured IPv6.
I see there is a /etc/netplan/01-netcfg.yaml :
--------------------------------------------------------------------------------
# This file describes the network interfaces available on your system
# For more information, see netplan(5).
network:
version: 2
renderer: networkd
ethernets:
eth0:
addresses: [ 85.119.82.225/21 ]
gateway4: 85.119.80.1
nameservers:
search: [ vps.bitfolk.com ]
addresses:
- "85.119.80.232"
--------------------------------------------------------------------------------
I think it has taken these from the network settings of the
installer, and not bothered with IPv6, so that is scenario (2) from
above.
Should I:
a) Make sure the self-install for Ubuntu 18.04 and beyond works with netplan and IPv6, or
b) Make the self-install for Ubuntu 18.04 and beyond default to
ifupdown? (I believe this can be done by preseeding
"netcfg/do_not_use_netplan=true")
I am unsure which way to go. On the one hand:
- netplan seems to have some deficiencies as highlighted by the keepalived thing
but on the other hand:
- those setups are going to be quite rare (fairly sure the only
person running keepalived at BitFolk is me)
- netplan is the official way in Ubuntu now so won't it be confusing
if it does not arrive out of the box configured with netplan?
I have added this as a bug here:
https://tools.bitfolk.com/redmine/issues/172
If you have any opinion as to which way I should go in fixing it, a
comment there would be appreciated (your usual BitFolk credentials to
log in).
It's depressing that there's not a single IPv6 example in
https://netplan.io/examples
Cheers,
Andy
--
https://bitfolk.com/ -- No-nonsense VPS hosting