day, February 21, 2011 5:01:52 PM GMT -08:00 US/Canada Pacific
> Subject: Re: [nox-dev] Getting individual flow stats for an python app
>
> So the thing is that flow.wildcard definitely needs to be at least 0x3f
> (and not 0x, which I am guessing you got from the monitor.py example,
t; Thanks!
>
> - Original Message -
> From: "Kyriakos Zarifis"
> To: malve...@cs.ucsd.edu
> Cc: nox-dev@noxrepo.org, "Murphy McCauley"
> Sent: Monday, February 21, 2011 5:01:52 PM GMT -08:00 US/Canada Pacific
> Subject: Re: [nox-dev] Getting individual flo
quot; < jam...@nau.edu >
Sent: Monday, February 21, 2011 2:47:10 PM GMT -08:00 US/Canada Pacific
Subject: Re: [nox-dev] Getting individual flow stats for an python app
can you try using " flow.wildcards = openflow.OFPFW_ALL"
after making sure that nox.lib.openflow has bee
be zero
> .. :(
>
>
> - Original Message -
> From: "Kyriakos Zarifis"
> To: malve...@cs.ucsd.edu
> Cc: nox-dev@noxrepo.org, "Murphy McCauley"
> Sent: Monday, February 21, 2011 2:47:10 PM GMT -08:00 US/Canada Pacific
> Subject: Re: [nox-dev]
quot; < jam...@nau.edu >
Cc: "Malveeka Tewari" < malve...@cs.ucsd.edu >, nox-dev@noxrepo.org
Sent: Monday, February 21, 2011 1:10:42 PM GMT -08:00 US/Canada Pacific
Subject: Re: [nox-dev] Getting individual flow stats for an python app
Exactly - there's an example of using
ge -
> From: "Kyriakos Zarifis"
> To: "Murphy McCauley"
> Cc: "Malveeka Tewari" , nox-dev@noxrepo.org
> Sent: Monday, February 21, 2011 1:10:42 PM GMT -08:00 US/Canada Pacific
> Subject: Re: [nox-dev] Getting individual flow stats for an python app
>
: "Kyriakos Zarifis"
Cc: nox-dev@noxrepo.org
Sent: Monday, February 21, 2011 1:37:39 PM GMT -08:00 US/Canada Pacific
Subject: Re: [nox-dev] Getting individual flow stats for an python app
Thanks! I have another question.
Using the nox controller , I have inserted forwarding rules
Tewari" , nox-dev@noxrepo.org
Sent: Monday, February 21, 2011 1:10:42 PM GMT -08:00 US/Canada Pacific
Subject: Re: [nox-dev] Getting individual flow stats for an python app
Exactly - there's an example of using this in netapps/monitoring.py (line 188)
in destiny, (and you can trace
Exactly - there's an example of using this in netapps/monitoring.py (line
188) in destiny, (and you can trace how it's handled etc)
If all you need is to print out/look at the flow stats (rather than act on
them programatically), and you do switch to destiny, you could use the gui
for that.
On M
I believe that the flow stats event is Pythonized in both the zaku and destiny
branches -- it's just that a helper method to make the callback easy to
register is missing from zaku. A simple register_for_flow_stats_in method DOES
exist in the destiny branch, though. So I'd suggest you either s
10 matches
Mail list logo
