I sent out an implementation:
http://openvswitch.org/pipermail/dev/2015-November/061811.html
http://openvswitch.org/pipermail/dev/2015-November/061812.html
Please consider testing and reviewing it.
(But it's hard for me to believe that this is genuinely useful.)
Thanks,
Ben.
On
Hi,
On 2015年10月26日 13:51, Ben Pfaff wrote:
> It seems that this is a missing feature.
OK, I understood.
I am waiting for this feature to be implemented.
thanks,
>
> On Mon, Oct 26, 2015 at 01:21:55PM +0900, Minoru TAKAHASHI wrote:
>> Hi Ben,
>>
>> Thank you for your reply!
>>
>> On 2015年10月25日
Hi Ben,
Thank you for your reply!
On 2015年10月25日 05:18, Ben Pfaff wrote:
> On Fri, Oct 23, 2015 at 11:54:02AM +0900, Minoru TAKAHASHI wrote:
>> Hi,
>>
>> I send QueueGetConfig message(*OFPP_ANY* was set to port) to
>> OVS(openflow1.3),
>> then the following errors occured.
>>
>> Version: 1.3 (0
It seems that this is a missing feature.
On Mon, Oct 26, 2015 at 01:21:55PM +0900, Minoru TAKAHASHI wrote:
> Hi Ben,
>
> Thank you for your reply!
>
> On 2015年10月25日 05:18, Ben Pfaff wrote:
> > On Fri, Oct 23, 2015 at 11:54:02AM +0900, Minoru TAKAHASHI wrote:
> >> Hi,
> >>
> >> I send QueueGetCo
On Fri, Oct 23, 2015 at 11:54:02AM +0900, Minoru TAKAHASHI wrote:
> Hi,
>
> I send QueueGetConfig message(*OFPP_ANY* was set to port) to OVS(openflow1.3),
> then the following errors occured.
>
> Version: 1.3 (0x04)
> Type: OFPET_QUEUE_OP_FAILED (9)
> Code: OFPQOFC_BAD_PORT (0)
>
> Is this a
Hi,
I send QueueGetConfig message(*OFPP_ANY* was set to port) to OVS(openflow1.3),
then the following errors occured.
Version: 1.3 (0x04)
Type: OFPET_QUEUE_OP_FAILED (9)
Code: OFPQOFC_BAD_PORT (0)
Is this a bug?
___
discuss mailing list
discuss@open
