https://bugzilla.novell.com/show_bug.cgi?id=410428
User mt@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=410428#c23
Marius Tomaschewski
OK, the first suggestion worked perfectly. Everything got mounted:
BRIDGE_STP='off' BRIDGE_FORWARDDELAY='0'
With the 2nd suggestion, only 3 of the 5 mounts got mounted.
BRIDGE_STP='on' BRIDGE_MAXAGE='4' BRIDGE_HELLOTIME='1' BRIDGE_FORWARDDELAY='4'
Since the first scenario worked I didn't try the most recent sysconfig packages that you listed, but I can try that if you still need me to.
No, you don't need. I think we can close it, since it is a configuration issue. YaST2 on SLES 11 should set the parameters by default. By default, a bridge is using STP with defaults from IEEE specs and needs someting like 50 secs to find shortests paths and make sure, that there are no loops in the topology. Until the procedure finished, it blocks all traffic, so dhcp client & nfs simply can't work. [See also BRIDGE HOWTO] The 2nd suggestion tweaks the parameters and gives ~12 sec takeover time. Depending on the number of interfaces and dhcp clients (that may do "rfc sleep" for 1..10 sec to "desynchronize" the start) - all together, this may still cause problems. With enabled STP it makes sense to tweak also the DHCLIENT_WAIT_AT_BOOT (how long to wait for IP from dhcp) and WAIT_FOR_INTERFACES (how long to wait for all in the network script interfaces) options. Because of the problems, sysconfig also provides the "man 5 ifservices" mechanizms, allowing you to start/stop services when the interface is ready. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.