Re: [Ryu-devel] OFPOxmId in Table Features Request

2017-04-04 Thread Iwase Yusuke
Hi Bill Thank you for your report! On 2017年04月05日 12:20, William Fisher wrote: > When an OXM id is serialized in a table features request, the OXM > header that is serialized sets the oxm_length to 0. That is, the OXM > id for "eth_dst" is sent as > > 8600 instead of 8606 (the last byt

[Ryu-devel] OFPOxmId in Table Features Request

2017-04-04 Thread William Fisher
When an OXM id is serialized in a table features request, the OXM header that is serialized sets the oxm_length to 0. That is, the OXM id for "eth_dst" is sent as 8600 instead of 8606 (the last byte is the length of the value). There's a comment in the code that explains the issue was un

[Ryu-devel] 4.13 released

2017-04-04 Thread FUJITA Tomonori
Hi, Here's a new release; enjoy! = FUJITA Tomonori (1): Ryu 4.13 Satoshi Fujimoto (5): ofctl: Fix type of fields of DescStat ofctl_rest: Add get role API ofctl_v1_5: Fix lack of arguments for modify role API bgp/peer: Fix invalid NEXT_HOP in UPDATE message bgp