On Wed, Apr 11, 2018 at 08:14:07PM -0400, Flavio Fernandes wrote:
>
>
> > On Apr 7, 2018, at 1:53 PM, Ben Pfaff wrote:
> >
> > On Fri, Apr 06, 2018 at 04:18:31PM -0400, Flavio Fernandes wrote:
> >> Dear OVS Gurus:
> >>
> >> I came across something simple and silly, which is making me think it
> On Apr 7, 2018, at 1:53 PM, Ben Pfaff wrote:
>
> On Fri, Apr 06, 2018 at 04:18:31PM -0400, Flavio Fernandes wrote:
>> Dear OVS Gurus:
>>
>> I came across something simple and silly, which is making me think it is
>> actually a bug.
>>
>> In a nutshell, I'm trying to use a literal with the
On Fri, Apr 06, 2018 at 04:18:31PM -0400, Flavio Fernandes wrote:
> Dear OVS Gurus:
>
> I came across something simple and silly, which is making me think it is
> actually a bug.
>
> In a nutshell, I'm trying to use a literal with the action output nested in a
> learn().
> If I use a fancier (a
Dear OVS Gurus:
I came across something simple and silly, which is making me think it is
actually a bug.
In a nutshell, I'm trying to use a literal with the action output nested in a
learn().
If I use a fancier (and more common) notation:
output:NXM_OF_IN_PORT[]
that works fine. However, i
The binary encoding of the "learn" action just doesn't support an
"output to immediate" action, so some kind of different approach is
needed.
On Fri, Apr 06, 2018 at 05:57:14PM -0400, Flavio Fernandes wrote:
>
> Heh, after sending that msg, I did a little digging in the code [1] and doc
> and it
Heh, after sending that msg, I did a little digging in the code [1] and doc and
it seems clear that
integer literals are just not supported as a value for the output action name.
I imagine that in order to handle that, that code section would need to be
extended to perform
a "parse_int_string(v
