Hi Mahdieh,
NXM fields in Ryu are defined as the following.
http://ryu.readthedocs.io/en/latest/nicira_ext_ref.html#module-ryu.ofproto.nicira_ext
For "NXM_OF_IN_PORT", you can use "in_port_nxm", I guess.
Thanks,
Iwase
On 2017年06月28日 18:28, Mahdieh Shariat wrote:
Hi Iwase,
Thank you for you
Hi Iwase,
Thank you for your reply.
I tried this code:
>> actions = [
parser.NXActionRegLoad(ofs_nbits=nicira_ext.ofs_nbits(4, 31),
dst="NXM_OF_IN_PORT[]", value=0x0),
parser.OFPActionOutput(_port)]
but in ryu console i get exception as this:
>> File
"/home/mahdie/.local/lib/python2.7/s
Hi Mahdieh,
Excuse me for jumping in.
On 2017年06月24日 03:16, Mahdieh Shariat wrote:
Hi, Fujimoto
Thank you very much for the prompt reply. It works.
But I have another problem in developing my app. In my app when I'm installing rules on tables, I
have a rule for two situations in a switch:
Hi, Fujimoto
Thank you very much for the prompt reply. It works.
But I have another problem in developing my app. In my app when I'm
installing rules on tables, I have a rule for two situations in a switch:
1. when a packet is incoming to in_port_1 and will go to out_port_2
2. when a packet is i
Hi, Mahdieh
You can use "ofproto.OFPP_IN_PORT" to do it.
actions = [parser.OFPActionOutput(ofproto.OFPP_IN_PORT)]
self.add_flow(datapath, 0, match, actions)
Then, the flow shown below will be installed.
$ovs-ofctl -O OpenFlow13 dump-flows s1
OFPST_FLOW reply (OF1.3) (xid=0x2):
Hi,
I want an ovs switch outputs a packet to its receiving port, but in ovs doc
I read:
actions=[action][,action...]
port
output:port
Outputs the packet to OpenFlow port number port. If
port is the packet's input port, the packet is not output.
so
Tahere Yaghou:
Hi,
I want an ovs switch outputs a packet to its receiving port, but in ovs doc
I read:
actions=[action][,action...]
port
output:port
Outputs the packet to OpenFlow port number port. If
port is the packet's input port, the packet is
