[adding back ovs-discuss]
I do believe that your computer has physical ports. Your enqueue action
isn't using any of them, though, and OpenFlow 1.0 forbids that, with the
wording that I quoted. To make your action acceptable, enqueue to a
physical port.
On Mon, Jul 20, 2015 at 10:42:34AM +0800,
We are very excited to announce that CloudNetEngine vswitch is available for
technical preview!
CloudNetEngine vswitch perfectly bridges the gaps of performance, efficiency and
full feature requirements which existing vswitches simply cannot provide.
CloudNetEngine vswitch is based on some great o
On Sun, Jul 19, 2015 at 11:07:01AM +0800, Huhui wrote:
> In my example I add two flow-table in the event of ConnectionUp.
> The action of flow-table like
> this:of.ofp_action_enqueue(port=of.OFPP_CONTROLLER,queue_id=0).
> When OVS connectted,OpenFlow said that "bad action',and priority queues did
Ok, this means that the packet will be forwarded to the data plane port 2
(not the Open FLow port 2).
Thanks, Abhishek
On Sat, Jul 18, 2015 at 7:57 PM, Abhishek Verma
wrote:
> Hi,
>
> The output of my ovs-appctl dpif/dump-flows BRIDGE shows:
>
>
> skb_priority(0),tunnel(tun_id=0x262,src=152.169
Dear Experts.
Thank you very much for your best efforts to openvswitch.
It is very surprising design and have a lot of functions.
I am studying the source of openvswitch.
It is very hard for me to understand the behavior of functions since a lot of
function call is via function pointer call.
If
