Re: [systemd-devel] systemd-networkd and bonding config

2015-03-05 Thread Mikhail Morfikov
You can use options bonding max_bonds=0 to disable the creation of bond0. That's exactly what I needed: # cat /proc/net/bonding/bond0 Ethernet Channel Bonding Driver: v3.7.1 (April 27, 2011) Bonding Mode: load balancing (round-robin) MII Status: up MII Polling Interval (ms): 1000 Up Delay

Re: [systemd-devel] systemd-networkd and bonding config

2015-03-05 Thread Susant Sahani
On Thu, 05 Mar 2015 21:01:53 +0530, Michał Bartoszkiewicz mbartoszkiew...@gmail.com wrote: On Thu, Mar 5, 2015 at 3:47 PM, Tom Gundersen t...@jklm.no wrote: The kernel creates bond0 itself. This is confusing and we should probably request the kernel to stop doing that (patch needed). You

Re: [systemd-devel] systemd-networkd and bonding config

2015-03-05 Thread Ian Pilcher
On 03/05/2015 09:31 AM, Michał Bartoszkiewicz wrote: You can use options bonding max_bonds=0 to disable the creation of bond0. Now there's a poorly documented (and named) module parameter! -- Ian Pilcher

Re: [systemd-devel] systemd-networkd and bonding config

2015-03-05 Thread Michał Bartoszkiewicz
On Thu, Mar 5, 2015 at 3:47 PM, Tom Gundersen t...@jklm.no wrote: The kernel creates bond0 itself. This is confusing and we should probably request the kernel to stop doing that (patch needed). You can use options bonding max_bonds=0 to disable the creation of bond0. -- Michał Bartoszkiewicz

Re: [systemd-devel] systemd-networkd and bonding config

2015-03-05 Thread Tom Gundersen
On Thu, Mar 5, 2015 at 5:27 AM, Mikhail Morfikov mmorfi...@gmail.com 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

Re: [systemd-devel] systemd-networkd and bonding config

2015-03-04 Thread 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.

Re: [systemd-devel] systemd-networkd and bonding config

2015-03-04 Thread Mikhail Morfikov
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; \

Re: [systemd-devel] systemd-networkd and bonding config

2015-03-04 Thread Mikhail Morfikov
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

Re: [systemd-devel] systemd-networkd and bonding config

2015-03-04 Thread Tom Gundersen
Hi Mikhail, On Sat, Feb 28, 2015 at 1:26 PM, Mikhail Morfikov mmorfi...@gmail.com wrote: I've just finished migration from /etc/init.d/networking script to systemd-networkd solution, and I just wanted to ask a couple of things. First, I have two interfaces -- one wire (eth1) and one wifi

[systemd-devel] systemd-networkd and bonding config

2015-02-28 Thread Mikhail Morfikov
I've just finished migration from /etc/init.d/networking script to systemd-networkd solution, and I just wanted to ask a couple of things. First, I have two interfaces -- one wire (eth1) and one wifi (wlan0), and I want them to be bonded into one bond0 interface. I had that solution when I was