We are actually using it in a somewhat unconventional way (at least in OpenWRT). I work at Skytap and we use OpenWRT (and have been for almost four years) as a micro virtual machine for gateway services to our customer's VMs. One of our features requires us to support a large number of dynamically allocated port forwarders. We are using OpenvSwitch as a policy routing engine in our distribution plane to distribute the traffic to the gateway instances that do the actual NAT (we used to use netfilter + ip rule + virtual route tables, but that has significant performance issues in the control plane at scale). The distribution router is a one-armed router and runs a proprietary policy routing protocol. The protocol daemon manages interface up/down events as well as adding/removing necessary flows for the policy routing, so we aren't using netifd.
On Mon, Nov 11, 2013 at 12:12 AM, Helmut Schaa <[email protected]>wrote: > Hi, > > On Fri, Nov 8, 2013 at 11:42 PM, Pete Holland <[email protected]> > wrote: > > This is a patch for the most recent stable build of OpenvSwitch (2.0.0). > It > > supports kernels 2.6.32 - 3.10.x > > > > It was taken and updated from Julius Shulz-Zander's work: > > https://github.com/schuza/openvswitch > > Nice, I've been playing around with openvswitch as well. > However, I'm still at 1.9.x due to the brcompat module :/ > > What scripts are you using for setting ovs up? Not netifd I guess? > > Helmut > _______________________________________________ > openwrt-devel mailing list > [email protected] > https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel >
_______________________________________________ openwrt-devel mailing list [email protected] https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
