Datapath#ports is kept for compatibility with the previous openflow versions (<
1.3). Datapath#ports is not updated when received EventOFPPortStatus. This
behavior may confuse users. Wherefore, showing warning message when the user
accesses to Datapath#ports with the currently openflow versions
hi,
ryu just talks with OVS. OVS implements the functionality using the kernel
stuff. but ryu doesn't have direct knowledges about such implementation
details.
the URL you mentioned seems discussing about VM -> switch traffic shaping.
the rest_qos is meant about queue rates, which is about the
Hi,
On 2015年04月05日 03:08, Николай Жупиков wrote:
> Hello! Please tell me how to extract the value of the field tcp_flags
> (openflow 1.5) using ryu.
> If possible, write example code.
Your question is how to extract the tcp_flags from packets (e.g. from packet-in
data), right?
If so, you can do
On Fri, 3 Apr 2015 13:48:37 + (UTC)
"MD.Badruzzaman Shakib" wrote:
> In my application I want to match destination address while adding flows. I
> am using OFP1.3. The main problem is when I match the destination ip I used
>
> match = datapath.ofproto_parser.OFPMatch(
> dl_dst=
Hi again,
I have made following modification in 'match' field of my add_flow function -
match = datapath.ofproto_parser.OFPMatch(
ipv4_dst=ipv4_to_bin(dst))
But now when I send dst = 11.0.1.1 to the add_flow
