Re: [nox-dev] Setting up a Flowmod in several Openflow switches at once.

2011-10-05 Thread Murphy McCauley
The buffer_id isn't required. Set it to -1 on the switches that aren't the one that it originated from. This could be clearer in the spec, but it's in there. Also, you might want to take a look at the routing components in NOX (e.g., sprouting), since installing flows along an optimal path is

Re: [nox-dev] Setting up a Flowmod in several Openflow switches at once.

2011-10-05 Thread Aimal Khan
Hi, You do not need buffer_id but what you really need is the Datapath ID ( or pi.datapath_id as you will see it the switch example ) of each switch to correctly identify all the switches currently connected to the Controller. You should look into Datapath join event (the event caused by a switch

Re: [nox-dev] Getting Actions From Events in Python

2011-10-05 Thread Christian Esteve Rothenberg
Hi Derek, did you succeed in implementing the to_python() for the action list in flow_stats? Does someone have a patch for this issue? Thanks, Christian On Fri, Jan 28, 2011 at 11:51, James Murphy McCauley jam...@nau.edu wrote: Yeah, I think this looks like the right direction.  I probably

Re: [nox-dev] Getting Actions From Events in Python

2011-10-05 Thread Murphy McCauley
Derek and I fixed this up quite a while ago. It's one of the commits that got lumped together and doesn't have a good commit message, but it's been in destiny for months now. (One day I may actually fix the commit log for it.) -- Murphy On Oct 5, 2011, at 2:39 PM, Christian Esteve Rothenberg