Dear, Actually RYU controller can provide it. I have not tested yet but I found it.
c*lass *ryu.ofproto.ofproto_v1_3_parser.NXActionRegLoad(*ofs_nbits*, *dst*, *value*, *type_=None*, *len_=None*, *experimenter=None*, *subtype=None*) I see this class can be used. This one is similar to the "*load*:*value*-> *dst**[**start*..*end* *]" of ovs-ofctl * On Mon, Aug 12, 2019, 2:32 AM Pedro Andres Aranda Gutierrez < paag...@gmail.com> wrote: > Thinking a bit, you may want to try tables. Although I fear the switch > will know the in_port and block. Another solution may be to have two OVS > instances that talk through more than one virtual port and you have an > application that overrides loop detection. > > Best /Pedro A > > Enviado desde mi iPhone > > El 10 ago 2019, a las 20:07, Soe Ye Htet <soeyehtet1...@gmail.com> > escribió: > > Unfortunately, that one is not worked. As long as the inport number and > outport number is same, OvS will simply drop that matched packet. > > On Sun, Aug 11, 2019, 12:51 AM <arti...@gmail.com> wrote: > >> Soe, >> >> Sorry about jumping in but the solution to your problem may be to force >> the packet to be forwarded to the same ingress port by using the reserved >> port OFPP_IN_PORT. >> >> Regards, >> >> Maen >> >> >> >> *From:* Soe Ye Htet <soeyehtet1...@gmail.com> >> *Sent:* Saturday, August 10, 2019 12:17 PM >> *To:* Pedro Andres Aranda Gutierrez <paag...@gmail.com> >> *Cc:* Ryu-devel@lists.sourceforge.net >> *Subject:* Re: [Ryu-devel] Modifying ingress port number in RYU >> controller >> >> >> >> Dear, >> >> >> >> Due to some situation in my wireless network, there is only one port in >> my openflow switch. However, sometimes that openvswitch need to relay other >> packets to other node for eg, if the wireless node receive that packet >> receives at port number 1 and that received packet is not intended to that >> node, that wireless node simply forward to its neighbor node. So the rules >> will be, in_port=1, dst_ip=other wireless node's ip, actions=output:1. In >> that case, OpenvSwtich will simply drop the packet instead of forwarding to >> prevent the looping problem. Therefore, the in_port number need to be >> logically changed. In openvswitch, we can simply install that rules by >> putting command " sudo xxxxx actions="load:0->OXM_OF_IN_PORT[]". If you >> know how to do that one, please let me know. >> >> >> >> Best regards, >> >> Soe Ye Htet >> >> Research Assistant >> >> Chulalongkorn University >> >> >> >> On Sat, Aug 10, 2019 at 10:07 PM Pedro Andres Aranda Gutierrez < >> paag...@gmail.com> wrote: >> >> Hi, why would you want to do such a thing? Just curious, /Pedro >> >> Enviado desde mi iPhone >> >> >> El 9 ago 2019, a las 9:41, Soe Ye Htet <soeyehtet1...@gmail.com> >> escribió: >> >> Dear RYU Team, >> >> >> >> May I raise one question that how can I change or modify the ingress port >> number in RYU controller. In OVS, we can simply put >> "load:0->OXM_OF_IN_PORT[]" >> this statement at action field. In RYU controller, >> >> how can i install that action. >> >> >> >> -- >> >> Best Regards, >> >> Soe Ye Htet >> >> Research Assistant (Chulalongkorn University) >> >> +66647240647 >> >> _______________________________________________ >> Ryu-devel mailing list >> Ryu-devel@lists.sourceforge.net >> https://lists.sourceforge.net/lists/listinfo/ryu-devel >> >> >> >> >> -- >> >> Best Regards, >> >> Soe Ye Htet >> >> Research Assistant (Chulalongkorn University) >> >> +66647240647 >> >> >> <https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=emailclient> >> Virus-free. >> www.avast.com >> <https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=emailclient> >> <#m_2922468183626164697_m_4591071135359504327_m_-5295692434427211613_DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2> >> >
_______________________________________________ Ryu-devel mailing list Ryu-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/ryu-devel
