[ovs-discuss] OVS Ports not Available at Boot Time

Nick Couchman Nick.Couchman at seakr.com
Wed Sep 8 20:29:13 UTC 2010


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.

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?

Thanks,
Nick



--------
This e-mail may contain confidential and privileged material for the sole use of the intended recipient.  If this email is not intended for you, or you are not responsible for the delivery of this message to the intended recipient, please note that this message may contain SEAKR Engineering (SEAKR) Privileged/Proprietary Information.  In such a case, you are strictly prohibited from downloading, photocopying, distributing or otherwise using this message, its contents or attachments in any way.  If you have received this message in error, please notify us immediately by replying to this e-mail and delete the message from your mailbox.  Information contained in this message that does not relate to the business of SEAKR is neither endorsed by nor attributable to SEAKR.




More information about the discuss mailing list