Hi Mike, I doubt that Henry is running keepalived. But… As far as I understand it the problem with keepalived is that systemd-networkd (and thus netplan) want to be in control of the interface configuration and so conflict with what keepalived is trying to do. Here is some more information about that: https://lists.ubuntu.com/archives/ubuntu-server/2018-October/007765.html If the above is true, then this problem is not restricted to Ubuntu but applies to any system that tries to move addresses about (e.g, keepalived) and also uses systemd-networkd. I would not at this time recommend systemd-networkd for servers, so it is important that some previous method of configuration (e.g. ifupdown) is known to work… Cheers, Andy On Tue, Nov 13, 2018 at 08:33:22AM +0000, Mike Zanker wrote: -- https://bitfolk.com/ -- No-nonsense VPS hosting

Hello, On Tue, Nov 13, 2018 at 12:07:58PM +0000, Ian Hobson wrote: To be clear I'm not saying "don't use Ubuntu 18.04", I'm saying "don't use systemd-networkd on servers (of any kind) (yet)". I don't think we will make any progress on this without someone replicating the problem, making a bug report against ifupdown on Launchpad, and pushing it along. 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. Cheers, Andy -- https://bitfolk.com/ -- No-nonsense VPS hosting

Hi Andreas, On Tue, Nov 13, 2018 at 05:02:25PM +0100, Andreas Olsson wrote: 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 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

Hello, On Tue, Nov 13, 2018 at 06:17:26PM +0100, Andreas Olsson wrote: The main IPv4 settings are passed on the kernel command line for these self-installs, as both Debian/Ubuntu installer and CentOS support that. For Debian/Ubuntu, a late pressed script writes an /etc/network/interfaces file that will contain the main IPv4 address, all additional IPv4 addresses, and the main IPv6. As it seems /etc/network/interfaces is being ignored by netplan, I think either the script will need to write a better netplan config or else the installer should force ifupdown. Which do you think should happen? Thanks, that's helpful. Would certainly not be difficult to construct that sort of thing. I have seen various ways to force choice of source address. Some people say to add the address last, others say to add it as a /128 and then it will always be chosen, and others say to add it as a deprecated address (preferred_lft 0) then it will never be chosen as a source address unless forced. So, personally I prefer the preferred_lft 0 method which in /etc/network/interfaces file looks like: iface eth0 inet6 static address 2001:ba8:1f1:f019::2 netmask 64 gateway 2001:ba8:1f1:f019::1 post-up /bin/ip -6 addr add 2001:ba8:1f1:f019::80/64 dev $IFACE preferred_lft 0 I will have to look up how to do it with netplan. Cheers, Andy -- https://bitfolk.com/ -- No-nonsense VPS hosting

On 13/11/2018 17:17, Andreas Olsson wrote: That's great, thank you. I haven't had time to go back and sort this for the last week, but it sounds like we have the solution! Cheers, Henry

Hi Keith, On Thu, Nov 22, 2018 at 09:24:14AM +0800, Keith Williams wrote: So it doesn't have a global IPv6 address? That would definitely cause IPv6 to not work. I don't think so, but if the package "netplan" is not installed then it's definitely not involved. What is a thing however, is systemd-networkd. But that should leave alone any interface that is defined in /etc/network/interfaces. Do you have a file called /run/network/ifstate? If so, the interfaces listed in it were configured by ifupdown as per /etc/network/interfaces. Which VPS is misbehaving with regard to IPv6? I will check there is nothing amiss on BitFOlk's side. Has it ever worked for IPv6? Cheers, Andy -- https://bitfolk.com/ -- No-nonsense VPS hosting

~# ifup --force -a RTNETLINK answers: File exists ifup: failed to bring up eth0 Xen shutdown then boot # cat /run/network/ifstate lo=lo eth0=eth0 I just rewrote the interfaces file. Well copied and pasted from other VPS then changed the relevant addresses. Then did Xen shutdown and booted it again, to ensure config files were re read. 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 Sorry, and thanks On Thu, 22 Nov 2018 at 12:21, Keith Williams <keithwilliamsnp(a)gmail.com> wrote:

Hi Keith, On Thu, Nov 22, 2018 at 12:53:14PM +0800, Keith Williams wrote: 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

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: -- https://bitfolk.com/ -- No-nonsense VPS hosting