Hi Murphy, Thanks for the reply. No, I am not using NOX (Yes indeed - I should have gone to the OpenFlow mailing list. I will.). This is a new controller which is still under development. I am sure the controller does not send a features-request (because that part has not been coded yet). So,
Hi, The ofprotocol in the reference switch is more than just a relayer process. If I remember correctly it also deals with in-band control and port status handling. For this latter feature it needs to know what ports were assigned to the datapath, and might use a feature request of its own.
Hi Sergio, if you don't care to send out the buffered packet that triggered the packet_in (or if, for example, you just want to install a flow proactively) using buffer_id=-1 I think should work. On Fri, Jan 13, 2012 at 8:09 AM, Sergio Jiménez Feijóo jjji...@gmail.comwrote: Hi Guys, I'm
Hi dear nox developers, I am new to NOX development. I am trying to create my own component under a new directory. for testing purpose I did the following things (in the virtual machine): 1. made directory under the coreapps directory 2. I copy the files in the examples directory and renamed
i know that to promote your own blog post is in complete bad taste :) but here you will find some notes i took while i was starting writing components for nox...hope you will find it useful...if you find any errors please let me know... http://blog.egofuzzer.net/2011/10/developing-in-nox.html
from http://noxrepo.org/~yapkke/doc/Howto.html please try: 1) Create a new directory in coreapps, netapps or webapps 2) Add the appropriate C and header files with meta.json and Makefile.am 3) Add the new directory to configure.ac.in 4) Rerun ./boot.sh and ./configure (step 2 would be your