On Wed, Feb 28, 2018 at 03:01:24PM -0800, William Tu wrote:
> On Wed, Feb 28, 2018 at 2:14 PM, Ben Pfaff wrote:
> > On Mon, Feb 26, 2018 at 01:43:39PM -0800, William Tu wrote:
> >> On Wed, Feb 14, 2018 at 3:03 PM, Ben Pfaff wrote:
> >> > On Wed, Feb 14, 2018 at
On Mon, Feb 26, 2018 at 01:43:39PM -0800, William Tu wrote:
> On Wed, Feb 14, 2018 at 3:03 PM, Ben Pfaff wrote:
> > On Wed, Feb 14, 2018 at 10:56:08AM -0800, William Tu wrote:
> >> Usually ofproto/trace is used to debug the flow translation error.
> >> When translation error such as
On Wed, Feb 14, 2018 at 3:03 PM, Ben Pfaff wrote:
> On Wed, Feb 14, 2018 at 10:56:08AM -0800, William Tu wrote:
>> Usually ofproto/trace is used to debug the flow translation error.
>> When translation error such as recursion too deep or too many resubmit,
>> the issue might happen
On Wed, Feb 14, 2018 at 10:56:08AM -0800, William Tu wrote:
> Usually ofproto/trace is used to debug the flow translation error.
> When translation error such as recursion too deep or too many resubmit,
> the issue might happen momentary; flows causing the recursion expire
> when users try to
Usually ofproto/trace is used to debug the flow translation error.
When translation error such as recursion too deep or too many resubmit,
the issue might happen momentary; flows causing the recursion expire
when users try to debug it. This patch enables the ofproto trace
automatically when