JBS> We've created a NOX package that seems to run the 'switch' module
JBS> successfully outside of the build directory, including an init.d
JBS> script that starts up NOX instances based on config files in an
JBS> /etc/nox/instances.d directory. I'm going through the BBN process to
JBS> publish th
Hello,
Here are two patches for destiny for the Python API.
patch 1:
- in pyrt.cc, add datapath id to the dictionaries created by
Flow_removed_event and Error_event
patch2:
- add lots of doxygen doc strings to core.api
- add callback generators for flow mod and flow removed events
- change th
Dear all,
My name is Min-Hyup Kang,
I am a student who studying about openflow.
so, I have a question. Can I ask you please ?
I have a pronto 3290 switch. so, I would like to install nox controller.'
Which can I get the nox version ? (http://noxrepo.org/wp)
Thank you for y
Hi, and welcome to nox-dev.
I believe your switch supports OpenFlow 1.0, so either the zaku (stable)
or destiny (unstable) branch of NOX should work.
I don't know if you're familiar with git at all, but installation
instructions can be found on the wiki at:
http://noxrepo.org/noxwiki/index.php/NO
Derek,
Thanks for the patches, these are very helpful. One of us will take a
look shortly.
.martin
Hello,
Here are two patches for destiny for the Python API.
patch 1:
- in pyrt.cc, add datapath id to the dictionaries created by
Flow_removed_event and Error_event
patch2:
- add lots of
Hi Derek,
Thanks. Great patches as usual. I have pushed them to the destiny branch.
Martin and Murphy, I believe I have pushed most (if not all) of
Derek's patches at this moment. If anything else is missing, let me
know.
Thanks.
Regards
KK
On 11 January 2011 07:23, Martin Casado wrote:
>
Hi All,
With Derek's patch, the documentation for destiny branch is more
useful for those using Python. Consequently, I have pushed the
doxygen documentation for destiny (which include Derek's patch) to
replace the one previously generated from zaku. FYI.
Regards
KK
On 11 January 2011 11:43, k
