That explains why your flow isn't timing out - but why OpenVSwitch isn't honoring your request to set an idle_timeout is somewhat mystifying.
I would suggest looking at how the mininet folks advise you to use WireShark, here: http://mininet.org/walkthrough/ Use WireShark to see if the FlowMod contains the specified idle_timeout. If it doesn't? That's either a problem in Ryu, or in how you're constructing your FlowMod. As far as I can tell, though, your usage of FlowMod looks OK. I don't think it's Ryu either, though - I use idle_timeout in my application, on several different varieties of hardware switches. If the FlowMod does contain the idle_timeout? Then the OVS in your mininet instance is somehow choosing to not honor that idle_timeout - and I'm not quite sure what to do about that. ;) Best, Victor -- Victor J. Orlikowski <> vjo@[cs.]duke.edu > On May 4, 2016, at 8:01 AM, Eman Bany salameh <[email protected]> > wrote: > > it returns the flow table but the idle_timeout didn't appear ------------------------------------------------------------------------------ Find and fix application performance issues faster with Applications Manager Applications Manager provides deep performance insights into multiple tiers of your business applications. It resolves application problems quickly and reduces your MTTR. Get your free trial! https://ad.doubleclick.net/ddm/clk/302982198;130105516;z _______________________________________________ Ryu-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/ryu-devel
