Hi! I use Mininet and Ryu Controller to test Open Flow protocol 1.3.
Now I want create a web app to see the Open Flow's traffic in Virtual Machine
between H1 and H2. How do I do? I want utilize REst API but when I'm starting
Ryu Controller (ryu-manager ryu.app.simple_switch_13 ryu.app.ofctl_rest
Hi,
I am trying to use mininet to test my fast failover app.
(with Openflow 1.3, Open vSwitch 2.6.1)
My testing topology is shown as follow.
/ 2 \ / 5 \
h1 - 1 4 7 - h2
\ 3 / \ 6 /
It is fine when I using mininet to pingall.
(The path is *s1-s2-s4-s5-s7*)
But if I
hi, Fujimoto
is there any conflict between OpenFlow 1.0 and OpenFlow 1.3?
you know, as you said, i use the code in my controller:
from ryu.ofproto import ofproto_v1_0_parser
class SimpleSwitch13(app_manager.RyuApp):
OFP_VERSIONS = [ofproto_v1_3.OFP_VERSION]
def __init__(self, *args,
Hi Yamamoto-San,
On Wed, 12 Jul 2017 23:43:25 +0900
Takashi YAMAMOTO wrote:
> this breaks openstack neutron_dynamic_routing, doesn't it?
I thank for advice. I know that.
So as soon as the ryu version with this commit is released,
I am going to push a patch to fix a breake to neutron-dynamic-rou
CC'ed Iwase,
On Thu, 13 Jul 2017 09:15:25 +0900
Takashi YAMAMOTO wrote:
> On Thu, Jul 13, 2017 at 7:04 AM, fumihiko kakuma
> wrote:
>
>> Hi Yamamoto-San,
>>
>> On Wed, 12 Jul 2017 23:43:25 +0900
>> Takashi YAMAMOTO wrote:
>>
>> > this breaks openstack neutron_dynamic_routing, doesn't it?
>>
>
Hi,
On 2017年07月13日 09:13, FUJITA Tomonori wrote:
CC'ed Iwase,
On Thu, 13 Jul 2017 09:15:25 +0900
Takashi YAMAMOTO wrote:
On Thu, Jul 13, 2017 at 7:04 AM, fumihiko kakuma
wrote:
Hi Yamamoto-San,
On Wed, 12 Jul 2017 23:43:25 +0900
Takashi YAMAMOTO wrote:
this breaks openstack neutron_d
On Thu, 13 Jul 2017 09:15:25 +0900
Takashi YAMAMOTO wrote:
> On Thu, Jul 13, 2017 at 7:04 AM, fumihiko kakuma
> wrote:
>
> > Hi Yamamoto-San,
> >
> > On Wed, 12 Jul 2017 23:43:25 +0900
> > Takashi YAMAMOTO wrote:
> >
> > > this breaks openstack neutron_dynamic_routing, doesn't it?
> >
> > I th
On Thu, 13 Jul 2017 09:44:30 +0900
Iwase Yusuke wrote:
> Hi,
>
>
> On 2017年07月13日 09:13, FUJITA Tomonori wrote:
>> CC'ed Iwase,
>> On Thu, 13 Jul 2017 09:15:25 +0900
>> Takashi YAMAMOTO wrote:
>>
>>> On Thu, Jul 13, 2017 at 7:04 AM, fumihiko kakuma
>>>
>>> wrote:
>>>
Hi Yamamoto-San,
>>
Hi, Mehran
is there any conflict between OpenFlow 1.0 and OpenFlow 1.3?
Sorry, I didn't make it clear enough.
"NXTSetControllerId" is not a OpenFlow action, is a Nicira Extension action.
But in Ryu, this action is provided for only OpenFlow 1.0.
In this solution, we "hack" to use this action in
On 2017年07月13日 09:52, FUJITA Tomonori wrote:
On Thu, 13 Jul 2017 09:44:30 +0900
Iwase Yusuke wrote:
Hi,
On 2017年07月13日 09:13, FUJITA Tomonori wrote:
CC'ed Iwase,
On Thu, 13 Jul 2017 09:15:25 +0900
Takashi YAMAMOTO wrote:
On Thu, Jul 13, 2017 at 7:04 AM, fumihiko kakuma
wrote:
Hi Yam
Hi!
I think fast-failover in s1 was succeeded.
But, for the packet from h2 to h1,
s4 may send it to s2, because s4 cannot notice the link between s1 and
s2 is down.
So, the packet from h2 to h1 is dropped in s2, and ping failed.
To avoid this, how about you have a link between s2 and s3?
And p
Dear Fujimoto,
I think the problem you mentioned occurred in my app indeed.
I will try to change my app or the topology to deal with this situation.
Thanks for your help, again.
I truly appreciate it.
Rex.
2017-07-13 10:21 GMT+08:00 Fujimoto Satoshi :
> Hi!
>
> I think fast-failover in s1 was
On Thu, 13 Jul 2017 13:15:46 +0900
Takashi YAMAMOTO wrote:
> On Thu, Jul 13, 2017 at 10:00 AM, fumihiko kakuma
> wrote:
>
> > On Thu, 13 Jul 2017 09:15:25 +0900
> > Takashi YAMAMOTO wrote:
> >
> > > On Thu, Jul 13, 2017 at 7:04 AM, fumihiko kakuma
> > > wrote:
> > >
> > > > Hi Yamamoto-San,
Hi
We are working on a research project that involves HP OpenFlow enabled
switch (HP 3500 yl). We are facing some issues with performance
particularly when operating the switch in "OpenFlow" mode. The switch is
controlled via a desktop running the Ryu controller.
The rules on the switch match pa
14 matches
Mail list logo
