On Fri, Dec 20, 2013 at 3:09 PM, Roberto Riggio <roberto.rig...@create-net.org> wrote: > On 12/20/2013 03:02 PM, Helmut Schaa wrote: >> Yep, that was me. I'm using the patch on openwrt since >> some time now and am quite happy. > > I looked at it and I;m not sure if you can define a device > as bridge and add other interfaces to it. At the moment it > seems to me that you define another "type" for the device > insteead I liked brcompt because i could completelly replace > the linux bridge with OVS.
True. However, using the current patch you can just replace a "type bridge" with "type ovs", specifying "option iface eth0 eth1" and you will get an ovs containing eth0 and eth1 as ports. However, if you want to have a more complex port configuration I thought about how to integrate port specific setup. But this is still WIP. >> I've got another similar patch for hostapd. > > What is the purpose of the integration? Letting hostapd automatically add wifi devices to openvswitches when they come up without the need for brcompat. >> I'm using ovs on mips (BE) but only with a local controller and >> haven't noticed any problems yet. >> >> Is your controller running a different architecture then the >> openwrt device? > > I tried all of them :) Pox chokes itself, beacon and floodlight > parse the packet but with the messed up fields (link level > fields are ok, only the network fields are messed up). > > I run the controllers on my laptop (x86). Maybe its worth asking on the ovs list? _______________________________________________ openwrt-devel mailing list openwrt-devel@lists.openwrt.org https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
