On Wed, Sep 8, 2010 at 1:29 PM, Nick Couchman <[email protected]> wrote: > I'm having trouble configuring the OVS startup sequence correctly such that > ports are available when the Linux network subsystem attempts to start. I'm > running OpenSuSE 11.3 and OpenvSwitch 1.1.0pre1. The ovsdb-server, > ovs-vswitchd, and ovs-brcompatd daemons start correctly at boot time. I > currently have them starting before Linux attempts to start network devices, > as I was under the impression this would allow all of the devices to be > created successfully. However, this does not seem to be the case - although > these daemons start correctly, the interfaces (br0, my bridge, and dom0.0, an > internal interface I created) are not available when Linux tries to bring up > interfaces. If I shut down all of the daemons and restart them, the > interfaces show up correctly.
Sounds like you have a timing issue, probably introduced by the bridge compatibility layer. What happens if you add a sleep() as a debugging measure? Is it possible to avoid using bridge compatibility and directly use the Open vSwitch tools? > > I've also noticed another problem. When eth0 is added to br0 (not via Linux > bridging, but via open vSwitch) it does not seem to operate in promiscuous > mode. This is problematic for internal interface that I've created, as > packets going back to that interface (right now, DHCP responses) don't get > put through. Any hints on how to solve this one? Open vSwitch puts the interfaces into promiscuous mode, so I somewhat doubt that this is the problem. My guess is that something is dropping the traffic for another reason. ovs-dpctl dump-flows <brname> is a good tool for seeing what Open vSwitch is doing (it shows the currently active flows from the last 5 seconds). Of course tcpdump is useful as well and checking that there are no iptables rules that might cause problems, etc. _______________________________________________ discuss mailing list [email protected] http://openvswitch.org/mailman/listinfo/discuss_openvswitch.org
