>Examining the openvswitch opening script I find that it only tries to remove >the module if there are no bridges up. ...to prevent the script from destroying all of your bridges, if you have some configured.
>But what good is brcompatd if there are no bridges up? I think you misunderstand the purpose of brcompatd. It is to allow commands such as "brctl addbr" to control Open vSwitch instead of the Linux bridge module. It is not to allow Open vSwitch to control the Linux bridge module. >Even if there are no bridges up and you fire up a bridge manually, but it >doesn't work due to the bridge module starting by itself? I don't understand that question/statement. >Not being able to remove the bridge module should also be an error that >prevents the brcompatd service from starting as it will do no good to be >started in this way. That's reasonable, and easy to change. I'll send a patch to ovs-dev. >Is there any way to prevent the bridge module from reappearing? I think that modprobe has a "blacklist" feature. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/917309 Title: brcompatd works with brctl delif but doesn't with addif To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openvswitch/+bug/917309/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
