Re: [nox-dev] NOX cannot be compiled in Ubuntu 11.10?
Thanks Murphy, I tried applying the changes from 73fc9071b9d4f77b8314bf44fe4e5c6bccb480df in destiny branch to the zaku branch and now I can 'configure' successfully. But I am still not able to compile NOX. When I 'make' I got this error message: /bin/bash ../libtool --tag=CXX --mode=link g++ -fno-omit-frame-pointer -fno-strict-aliasing -Wall -Wno-sign-compare -Winit-self -Wformat-nonliteral -Wformat-security -g -O2 -R/usr/local/bin -export-dynamic -L/usr/lib -lboost_unit_test_framework-mt -lboost_filesystem-mt -lssl -lcrypto -Wl,-E -o nox_core components.xsd.o nox.xsd.o nox_main.o ./builtin/.libs/libbuiltin.la ./lib/libnoxcore.la libtool: link: g++ -fno-omit-frame-pointer -fno-strict-aliasing -Wall -Wno-sign-compare -Winit-self -Wformat-nonliteral -Wformat-security -g -O2 -Wl,-E -o .libs/nox_core components.xsd.o nox.xsd.o nox_main.o -Wl,--export-dynamic -L/usr/lib -lboost_unit_test_framework-mt -lboost_filesystem-mt -lssl -lcrypto ./builtin/.libs/libbuiltin.so ./lib/.libs/libnoxcore.so -Wl,-rpath -Wl,/usr/local/bin/builtin -Wl,-rpath -Wl,/usr/local/bin /usr/bin/ld: components.xsd.o: undefined reference to symbol 'boost::system::get_system_category()' /usr/bin/ld: note: 'boost::system::get_system_category()' is defined in DSO /usr/lib/libboost_system.so.1.42.0 so try adding it to the linker command line /usr/lib/libboost_system.so.1.42.0: could not read symbols: Invalid operation collect2: ld returned 1 exit status I am currently using boost 1.42. Previously I used boost 1.46 but there was another error message (which I didn't keep) and I thought the boost used is too new, therefore I changed it to 1.42. I can provide the 'make' log message with boost 1.46 if needed. Regards, Heryandi -Original Message- From: Murphy McCauley [mailto:jam...@nau.edu] Sent: Thursday, October 20, 2011 4:52 PM To: Heryandi Cc: nox-dev@noxrepo.org Subject: Re: [nox-dev] NOX cannot be compiled in Ubuntu 11.10? I believe I fixed this in the destiny branch some time ago. Give that a shot? -- Murphy On Oct 20, 2011, at 1:32 AM, Heryandi wrote: Hi all, I have previously compiled NOX successfully in ubuntu 10.04. Now, I am trying to compile NOX zaku in my ubuntu 11.10 VM, but it doesn't work. All the NOX dependencies have been installed. Here is the end of the configure output: checking pcap.h usability... yes checking pcap.h presence... yes checking for pcap.h... yes checking openssl/md5.h usability... yes checking openssl/md5.h presence... yes checking for openssl/md5.h... yes checking for MD5_Init in -lssl... no configure: error: openssl/md5.h not found. NOX requires OpenSSL The full log and the config.log output are as attached. I have installed openssl and I can find the md5.h inside /usr/include/openssl/md5.h. Regards, Heryandi CONFIDENTIALITY: This email is intended solely for the person(s) named and may be confidential and/or privileged. If you are not the intended recipient, please delete it, notify us and do not copy, use, or disclose its content. Towards A Sustainable Earth: Print Only When Necessary. Thank you. config.logconfigure output.log___ nox-dev mailing list nox-dev@noxrepo.org http://noxrepo.org/mailman/listinfo/nox-dev ___ nox-dev mailing list nox-dev@noxrepo.org http://noxrepo.org/mailman/listinfo/nox-dev
Re: [nox-dev] NOX cannot be compiled in Ubuntu 11.10?
Patches to fix this link error and to make us compatible with Boost 1.46 have been pushed. -- Murphy On Oct 20, 2011, at 11:17 PM, Heryandi wrote: Thanks Murphy, I tried applying the changes from 73fc9071b9d4f77b8314bf44fe4e5c6bccb480df in destiny branch to the zaku branch and now I can 'configure' successfully. But I am still not able to compile NOX. When I 'make' I got this error message: /bin/bash ../libtool --tag=CXX --mode=link g++ -fno-omit-frame-pointer -fno-strict-aliasing -Wall -Wno-sign-compare -Winit-self -Wformat-nonliteral -Wformat-security -g -O2 -R/usr/local/bin -export-dynamic -L/usr/lib -lboost_unit_test_framework-mt -lboost_filesystem-mt -lssl -lcrypto -Wl,-E -o nox_core components.xsd.o nox.xsd.o nox_main.o ./builtin/.libs/libbuiltin.la ./lib/libnoxcore.la libtool: link: g++ -fno-omit-frame-pointer -fno-strict-aliasing -Wall -Wno-sign-compare -Winit-self -Wformat-nonliteral -Wformat-security -g -O2 -Wl,-E -o .libs/nox_core components.xsd.o nox.xsd.o nox_main.o -Wl,--export-dynamic -L/usr/lib -lboost_unit_test_framework-mt -lboost_filesystem-mt -lssl -lcrypto ./builtin/.libs/libbuiltin.so ./lib/.libs/libnoxcore.so -Wl,-rpath -Wl,/usr/local/bin/builtin -Wl,-rpath -Wl,/usr/local/bin /usr/bin/ld: components.xsd.o: undefined reference to symbol 'boost::system::get_system_category()' /usr/bin/ld: note: 'boost::system::get_system_category()' is defined in DSO /usr/lib/libboost_system.so.1.42.0 so try adding it to the linker command line /usr/lib/libboost_system.so.1.42.0: could not read symbols: Invalid operation collect2: ld returned 1 exit status I am currently using boost 1.42. Previously I used boost 1.46 but there was another error message (which I didn't keep) and I thought the boost used is too new, therefore I changed it to 1.42. I can provide the 'make' log message with boost 1.46 if needed. Regards, Heryandi -Original Message- From: Murphy McCauley [mailto:jam...@nau.edu] Sent: Thursday, October 20, 2011 4:52 PM To: Heryandi Cc: nox-dev@noxrepo.org Subject: Re: [nox-dev] NOX cannot be compiled in Ubuntu 11.10? I believe I fixed this in the destiny branch some time ago. Give that a shot? -- Murphy On Oct 20, 2011, at 1:32 AM, Heryandi wrote: Hi all, I have previously compiled NOX successfully in ubuntu 10.04. Now, I am trying to compile NOX zaku in my ubuntu 11.10 VM, but it doesn't work. All the NOX dependencies have been installed. Here is the end of the configure output: checking pcap.h usability... yes checking pcap.h presence... yes checking for pcap.h... yes checking openssl/md5.h usability... yes checking openssl/md5.h presence... yes checking for openssl/md5.h... yes checking for MD5_Init in -lssl... no configure: error: openssl/md5.h not found. NOX requires OpenSSL The full log and the config.log output are as attached. I have installed openssl and I can find the md5.h inside /usr/include/openssl/md5.h. Regards, Heryandi CONFIDENTIALITY: This email is intended solely for the person(s) named and may be confidential and/or privileged. If you are not the intended recipient, please delete it, notify us and do not copy, use, or disclose its content. Towards A Sustainable Earth: Print Only When Necessary. Thank you. config.logconfigure output.log___ nox-dev mailing list nox-dev@noxrepo.org http://noxrepo.org/mailman/listinfo/nox-dev ___ nox-dev mailing list nox-dev@noxrepo.org http://noxrepo.org/mailman/listinfo/nox-dev
Re: [nox-dev] Flow expired events in NOX
I'm seeing another issue. I'm getting flow expired message even before a flow is started. I'm getting the flow expired messages when the switch is trying to connect to NOX. Please see the prints below. Why is flow expiry messages coming? 00041|openflow|DBG:Passive tcp interface bound to port 6633 00042|nox|INFO:nox bootstrap complete 00043|openflow|DBG:Passive tcp interface received connection 00044|openflow|DBG:stream: negotiated OpenFlow version 0x01 (we support versions 0x01 to 0x01 inclusive, peer no later than version 0x01) 00045|nox|DBG:Success sending in 'sending switch config' 00046|nox|DBG:Success sending in 'receiving features reply' 00047|nox|DBG:Success receiving in 'receiving features reply' 00048|nox|DBG:Success sending in 'receiving ofmp capability reply' 00049|nox|DBG:Success receiving in 'receiving ofmp capability reply' 00050|nox|DBG:Datapath 0036fb31fe75 sent error in response to capability reply, assuming no management support 00051|nox|DBG:No switch auth module registered, auto-approving switch 00052|nox|DBG:Registering switch with DPID = 36fb31fe75 00053|nox.coreapps.examples.pyswitch|INFO:Switch 36fb31fe75 has joined the network 00054|openflow-event|DBG:received flow expired event from 0036fb31fe75 00055|openflow-event|DBG:received flow expired event from 0036fb31fe75 00056|openflow-event|DBG:received flow expired event from 0036fb31fe75 00057|openflow-event|DBG:received flow expired event from 0036fb31fe75 00058|openflow|DBG:Passive tcp interface received connection 00059|openflow|DBG:stream: negotiated OpenFlow version 0x01 (we support versions 0x01 to 0x01 inclusive, peer no later than version 0x01) 00060|nox|DBG:Success sending in 'sending switch config' 00061|nox|DBG:Success sending in 'receiving features reply' 00062|nox|DBG:Success receiving in 'receiving features reply' 00063|nox|DBG:Success sending in 'receiving ofmp capability reply' 00064|nox|DBG:Success receiving in 'receiving ofmp capability reply' 00065|nox|DBG:Datapath 0036fb31fe76 sent error in response to capability reply, assuming no management support 00066|nox|DBG:No switch auth module registered, auto-approving switch 00067|nox|DBG:Registering switch with DPID = 36fb31fe76 00068|nox.coreapps.examples.pyswitch|INFO:Switch 36fb31fe76 has joined the network 00069|openflow-event|DBG:received flow expired event from 0036fb31fe76 00070|openflow-event|DBG:received flow expired event from 0036fb31fe76 00071|openflow-event|DBG:received flow expired event from 0036fb31fe76 00072|openflow-event|DBG:received flow expired event from 0036fb31fe76 Thanks Regards, Candy On Thu, Oct 20, 2011 at 3:26 PM, kk yap yap...@stanford.edu wrote: Hi, Try changing src/include/openflow-default.hh. Hope this is what you are looking for. Regards KK On 20 October 2011 13:42, Candy Floss cndf...@gmail.com wrote: Thanks for the reply. I'm not running discovery module. The idle time out is set for 5 secs and the hard timeout is set to 0(i.e. permanent). These are the parameters that are in the code by default. I have not changed anything. Regards, Candy On Thu, Oct 20, 2011 at 1:39 PM, Kyriakos Zarifis kyr.zari...@gmail.com wrote: Hi, are you running 'discovery' or any other application that has discovery as a dependency? If so, the packet_ins you see are most probably the control (LLDP) packets sent by discovery to discover neighbors. ( http://noxrepo.org/noxwiki/index.php/Discovery ) the flow expiration time is set from the controller, when you send the flow_mods. The flow_mod includes arguments to set hard/idle timeout for the entry. 'Idle timeout' means the entry will expire X seconds after no matching traffic has hit the switch, 'hard timeout' means it will expire in X seconds no matter what. (Section 5.5.3 in http://www.openflow.org/documents/openflow-spec-v1.0.0.pdf) On Thu, Oct 20, 2011 at 1:27 PM, Candy Floss cndf...@gmail.com wrote: I have copnnected NOX and two switches. Sometimes when I connect the switch to the NOX I see packet_in event in addition to datapath_join event. This is happening randomly. Not able to find a pattern when this eaxctly happens but it happens most of teh time. I'm not starting any flows but I still see packet_in event coming continously. What could be the reason? And also when I start the flow I see flow expired event on NOX in 1-2 secs. Where can I change the default timeout? Do I have to change in NOX or in openflow switch? Thanks Regards, Candy ___ nox-dev mailing list nox-dev@noxrepo.org http://noxrepo.org/mailman/listinfo/nox-dev ___ nox-dev mailing list nox-dev@noxrepo.org http://noxrepo.org/mailman/listinfo/nox-dev ___ nox-dev mailing list nox-dev@noxrepo.org http://noxrepo.org/mailman/listinfo/nox-dev
[nox-dev] The status of NOX
This is a quick update about the status of NOX. While, over the past few years, NOX has gone from the only controller available to one among many controller options, we want to emphasize that NOX is still here and is being actively maintained and improved. The NOX community is largely centered around the nox-dev mailing list (which is relatively active -- something like 100 posts per month), and consists of a mix of users -- those just playing around with the technology (asking questions), those actively using NOX for research or other projects (reporting bugs), those using NOX for a commercial product, and a handful of developers (who, we hope, are effectively meeting the needs of the previous three groups). There has also been some progress on NOX that hasn't been widely discussed yet. Specifically, there's a new branch which we're pretty excited about. It is the biggest update to NOX we've seen so far, and it responds to requests from the community: in particular, this release involves a streamlining of the codebase and API, along with a sizable performance jump. We are close to making this branch public. We also know that quite a few NOX users appreciate the Python interface. We want to support these users even better. To that end, we've been developing POX -- a new controller framework written in pure Python. We think it's pretty quick and easy to hack on, and it is remarkably easy to deploy. It's still under active initial development, but there are a handful of projects using it now or that are planning to use it soon. We aren't sure exactly when to expect a 1.0 release of POX, but it's coming along. In short: NOX has a thriving community of users, both commercial and academic, and an active set of developers committed to maintaining and improving the codebase, with bugs fixed rapidly and a fairly substantial NOX upgrade on the way. There's even an entirely new Python-only controller in the works to provide an even easier-to-use controller for those who want a Python interface. The comments at ONS about lack of NOX support were ill-informed and may have caused a bit of undue concern, and we hope this note clarifies the situation. We remain interested in your feedback, stand ready to fix any problems you find, and are excited to keep the project moving forward. Murphy McCauley Martin Casado Kyriakos Zarifis Amin Tootoonchian ___ nox-dev mailing list nox-dev@noxrepo.org http://noxrepo.org/mailman/listinfo/nox-dev
