On Mon, 24 Feb 2014 17:18:29 -0800
vinay pai wrote:
> Thank you so much for the response. That helped alot. One other small issue
> is that Im trying to match on TCP source port for IPv6. The match
> parameters I give is TCP source port = 2000+protocol=6(for
> TCP)+ethertype=0x86DD(for IPv6). How
Hi Fujita,
Thank you so much for the response. That helped alot. One other small issue
is that Im trying to match on TCP source port for IPv6. The match
parameters I give is TCP source port = 2000+protocol=6(for
TCP)+ethertype=0x86DD(for IPv6). However the controller reports an error
when it tries
On Mon, 17 Feb 2014 12:31:51 -0800
vinay pai wrote:
> What I am trying to achieve is incrementally pass flow with the combination
> of matches. For Example, I first pass a flow with match on ethertype, next
> with match on ethertype and source MAC, then with match on ethertype,
> source MAC and d
Hi Fujita,
Thank you so much for the response.
What I am trying to achieve is incrementally pass flow with the combination
of matches. For Example, I first pass a flow with match on ethertype, next
with match on ethertype and source MAC, then with match on ethertype,
source MAC and destination MA
On Thu, 13 Feb 2014 17:15:44 -0800
vinay pai wrote:
> mod = parser.OFPFlowMod(datapath=datapath, priority=priority,
> match = match, instructions=inst)
You can specify table number as table_id argument here like.
mod = parser.OFPFlowMod(datapath=datapath, table_i
Hi Fujita,
Few more details are: The flow programs fine in L2 mode of the switch
because there is only 1 table. However we are suspecting that always table
0 goes out because of which the L3 mode of the switch is rejecting the flow.
Regards,
Vinay Pai B.H.
On Thu, Feb 13, 2014 at 5:15 PM, vina
Hi Fujita,
Thanks for the response.
I wanted to know if we can specify the table number on the switch side when
we are trying to install the flow? The switch architecture is different
compared to traditional Openflow switches. We have a L2 mode where we can
install only L2 flows and L3 mode where
On Wed, 12 Feb 2014 20:06:16 -0800
vinay pai wrote:
> I have another small query. When I pass the flow onto my switch I see the
> error on my switch as follows:
>
> Debug: |1|00705|connmgr|INFO|sw1<->tcp:172.28.243.51:6633%management:
> sending OFPBRC_EPERM error reply to OFPT_FLOW_MOD message
>
Hi Fujita,
Thank you so much for your response! It worked perfectly with that change!
I have another small query. When I pass the flow onto my switch I see the
error on my switch as follows:
Debug: |1|00705|connmgr|INFO|sw1<->tcp:172.28.243.51:6633%management:
sending OFPBRC_EPERM error reply to
On Wed, 12 Feb 2014 14:49:02 -0800
vinay pai wrote:
> class SwitchEventApp(app_manager.RyuApp):
> _CONTEXTS = {
> 'switches': switches.Switches,
> }
>
> @set_ev_cls(EventSwitchEnter)
> def _ev_switch_enter_handler(self, ev):
> print('enter: %s' % ev)
> datapath = ev.msg.datap
Hi Satoshi,
Thank you so much for the response.
My end goal is to pass a flow to the switch as soon as its up using OFv1.3.
I have written the following snippet of code but Im not sure where I am
going wrong. I would be obliged if you could help me out in this regard.
from ryu.base import app_ma
Hi Vinay,
You can use EventSwitchEnter and EventSwitchLeave.
(Note that this API is supported only by OpenFlow 1.0 and 1.3)
--
from ryu.base import app_manager
from ryu.controller.handler import set_ev_cls
from ryu.topology import switches
from ryu.topology.event import EventSwitchEnter,
Hi All,
I am traditionally a POX user and am more familiar with the APIs used
there. I have recently started using Ryu and am finding difficulty in
finding the appropriate APIs. In POX there is an API which is called when a
switch connects to the controller. It is _handle_ConnectionUp(). I am
sear
13 matches
Mail list logo
