On 20/05/2011 12:11, "Tóth Attila" wrote: > After a week I think I've sorted out nearly all issues about openrc on my > systems. > Bonding was compiled into the kernel. Upon I tried to echo mode 4 > (802.3ad) to set up the lacp, the system said there's no write access to > the mode file. So the bonding interface remained in round-robin mode. That > was disturbing.
I use compiled in bonding module, openrc, hardened and everything is configured correctly at boot using openrc via sysfs? My working machine uses 2.6.32 + grsec and openrc 0.6.2. I haven't tested variations to this, but note that previous openrc had issues configuring bonds via sysfs? Your error message "no write access", I think is a symptom of wrong ordering of bond creation when using sysfs? Check gentoo bugzilla or openrc bug tracker, there was an open issue against older openrc to fix this (haven't checked it hasn't regressed in later openrc say) My conf.d looks like: # config eth0 config_eth0=( "null" ) config_eth1=( "null" ) config_eth2=( "null" ) config_eth3=( "null" ) # Bonding slaves_bond0="eth0 eth1" mode_bond0="802.3ad" miimon_bond0="100" lacp_rate_bond0="1" config_bond0=( "null" ) slaves_bond1="eth2 eth3" miimon_bond1="100" mode_bond1="balance-rr" config_bond1=( "192.168.2.10/24" ) # config tap0 to bring up bridge tuntap_tap0="tap" config_tap0=( "null" ) bridge_add_tap0="br0" rc_need_tap0="net.br0" # config tap1 to bring up bridge tuntap_tap1="tap" config_tap1=( "null" ) bridge_add_tap1="br0" rc_need_tap1="net.br0" # Config bridge to come up with just eth0 bridge_br0="bond0" # or dynamically add them when the interface comes up #bridge_add_eth0="br0" config_br0=( "1.2.3.4/24" ) routes_br0=( "default via 1.2.3.1" ) # Make the bridge depend on bond0 rc_need_br0="net.bond0" # Below is an example of configuring the bridge brctl_br0=( "stp on" ) Does that help? Ed W
