If your switches support the Nicira / Open vSwitch extensions, an easy way to do it might be to modify RouteFlow very slightly so that it installs rules in a table that isn't the first one. Then use OVS's learning functionality to add rules that have IP/port (which you'd use for monitoring), but always still jump to the RouteFlow table to do the actual forwarding.
-- Murphy On Aug 17, 2013, at 10:39 AM, Anna Cruz <[email protected]> wrote: > Hi Murphy! > > What I need is to get source ip, source port, destination ip, destination > port and number of packages. I wanna take this to make a histogram to, then, > calculate shannon entropy. Get's the idea? > I'm using mininet as dataplane. > > > Sorry to my terrible english. > > Att, > Anna Cruz > > > On Fri, Aug 16, 2013 at 5:20 PM, Murphy McCauley <[email protected]> > wrote: > If those are the flow entries that RouteFlow is installing, then I don't know > that there's much sane to be done about it without modifying RouteFlow. How > big of a modification is needed may depend on exactly what you're trying to > do, what types of switches you have, etc. > > -- Murphy > > On Aug 16, 2013, at 12:25 PM, Anna Cruz <[email protected]> wrote: > > > Hi everyone, > > > > I'm getting flow statistics from pox in a structure including RouteFlow, so > > the match object is returning a wildcard and I can't get informations like > > nw_src, tp_src, tp_dst and so on > > > > Anyone can help me? > > Att, > > Anna Cruz > >
