NOX is an open-source OpenFlow controller. Its purpose is to provide a simplified platform for writing network control software in C++ or Python. While still under heavy development, NOX is currently used in a number of large production network deployments. New users can learn more from the NOX development mailing list.
The nox-dev mailing list is still the best way discuss NOX or ask for help, but there is now also a IRC channel where NOX developers and users can hangout for a more real-time type of interaction.
Join us on #noxcontroller on “freenode” servers.
(For instant web-based access: http://webchat.freenode.net/ )
The Wiki is currently the most up-to-date resource of information about NOX, covering basic concepts, installation, development, FAQ.
New users are encouraged to go through it, and older users can use it as a reference. The content will be dynamic and always up-to-date with the latest releases of NOX. Feel free to contribute.
-kk
The NOX team is happy to announce the release of NOX-Zaku (based on
the unstable/destiny branch – Sept 15, 2010). This release will
replace the current HEAD with the following changes:
The new release structure is described in
http://noxrepo.org/noxwiki/index.php/NOX_Introduction#Versioning.
As a note, this results in the following branches in the
git://noxrepo.org/nox repository:
The last three branches are retained for legacy and will not be supported.
We are also reaching out to the community to contribute to NOX (code,
patches and components) and keep documentation up-to-date. To aid the
process, documentation has been moved to a wiki at
http://noxrepo.org/noxwiki/.
We understand that there is a lot of changes made from the master
branch which is fairly old, and this might cause some churn in other’s
code. We are hoping the streamlining will minimize future pain. Hope
we have everyone’s understanding too.
Best wishes
The NOX Team
We’ve pushed the latest Nox codebase (0.6.0) to git on noxrepo. Currently this version is available from git pending updates to documentation and further examples. We will provide more formal release notes on 0.6.0 later, but briefly it is a much simpler and robust codebase than 0.5. We suggest that projects built on Nox plan to transition to 0.6.0.
To get/build the code:
git clone git://noxrepo.org/nox
cd nox
./boot.sh
mkdir build
cd build/
../configure
make
NOX 0.5 has been added to the download page and pushed to the noxrepo git repository. The major changes include removing dojo, restructuring of authenticator, and many bugfixes. Users of 0.4 can probably upgrade to 0.5 without requiring any major restructuring. You can download the source releases here:
To download from git:
mkdir nox
cd nox/
git clone git://noxrepo.org/noxcore
cd noxcore
./boot.sh
mkdir build
cd build/
../configure –with-python=yes
make
We’ve pushed a non-trivial update to git which includes a number of bug fixes. The most significant fixes were in netapps so if you rely on any of those applications, it is a good idea to update.
The binaries posted for running OpenFlow in the virtual test environment were really old (0.8.1) and causing problems. They’ve since been updated to the latest release (0.8.9).
Quicklinks:
We pushed 0.4.0 to the public nox git repository. The primary benefit of these changes is that much of the cruft which was never used has been removed. Also it is now possible to only build the core apps (with greatly reduced compile times).
To build just the core packages:
git clone git://noxrepo.org/noxcore
cd noxcore
./boot.sh –apps-core
mkdir build && cd build
../configure –with-python=yes –enable-ndebug
make – j 2
Please let us know if you experience build problems.
I installed Redmine for bug and feature tracking of NOXrepo. The URL is http://noxrepo.org:8080/redmine/. It would be very helpful if feature requests and bugtreport where filed with Redmine so we can keep track of them. Let us know if you have any problems with the registration process.
0
Back to top