NOXRepo

It really depends on what you expect to trigger the event. The FlowRemoved event is triggered by an OpenFlow message from the switch. There’s no corresponding OpenFlow message for when a flow is installed, so what condition or event do you want to trigger your FlowAdded event?

As far as OpenFlow 1.0 goes (which is as far as the official versions of NOX go), I believe the only way ECMP features on the switch are utilized is if you output to the OFPP_NORMAL virtual port, in which case the switch can forward the packet however it likes (possibly including ECMP).

You could, however, build a reactive NOX application which…[Read more]

Yeah, the docs are kind of weak on this. I just slightly improved the section on recoco/tasks/etc. in the wiki.

1) POX has the recoco library for implementing simple cooperative tasks. You can use it, but you don’t have to — you can use normal threading if you want. Indeed, there are several parts of POX which use normal threads. You…[Read more]

For the most part, when an event occurs on the switch, it sends an OpenFlow message to its connected controllers (like POX). POX then raises a corresponding event.

Sorry I missed this — I don’t check the forums as often as I read the mailing list.

It looks like you’re not starting the task. You need to do l.start(). Though rather than have your own IO loop, I’d suggest that a more desirable way to do it is using IOWorker. This is what the STS debugger stuff does, but it hasn’t been the main POX…[Read more]

I’m not sure anyone involved with the CPqD fork monitors the messageboards. You might have better luck contacting Eder Leão Fernandes (listed as the contact in their README).

To do what is done in the video does not require a full LAMP stack, at least for the OpenFlow part — I don’t know what the traffic generator might require, for example. The OpenFlow functionality in that demo could easily be accomplished with POX and a few lines of Python code, or an HTTP requests to a POX-based webservice like…
curl -i -X…[Read more]

Any particular reason you want to use NOX?

POX is considerably easier. It will work with almost any current Linux distribution will do (and so will Windows, Mac OS, and other OSes). Installing it is basically one step. And it is better documented (for example on the POX wiki: https://openflow.stanford.edu/display/ONL/POX+Wiki)…

Host nodes are tricky. OpenFlow *tells* you about which switches exist, but how do you determine what the hosts are and where they are? POX has a hosttracker component which attempts to do this under some circumstances, but this is always going to be a bit of a guessing game if you’re trying to detect it from the traffic.

Adding more…[Read more]

This really depends on what you’re trying to do. The topo viewer is implemented in two parts. The backend part runs in POX and basically just listens to discovery events to construct an idea of the topology. That is communicated to the frontend part via the messenger system — a “service” part in POX and a “client” part in JavaScript. The…[Read more]

Thanks for the specifics. That was my first guess, but it’s been so long since I even thought about the NOX build system I was definitely not sure.

Glad it’s working.

Feel free to file an issue or submit a pull request on the github repository.