Hey ben thanks again for the help. Just hoping to run my current understanding of brcompat through you. Please let me know if this incorrect.
ovs-brcompat and brcompat.ko are both only responsible for allowing the use of linux brctl/bridge-utility tools to work with openvswitch. If the system I am working on had previously not used any bridging or bridge-utilities then these items should not be necessary correct? The bridging can be handled completely by openvswitch and connecting the existing network interfaces into an ovs bridge's virtual ports. Do you know of any references for this level of stuff (so I dont have to continue pestering you), probably the kernel and ovs kernel module? Thanks again for the help, it is greatly appreciated. Chris On Wed, Jun 26, 2013 at 10:45 AM, Ben Pfaff <b...@nicira.com> wrote: > On Wed, Jun 26, 2013 at 10:18:31AM -0700, Cali Ente wrote: > > Ok so openvswitch starts up fine. Everything seems good until I add the > > virtual bridge (Log output at the bottom). 'ovs-vsctl show' still > displays > > the bridge I created and I can add ports to it. However it does not show > up > > under ifconfig. I am guessing "2000-02-05T21:48:08Z|00007| > > dpif|WARN|failed to create datapath ovs-system: Message too long" is the > > problem. Does this have to do with the openvswitch kernel module > > communicating with the linux network stack? > > Yes. The problem could be in userspace or on the kernel side. You > might want to hex-dump the messages being sent to the kernel and > verify that they look sensible. >
_______________________________________________ discuss mailing list discuss@openvswitch.org http://openvswitch.org/mailman/listinfo/discuss
