On Thu, Mar 08, 2012 at 08:23:16AM -0800, Rob Sherwood wrote: > I've seen a bunch of mail about issues that controller folks > (particularly using nox) have run into when they send packet_out's > with the in_port field being set to OFPP_CONTROLLER instead of > OFPP_NONE. In particular, OVS chooses to reject packet_out's of this > form.
<frustration> Why haven't the NOX maintainers fixed this yet? I've pointed out the problem to any number of people on the mailing lists here. I keep expecting it to go away because NOX fixes it. </frustration> > Now, I completely agree with Ben and everyone's conclusion that the > packet_out *should* use OFPP_NONE in this case, but I'm sitting at the > ONF's interoperability event and this issue is apparently biting a > bunch of the folks here (particularly those with implementations that > derive from OVS). > > I'm wondering if you would be willing to accept a patch to accept both > OFPP_CONTROLLER and OFPP_NONE in this case? It seems like a straight > forward case of being liberal in what you accept. > > Please let me know what you think. If this is something that's > agreeable to you, then I can look into supplying a patch. Yes, I'd be willing to apply such a patch. You state one valid reason. Another one is that OF1.1 switched to OFPP_CONTROLLER for this purpose and OVS is inching toward OF1.1 support. Thanks, Ben. _______________________________________________ discuss mailing list [email protected] http://openvswitch.org/mailman/listinfo/discuss
