On Wed, 6 Jul 2016 15:12:20 +0900
IWASE Yusuke wrote:
> The following patches enable BGPSpeaker to support Four-Octet AS number
> and include some improvements of BGP.
>
> IWASE Yusuke (4):
> BGPSpeaker: Fix capability check when MP-BGP not supported
> packet/bgp: Support Four-Octet AGGREGA
On Wed, 6 Jul 2016 15:26:32 +0900
IWASE Yusuke wrote:
> For the discussion with Kawai-San and Fujita-San, this patch
> fixes ryu/lib/packet/ethernet.py to fix up the minimum length
> of the generated ethernet frames by Ryu's Packet library.
>
> With this patch, the generated ethernet frames wil
On Wed, 6 Jul 2016 20:01:57 -0700
"Kawai, Hiroaki" wrote:
> To test VLAN_PCP, VLAN_VID must match.
> Table miss test was testing VLAN_VID instead of VLAN_PCP,
> because the packet had mismatching VLAN_VID.
> Fixes to set only OFPVID_PRESENT bit in the match field.
> ---
> ryu/tests/switch/of13/
On Thu, 7 Jul 2016 04:52:50 +
Jason Kölker wrote:
> Signed-off-by: Jason Kölker
> ---
> ryu/lib/ofctl_nicira_ext.py | 9 +++--
> 1 file changed, 3 insertions(+), 6 deletions(-)
Sorry about the trouble. As discussed on the different thread, the API
change should be reverted soon. Pleas
On Mon, 11 Jul 2016 17:13:52 +0900
Shinpei Muraoka wrote:
> Hi Fujita-San
>
>> You mean that after I apply
>>
>> [PATCH v2 0/8] Support some NXAction
>>
>> then you send a patch to revert
>>
>> commit 3c3896fd77f274ce953dcb78795aa5cc4fde6c65
>> Author: Shinpei Muraoka
>> Date: Mon Jun 6 09:48
Hi,
AFAIK, OpenFlow 1.3 does not provide match fields for identifying the
sequential ICMPv4 packets.
The match fields related to ICMPv4 packets are:
OFPXMT_OFB_ICMPV4_TYPE = 19, /* ICMP type. */
OFPXMT_OFB_ICMPV4_CODE = 20, /* ICMP code. */
If you want to do the different actions for each
Shinpei MuraokaThank you
its apply for my environment
Wisam Maala
On Monday, July 11, 2016 11:05 AM, Shinpei Muraoka
wrote:
Hi,
> but the problem is still
> and I modification the file of (simple_switch_stp_13.py) you can the
> error in attachment
> and I attachment the fil
Hi Fujita-San
> You mean that after I apply
>
> [PATCH v2 0/8] Support some NXAction
>
> then you send a patch to revert
>
> commit 3c3896fd77f274ce953dcb78795aa5cc4fde6c65
> Author: Shinpei Muraoka
> Date: Mon Jun 6 09:48:12 2016 +0900
>
> ofproto/nx_actions: Update arguments t
On Mon, 11 Jul 2016 11:49:16 +0900
Shinpei Muraoka wrote:
> Hi Fujita-San
>
>> We should have really good reason to break the API compatibility with
>> the older versions. I don't think that this is the case.
>>
>> Seems that better to revert this. Can we cleanly revert this? Any
>> other side e
