[systemd-devel] systemd-networkd and bonding config

[Ian Pilcher]

On 03/04/2015 03:43 AM, Tom Gundersen wrote:
> The logic here is that when we create a new bond we will create it
> with these settings, but we will not change the settings of a
> preexisting bond, as that may have been created by somebody else we
> don't know about so we figure better leave it alone.
>
> The confusing part here is that the kernel will create bond0 with
> default settings, and we will then not touch that. Ideally there would
> be a kernel config switch to make it not create default devices like
> that, but for the moment I think the best solution is to simply call
> your bond something else. So if you put bond1 everywhere instead
> things should JustWork(TM).

Alternatively, if you're attached to the name bond0, you might be able
to something like this (not tested with systemd-networkd):

/etc/modprobe.d/rename-bond.conf:

install bonding /usr/sbin/modprobe --ignore-install bonding \
	$CMDLINE_OPTS; /usr/sbin/ip link set dev bond0 down; \
	/usr/sbin/ifrename -c /dev/null -i bond0 -n FOO	>/dev/null

(Or an equivalent udev rule)

-- 
========================================================================
Ian Pilcher                                         arequipeno at gmail.com
-------- "I grew up before Mark Zuckerberg invented friendship" --------
========================================================================