On Wed, Mar 30, 2016 at 12:31:27PM -0700, pravin shelar wrote:
> On Wed, Mar 30, 2016 at 10:24 AM, William Tu wrote:
> > Hi Pravin,
> >
> > Thanks for the feedback.
> > So another option is to add an new truncate action, and modify the size for
> > all the following output packets. For example, t
On Wed, Mar 30, 2016 at 10:24 AM, William Tu wrote:
> Hi Pravin,
>
> Thanks for the feedback.
> So another option is to add an new truncate action, and modify the size for
> all the following output packets. For example, the output:1 remains the
> original size and the output:2 and output:3 will
Hi Pravin,
Thanks for the feedback.
So another option is to add an new truncate action, and modify the size for
all the following output packets. For example, the output:1 remains the
original size and the output:2 and output:3 will have size 100.
# ovs-ofctl add-flow br0 'actions=output:1, tru
On Tue, Mar 29, 2016 at 3:16 PM, William Tu wrote:
> Before, OpenFlow specification defines 'max_len' in struct ofp_action_output
> as the max number of bytes to send when port is OFPP_CONTROLLER. A max_len
> of zero means no bytes of the packet should be sent, and max_len of
> OFPCML_NO_BUFFER m
Before, OpenFlow specification defines 'max_len' in struct ofp_action_output
as the max number of bytes to send when port is OFPP_CONTROLLER. A max_len
of zero means no bytes of the packet should be sent, and max_len of
OFPCML_NO_BUFFER means the complete packet is sent to the controller.
It is le